Describe the bug

A player on my new Survive The Nether pack hit the 'n' key and subsequently crashed.

Client Crash Report

https://pastebin.com/buCcB4f1

@kreezxil do you have "legacybuttonids" enabled in the mod config?
The full game log would be good, can you please send me the full log file from .minecraft/mods too?

@T0uchMeSenpai Most likely yes. It opens a menu, so I assume some of the buttons of the voxelmap menu are added in a weird way or something.

Will check this later! :)

It's not a conflict with voxelmap, i've remapped voxelmaps keys and it's still happening.

new client crash report:
https://gist.github.com/81137f8ea53e9ea4ecf91cbc1844c8dd

new client latest.log:
https://gist.github.com/158ba68e8f5d9fa77f4f5731edd09012

new client debug.log:
https://gist.github.com/408bff70b2e20814eadb525f56058e26

and we use a launcher such as GDL so it doesn't even launch the packs from that location.

the config.txt:
https://gist.github.com/f72dc1f1abf3d99ed4c55b4787dd4a3a

you said legacy ids, is that the source of the issue here?

The n key is assigned to voxelmap's waypoint menu. Based on the crash report (and consequently the latest.log file), I suspect a problematic interaction between FancyMenu and voxelmap. I will do a couple tests and see if there is anything to add.

ok, i turned off using legacy ids and the crashes went away

Screen name: com.mamiyaotaru.voxelmap.gui.GuiAddWaypoint

It's crashing in a voxelmap GUI, I’m pretty sure it’s a conflict with it :D

I just asked if you’re using legacy IDs, because the crash happens in a method related to it. Wasn’t sure if not using the legacy system would fix it ^^

I'm working on a system to manually exclude specific menus from FM (as mod user) to fix this kind of conflict without the need to update the mod.

@kreezxil Does excluding voxelmap menus fixed your issue?

just 2 comments back I said that turning off legacy ids worked. #76 (comment)