Dragon Survival [Forge]

Dragon Survival [Forge]

685k Downloads

[1.19.2 Bug]: Getting turned to human from dragon when reconnecting to a server, teleporting, or dying.

Lyrth opened this issue · 0 comments

commented

■ Your Discord ID or other contacts

lyrth

■ Dragon Survival version

DragonSurvival-1.19.2-02.03.2024_stable

■ Single game or server?

Host site

■ Describe the bug

Getting turned to human from dragon when reconnecting to a server, teleporting (across dimensions - using Waystones mod objects), or dying (and respawning).

Most of the time, I am shown the "Choose a Dragon Species" menu after turning into a human when doing any of the above.

Exiting the species select menu will make the player human. Either of the two happens:

  • Disconnecting from the server quick enough and rejoining will restore dragon form and progress. Used to happen before, but does not anymore. Dev note: in this state, the dragon stats in the player NBT data (type/age/skills/presets/etc under ForgeCaps/dragonsurvival:playerstatehandler) are KEPT intact.
  • Player will retain human form, and still will even with reconnect/death/teleport. Dev note: in this state, dragon stats in player NBT data are CLEARED (type: none, cave/forest/seaSize are 0, skinPreset also reset to all None).

Selecting a species and saving (cave dragon in my case) will OVERWRITE my dragon age/skills/etc. with a newborn's. Not good either.

A player data backup was made back when I have the proper dragon form, age, and progress. Player data NBT looks correct and fine too. That same backup is then used to replace my player data on the server, BUT when I join the server, it often makes me join as a human player. On the other hand, another player using my same exact player data (from the backup) on their character works fine for them even after multiple reconnects.

I have tried using a different launcher (curseforge, multimc), different and fresh install location too. Problem persists.

■ Crash Report File and Logs

Being turned human happened as soon as the chat entry NO AM HUMAN AGAIN appears in the log, both client and server. No crash.

Client log

Server log