[1.16.5 Forge Bug]: startWithDragonChoice has no effect for dedicated servers
Drulikar opened this issue · 6 comments
■ Your Discord ID
Drathek#9503
■ Dragon Survival version
DragonSurvival_DragonEditor-1.16.5-0.10.4
■ Single game or server?
Forge Server or host
■ Do you delete old configs before writing a bug report?
I always delete configs
■ Do you play pure MC + DS and Geckolib or do you have some kind of modpack?
I only play with DS and Geckolib (Default)
■ Describe the bug
In dragonsurvival-common.toml setting: startWithDragonChoice = true
has no effect on a dedicated server. I made sure the setting is set both in server and the client. It only seems to affect singleplayer games. Tested on forge 36.2.29 and 36.2.34.
I will also note I tried having the server use an exact copy of a client's dragonsurvival-common.toml file (which successfully prompts user to become dragon in singleplayer), as well as having the server generate the config fresh, shuting it down, editing the value, and restarting.
■ To Reproduce
- Set startWithDragonChoice to true in dragonsurvival-common.toml both for a dedicated server, and a client.
- Connect to that server (127.0.0.1).
- Start game with no prompt to be a dragon.
■ Expected behavior
Like in singleplayer, player should be prompted on first spawn to become a dragon.
■ Crash Report
N/A
Server logs:
debug.log
latest.log
Client log:
latest.log
Wow, how many hidden functions are in our mod! I had already forgotten that someone had added this. For some reason I was sure we didn't have this feature