Bug Open

Spawner state does get written to the wrong file sometimes

#6602 opened by Unknown 11 months ago

Unknownreported this bug

Summary

I encountered these lines in my log file:

[15:56:53] [Server thread/WARN]: [MythicMobs] WARNING: HashCode collision detected when loading spawners.
[15:56:53] [Server thread/WARN]: [MythicMobs] Spawner 1 Hash: 1957253606 Type: spawner_Lehen_14_Natur_Dachs_003
[15:56:53] [Server thread/WARN]: [MythicMobs] Spawner 2 Hash: 1957253606 Type: spawner_Lehen_14_Natur_Dachs_003
[15:56:53] [Server thread/WARN]: [MythicMobs] We recommend changing one of these spawners' names to avoid issues resolving mob type.
[15:56:53] [Server thread/WARN]: [MythicMobs] WARNING: HashCode collision detected when loading spawners.
[15:56:53] [Server thread/WARN]: [MythicMobs] Spawner 1 Hash: 1406897784 Type: spawner_Lehen_64_Natur_Feldhase_001
[15:56:53] [Server thread/WARN]: [MythicMobs] Spawner 2 Hash: 1406897784 Type: spawner_Lehen_64_Natur_Feldhase_001

I did not create theses spawners twice, but for some reason the content of the spawner file spawner_Lehen_14_Natur_Dachs_003 got written in another file, than the one for the spawner spawner_Lehen_14_Natur_Dachs_003.

As you can see by the command output, the content is actually present in two files:

minecraft@ottonien-2:/opt/minecraft/test/plugins/MythicMobs/Spawners$ grep "spawner_Lehen_14_Natur_Dachs_003" *.yml
spawner_Lehen_14_Natur_Dachs_003.yml:spawner_Lehen_14_Natur_Dachs_003:
spawner_Lehen_5_Natur_Feldhase_002.yml:spawner_Lehen_14_Natur_Dachs_003:

Steps to reproduce

Create some spawners and wait.

Current behavior

We are loosing spawners, since some files do get overwritten.

Intended correct behavior

I want the spawner state to get written to the correct file.

Server log file

Can provide that if needed.

Debug log snippet

Can provide that if needed.

Proposed fixes

See above.

Unknowncommented

the steps to reproduce are super generic, can you be more specific? or is it literally make any 2 spawners, and wait?

Unknowncommented

I'm sorry, but thats our setup. But this bug is making the plugin unusable for us, while it is crucial to have it at the same time. I am willing to help investigate. Do you have any idea where this logic is located in the code and where I could have a closer look at? Thanks!

Sign in to join the discussion.