Read the seed from the active dedicated-server save
- Step 1: Ask the dedicated-server owner to identify the server save and authorize the lookup; do not use a client character folder as the seed source.
- Step 2: Copy the seed from the server save or administrator workflow, record the server version, and open it in the viewer with the matching version.
- Step 3: Verify one known server landmark in the live world, then share only the coordinates needed for the group’s route.
The server seed is an administrative record, not a value to guess. A self-hosted dedicated server commonly stores its active world under the server account’s worlds_local directory, while a provider such as Nitrado exposes the active save through its file manager or backup panel. The owner must identify the running world and copy the seed from that authoritative save; a client’s local character folder cannot provide it.
First establish which save is active and whether the provider panel or a local server folder owns it; only then use a viewer for route planning.
Ask the host which save is active, whether the server uses a provider panel or a local file, and when the last restart occurred. Copy the seed from that authoritative record, then verify spawn or one known landmark after joining. Never replace a live server save while testing a viewer result; work from a copy and keep the original path unchanged.
- Ask the server owner to identify the save and authorize the lookup.
- Open the seed with the matching version before using a viewer.
- Verify one known server landmark in the live world before sharing coordinates with the group.
Confirm the result in game
The owner has authorized the lookup and the viewer reproduces the server world closely enough for planning.
If joining or applying the setting fails
- Stop if the save owner or file scope is unclear.
- Restore the untouched server copy after a failed inspection.
- Share only the coordinates the group actually needs.