Configuration with Application Deployment - Windrose server instance creates new world on restart

Technical Support
,
1

System Information

Field Value
Operating System Windows - Windows 11 Pro on x86_64
Product AMPService ‘Deimos’ v2.7.0.0 (Mainline)
Virtualization None
Application Application Deployment
Module ADSModule
Running in Container No
Current State Indeterminate

Problem Description

Issue

After server/instance restart a new world folder is created in the ‘windrose\4129620\R5\Saved\SaveProfiles\Default\RocksDB\0.10.0\Worlds’ folder.

Attempted to updated ServerDescription.json in ‘windrose\4129620\R5’ folder, and when server was restarted a new world was created updating this json as well.

Appears to be an issue with how the server/instance is being launched.

Reproduction Steps

  • Create Windrose instance
  • Run Windrose instance
  • Restart Windrose server
  • Observe none of items/world is same
2

seems like the setting for world id needs to be configured in amp.
World Island ID

Sets the ID of world to load on server start. It must match the ID in that world’s ‘WorldDescription.json’ file. Empty = new world (the world ID generated for that world can be imported from ‘R5/ServerDescription.json’ into this setting)

and for some reason even upon creating a world the id isnt pinned.

so steps i took to lock it in was after world creation you need to gather the WorldIslandId from
windrose/4129620/R5/Saved/SaveProfiles/Default/RocksDB/0.10.0/Worlds/<WORLD_ID>/WorldDescription.json
once i set the setting in the config the world seems to persist between restarts.

3

See Windrose Server Guide

4

This is not working for me, whenever i restart my server it creates a new world file in “.\windrose\4129620\R5\Saved\SaveProfiles\Default\RocksDB\0.10.0\Worlds”.

It completely ignores what ID I put in to the AMP windrose config “World Island ID” field and also if I change the ID in the ServerDescription.json file manually it creates a new world and replaces the ID in the “ServerDescription.json” file after every restart.

5

Same behavior on my Windows Server 2025. There must be an issue in the config file of AMP.

6

I’m also using WS25.

Seems to be an permissions issue.

After giving the users group full permission on the world folder its working for no obvious reason…

1 Like
7

Thank you so much. This was the solution for me as well. :wink:

1 Like
8

Just add the info from here:

This is the Solution.

1 Like
9

Why do you jump to that conclusion?

If perms are broken, it suggests that you did something with the worlds folder outside AMP, like maybe uploaded a world through Windows Explorer.

Everything works completely fine for me on Windows Server 2022, Windows 11 and Linux. An AMP dev also tested Windows Server 2025, and that was fine too.

10

I got to this conclusion, because everything else didn’t work. I followed exact all the instructions. Step by step. Nothing worked. Then I edited the permissions of the folder and everything was working like a charm.

And even if this would be done by windows explorer or anything else, it’s just one step to edit the permissions. Everything else are 5-6 steps. So this is a real shortcut. :wink: