Silent Gear Elytra right-click equipping to curios slot issue similar to Issues #432 and #435
Vulp-OS opened this issue ยท 4 comments
Versions
- Silent Gear:1.20.1-3.5.0
- Silent's Gems: N/A
- Silent Lib: 1.20.1-8.0.0
- Forge: 47.1.3
- Modpack: All the Mods 9 0.0.45
- Optifine Installed: No
- Curios API (Forge):5.2.0-beta.3
- Caelus API (Forge):3.1.0
Expected Behavior
After crafting an Elytra from Silent Gear, right clicking it in inventory should auto-equip it to a supported slot (Chest Armor or Curios Back Slot) without issue and be useable.
Actual Behavior
After crafting an Elytra from Silent Gear, right clicking it in inventory immediately disconnects the player that attempted to auto-equip it. The player can no longer reconnect to the server.
In single player, the game crashes entirely.
Links/Images
Steps to Reproduce the Problem
- Create a minimal modpack setup based on Minecraft 1.20.1 and Forge 47.1.3 (Other versions not tested):
- Silent Gear, Silent Lib, Curios API, Caelus API (See versions above)
- Specifically, the silent gear must be crafted, it cannot be gifted without crafting via server commands (at least in my brief testing).
I used the following sequence on a crafting table:
For the Elytra Part:
Craft | ing | Table |
---|---|---|
Silent Gear Elytra Blueprint | White Wool | White Wool |
White Wool | White Wool | White Wool |
White Wool | Empty | Empty |
For the Binding:
Craft | ing | Table |
---|---|---|
Silent Gear Binding Blueprint | String | Empty |
Empty | Empty | Empty |
Empty | Empty | Empty |
- Combine in crafting table
- Right click in inventory.
- Crash/Disconnect
The workaround to allow players to access their worlds again as outlined here works for multiplayer worlds as well.
To work around this issue, you can use an NBT Editor like this one to edit the player's .dat file to remove the silentgear elytra from the impacted player's curio back slot.
This is great for allowing people to access their worlds again, but it is not a fix for the above issue.
Just saw that #611 also covers this issue. I didn't see it before submitting my issue.
At a quick glance the issue appears to be that the mapped name instead of SRG name (f_20937_
) is provided.