geospiza-fortis / argonms-server Goto Github PK

Stopping the server often calls docker-compose down, which will remove the database instance. Sometimes this is useful when the database schemas change. However, it'd be convenient to have a persistent volume, so characters can persist in the testing environment.

• Update launch script to avoid database initialization if the tables already exist
• Add a named volume to the docker-compose configuration
• Update documentation to mention docker-compose down -v to drop the database state and reinitialize

Starting the environment with docker on windows will not copy over all the required files, such as WZ, scripts and bin.
On linux on the otherhand, it does copy over all the required files. I have no idea why this is happening.

While running the game server and loading XML dumps of WZ files, the process exits unexpectedly.

game_1    | Oct 30, 2020 9:31:47 PM argonms.common.net.internal.RemoteCenterSession connect
game_1    | FINE: Connected to Center server at center/172.29.0.6:8383
game_1    | Oct 30, 2020 9:31:47 PM argonms.game.GameServer registerCenter
game_1    | INFO: Center server registered.
game_1    | Loading String data...[WARNING]
game_1    | java.lang.NullPointerException
game_1    |     at argonms.game.GameServer.initializeData (GameServer.java:259)
game_1    |     at argonms.game.GameServer.access$300 (GameServer.java:74)
game_1    |     at argonms.game.GameServer$1.run (GameServer.java:303)
game_1    |     at java.lang.Thread.run (Thread.java:748)

This is because only MCDB and KVJ are supported data types for reading dumps.

This should be removed from the enum or documented clearly somewhere.