Skip to content

Commit 9011fb2

Browse files
committed
Further improve README
Making it clearer the Panel / DSSettings is preferred and cleanly splitting the 2 configuration options.
1 parent 9ac4a38 commit 9011fb2

File tree

1 file changed

+80
-99
lines changed

1 file changed

+80
-99
lines changed

starrupture/README.md

Lines changed: 80 additions & 99 deletions
Original file line numberDiff line numberDiff line change
@@ -3,28 +3,19 @@
33
StarRupture is a first-person open-world base-building game with advanced combat and tons of exploration. Play alone or in a group on this sublime and ever-changing planet, extract and manage resources, create your complex industrial system, and fight off hordes of alien monsters.
44

55
> ⚠️ **Note:** Server software is still in an experimental phase. Expect some issues in future updates!
6+
67
## Contributors
78

89
| Name | GitHub Profile |
910
|------------|-----------------------------------------|
1011
| brainshead | https://github.com/brainshead |
1112
| SavageCore | https://github.com/SavageCore |
1213

13-
### Configuration files
14-
15-
| File | Purpose | Path |
16-
|-----------|---------|---------|
17-
| DSSettings.txt | General game configuration | /home/container/StarRupture/DSSettings.txt |
18-
| Password.json | Admin password configuration | /home/container/Password.json |
19-
| PlayerPassword.json | Player password configuration | /home/container/PlayerPassword.json |
20-
21-
You can generate the password files at https://starrupture-utilities.com/passwords.
22-
2314
## Server Ports
2415

25-
| Name | Default |
26-
|---------|---------------|
27-
| Game | 7777 |
16+
| Name | Default |
17+
|------|---------|
18+
| Game | 7777 |
2819

2920
## System Requirements
3021

@@ -33,108 +24,98 @@ You can generate the password files at https://starrupture-utilities.com/passwor
3324
| Minimal | 2 GB | 25 GB |
3425
| Recommended | 4+ GB | 40 GB+ |
3526

27+
## Configuration Files
28+
29+
| File | Purpose | Path |
30+
|---------------------|------------------------------|--------------------------------------------|
31+
| DSSettings.txt | Server configuration for save management | /home/container/DSSettings.txt |
32+
| Password.json | Admin password configuration | /home/container/Password.json |
33+
| PlayerPassword.json | Server join password configuration | /home/container/PlayerPassword.json |
34+
| .pteroignore | Files/folders to ignore during backups | /home/container/.pteroignore |
35+
36+
Unofficial documentation: https://wiki.starrupture-utilities.com/en/dedicated-server/configuration
37+
3638
---
3739

38-
## Configuration
40+
# Setup Methods
3941

40-
You must stop the server before making any configuration changes to DSSettings.txt or password files.
42+
There are two ways to configure your server: via the **Panel** (recommended) or **In-Game**. Choose one method and follow it consistently.
4143

42-
Unofficial documentation: https://wiki.starrupture-utilities.com/en/dedicated-server/configuration
44+
---
45+
46+
## Method 1: Panel Configuration (Recommended)
4347

44-
### Password Protection
48+
This method uses the Pterodactyl Panel and `DSSettings.txt` for all configuration. This is the recommended approach as settings persist across server restarts.
49+
50+
> ⚠️ **Important:** Always stop the server before making configuration changes.
51+
52+
### Password Setup
4553

