Dragon Survival [Forge]

Dragon Survival [Forge]

685k Downloads

[1.20.1 Bug]: Progress erased after joining a server / switching dimensions

TrudeEH opened this issue · 3 comments

commented

■ Your Discord ID or other contacts

ehtrude

■ Dragon Survival version

DragonSurvival-1.20.1-27.06.2024-all.jar

■ Forge/Neoforge version

47.3.0

■ Single game or server?

Local network (LAN, Hamachi, etc.)

■ Describe the bug

When the bug happens, a player will either lose all their progress with the dragon survival mod permanently, or temporarily until switching dimensions or rejoining. The issue seems to happen randomly, and all progress is reset, including equipped tools in their respective slots, ability upgrades and age.
The issue happen in both my own test servers, LAN worlds and servers.

Possible triggers for the bug:

  • Switching to any dimension or from any dimension, vanilla and modded.
  • Joining a server

This is exactly what happens to me when I encounter this error:

  1. I spawn as a human
  2. I am prompted to choose a dragon race
  3. If I click away or press ESC, I will remain human, if not, the dragon race selected will be applied.
  4. All progress is lost, I will be a "newborn" again and have no abilities. Inventory and EXP remains instact.
  5. I will sometimes get killed immediately, but most of the time nothing more happens. Sometimes switching dimensions again restores the old progress, often it never does.

■ Crash Report File and Logs

No response

commented

From what I've experienced, the problem occurs when different methods are used to connect to a DS server.

When connecting to my server via the 'Finding LAN Servers,' my Dragon Survival progress gets reset, while connecting via the Add Server button doesn't.

One of my players has incurred this issue multiple times, and upon investigation, I discovered they were using a VPN. This is a theory, and I'd like to add that I am not officially affiliated with Dragon Survival.

commented

For me, this issue occurs even without a VPN or any proxy, and using the same method to connect every time. Older versions don't seem to be affected by this bug at all.