Skip to main content

Why did Rust ignore a change to your procedural map settings?

A change to procedural generation settings usually takes effect when Rust creates the map. Check for an existing map before assuming your new setting did nothing.

Compare the launch settings and the loaded map

Check that the launch settings reference the file you edited through world.configfile and that it lives inside the intended server identity folder. For example, if you set Trails to false and still see the same trails, check whether the old map was already present. Keep that live map and save while you test.

Generate once in a separate test folder

Use a fresh test identity with the intended seed and size and the changed configuration. Look for the expected result there, such as the absence of the trails you targeted. If the clean generation behaves as expected, use the change at your next planned world reset. If it still differs, check the configuration name and values before changing another option.

If both versions look the same around the first landmark, check a second area where you know the old world has trails. A valid change may be hard to spot in a place that never had the feature.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details