Bug Closed · Resolved

Error Report Which File

#1036 opened by Unknown 5 years ago

Unknownreported this bug

Summary Tell a user which file their Error is occurring in, for example spawners with this error do not: [08:10:37 WARN]: [MythicMobs] Mob 1 Hash: 609953211 Type: VOID_HEART [08:10:37 WARN]: [MythicMobs] Mob 2 Hash: 609953211 Type: VOID_HEART [08:10:37 WARN]: [MythicMobs] WARNING: HashCode collision detected when loading mobs.

So i have to sort through every spawner file to find which is messed up. Usage Easily identify where your error is located, rather than having to manually search through hundreds of files

Unknowncommented

This error occurs when you have 2 mythic mobs with the same internal name, and doesnt have anything to do with spawners. It would be in your mobs.yml files. Example: I set 2 mobs to the name TestSchematics1 and I get these errors: [14:20:04 WARN]: [MythicMobs] WARNING: HashCode collision detected when loading mobs. [14:20:04 WARN]: [MythicMobs] Mob 1 Hash: 1647048217 Type: TestSchematics1 [14:20:04 WARN]: [MythicMobs] Mob 2 Hash: 1647048217 Type: TestSchematics1 [14:20:04 WARN]: [MythicMobs] We recommend changing one of these mobs' internal name to avoid issues resolving mob type.

Unknowncommented

I appreciate the help with the error itself, but my overall suggestion is to add more context for errors, which will help users locate where the issue takes place and easily fix it.

I've had a similar error with Spawners, which made me go through a ton of my spawners to figure out which had the same name.

Unknowncommented

I have submitted this as issue #100 in a format that is compliant with what we request. In the future please fill out suggestion forms in their entirety.

Sign in to join the discussion.