After you configure an ARK to your liking in singleplayer mode, copy the values to your dedicated server’s Game.ini file, and then host the server on the map called “PGARK” (ala “ShooterGameServer.exe PGARK?listen”. The server will automatically load whatever PGMapName you have set. So if you want to do a different Procedural ARK, change the PGMapName value to “YourPGARK2” and you’ll get a different savedata for that. You can revert back to any previous PGMapName to load the data of a previously saved PGARK. Note that if you have no existing save data for the PGMapName, it will use the PGTerrainPropertiesString to create the new ARK. But after you have save data for a PGMapName, the INI’s PGTerrainPropertiesString will not take effect when loading that save data — instead, it will use whatever procedural settings are contained within the PGMapName’s existing savedata. In other words, to try out a new PGTerrainPropertiesString configuration, you either would need to delete your PGMapName’s savedata, or use a different PGMapName.

To get a PGARK configuration that you like, we recommend experimenting in singleplayer through the in-game UI, and then once you have settings you’re happy with, copy the PGTerrainPropertiesString from your Windows\Game.ini into your dedicated server’s WindowsServer\Game.ini (into the [/Script/ShooterGame.ShooterGameMode] section as described above). Then, as long as you’re hosting a new PGMapName, those settings will take effect just as they were in your singleplayer game!