4654
> ⚠️ **Warning:** Anyone who knows your IP and port can join your server if no password is set!
4755
48-
### Option 1: Manual Creation
4956
1. Visit https://starrupture-utilities.com/passwords
50-
2. Generate both an Admin password and a Player Password
51-
3. Create `Password.json` in the root of the container (`/home/container/`) and paste the contents of the site's Password.json field into it
52-
4. Create `PlayerPassword.json` in the root of the container (`/home/container/`) and paste the contents of the site's PlayerPassword.json field into it
53-
5. Start server!
54-
55-
### Option 2: In-Game Server Management
56-
1. Start your server (ensure no `DSSettings.txt` file exists).
57-
2. Open the StarRupture game client.
58-
3. From the main menu, open **Manage Server** and connect to your server.
59-
4. When prompted, configure an **Admin Password**.
60-
5. Click **Change Password** and enter the join password for players.
61-
6. Press **Back** (or ESC). **Do not** create or load a game at this point.
62-
7. Stop your server.
63-
8. Continue with the `DSSettings.txt` configuration below.
64-
65-
## Save Game Management
66-
67-
There are two ways to manage save games:
68-
69-
### Option 1: Manual Configuration (Loading save when server starts.)
70-
71-
Create/Edit the `DSSettings.txt` file in the root directory (`/home/container/`) with the following contents:
72-
73-
```json
74-
{
75-
"SessionName": "StarRuptureServer",
76-
"SaveGameInterval": "300",
77-
"StartNewGame": "false",
78-
"LoadSavedGame": "true",
79-
"SaveGameName": "AutoSave0.sav"
80-
}
81-
```
82-
83-
### Configuration Options
84-
85-
| Option | Description |
86-
|------------------|-----------------------------------------------------------------------------|
87-
| `SessionName` | Name of the save game session. Maximum 20 characters. |
88-
| `SaveGameInterval` | Time between automatic saves in seconds (e.g., `300` = 5 minutes). |
89-
| `StartNewGame` | `true` to create a new world, `false` to prevent new save creation. |
90-
| `LoadSavedGame` | `true` to load an existing save, `false` to skip loading saved data. |
91-
| `SaveGameName` | Filename of the save to load (e.g., `AutoSave0.sav`). |
57+
2. Generate both an Admin password and a Player password
58+
3. Create `Password.json` in the root of the container (`/home/container/`) and paste the generated content
59+
4. Create `PlayerPassword.json` in the root of the container (`/home/container/`) and paste the generated content
60+
5. Start the server
61+
62+
### Save Game Settings
63+
64+
The egg manages `DSSettings.txt` automatically via the Panel's **Startup** tab.
65+
66+
| Panel Option | DSSettings.txt Key | Description |
67+
|----------------------------|--------------------|----------------------------------------------------------------|
68+
| `[SERVER] Session Name` | `SessionName` | Name of the save game session (max 20 characters) |
69+
| `[SERVER] Save Interval` | `SaveGameInterval` | Time between automatic saves in seconds (e.g., `300` = 5 mins) |
70+
| `[SERVER] Start new Savegame` | `StartNewGame` | `true` to create a new world (use only once!) |
71+
| `[SERVER] Load saved Game` | `LoadSavedGame` | `true` to load an existing save on startup |
72+
| `[SERVER] Savegame Name` | `SaveGameName` | Filename of the save to load (e.g., `AutoSave0.sav`) |
73+
74+
### Creating a New World
75+
76+
> ⚠️ **Important:** Only enable `Start new Savegame` for initial world creation - disable it immediately after!
77+
78+
1. Stop the server
79+
2. Go to the **Startup** tab in the Panel
80+
3. Set `[SERVER] Load saved Game` to `false`
81+
4. Set `[SERVER] Start new Savegame` to `true`
82+
5. Start the server and join to verify it works
83+
6. Stop the server
84+
7. Set `[SERVER] Load saved Game` to `true`
85+
8. Set `[SERVER] Start new Savegame` to `false`
86+
9. Start the server - it will now load your new world on each restart
87+
88+
### Loading an Existing Save
89+
90+
1. Stop the server
91+
2. Go to the **Startup** tab in the Panel
92+
3. Set `[SERVER] Load saved Game` to `true`
93+
4. Set `[SERVER] Start new Savegame` to `false`
94+
5. Set `[SERVER] Savegame Name` to match your save file (e.g., `AutoSave0.sav`)
95+
6. Set `[SERVER] Session Name` to match your session folder name (e.g., `StarRuptureServer`)
96+
7. Start the server
9297

9398
---
9499

95-
## Creating a New World
96-
97-
> ⚠️ **Important:** Only set `StartNewGame` to `true` once when creating a new world!
98-
1. Stop the server.
99-
2. Update `DSSettings.txt`:
100-
```json
101-
"StartNewGame": "true",
102-
"LoadSavedGame": "false"
103-
```
104-
3. Start the server and wait for it to finish loading.
105-
4. Stop the server.
106-
5. Revert `DSSettings.txt`:
107-
```json
108-
"StartNewGame": "false",
109-
"LoadSavedGame": "true"
110-
```
111-
6. Start the server and join.
100+
## Method 2: In-Game Configuration
112101

113-
---
102+
This method uses the game's built-in **Manage Server** feature. Only use this method if you have issues with DSSettings.txt.
114103

115-
## Loading an Existing Save
104+
> ⚠️ **Important:** For this method to work, `DSSettings.txt` must **not** exist. Shutdown the server and delete it if present. You'll be stuck on a loading spinner when trying to connect if it exists.
116105
117-
1. Stop the server.
118-
2. Ensure `DSSettings.txt` contains:
119-
```json
120-
"StartNewGame": "false",
121-
"LoadSavedGame": "true",
122-
"SaveGameName": "AutoSave0.sav",
123-
"SessionName": "MyExistingSave"
124-
```
125-
3. Upload your `.sav` and `.met` files to:
126-
```
127-
/home/container/StarRupture/Saved/SaveGames/MyExistingSave/
128-
```
106+
### Password Setup
129107

130-
> You will need to create the `MyExistingSave` folder if it does not exist:
108+
1. Start your server
109+
2. Open the StarRupture game client
110+
3. From the main menu, select **Manage Server** and connect to your server
111+
4. When prompted, configure an **Admin Password**
112+
5. Click **Change Password** to set the player join password
131113

132-
4. Rename the files to `AutoSave0.sav` and `AutoSave0.met`.
133-
5. Start the server and join.
114+
### Save Game Management
134115

135-
### Option 2: In-Game Server Management
116+
1. Start your server
117+
2. Open the StarRupture game client
118+
3. From the main menu, select **Manage Server** and connect to your server
119+
4. Use the in-game interface to create a new world or load an existing save
136120

137-
1. Start your server (ensure no `DSSettings.txt` file exists).
138-
2. Open the StarRupture game client.
139-
3. From the main menu, open **Manage Server** and connect to your server.
140-
4. From here, you can create a new world or load an existing save.
121+
> ⚠️ **Note:** With this method, you will need to load your save via the in-game interface each time the server restarts.

0 commit comments

Comments
 (0)