Using a lead to connect a fence post to itself occassionally glitches out the player
ttpcodes opened this issue · 5 comments
Haven't been able to reproduce this consistently, but this happens fairly often (I'd say about 50% of the time?) and shouldn't be hard to get reproduced quickly (assuming it's not a problem on my end, sorry if that does happen to be the case!).
For the most part, tying a lead between fences seems to work just fine. It seems like tying a fence to itself also works about half the time (though I don't know if this is intentional or not because of this bug). The other half of the time though, even though the audio plays (and the subtitle gets displayed that the lead should be tied to that fence now), the lead still registers as being connected to the player, even though it should be tied by now. Right clicking the fence results in the lead dropping but the lead still being displayed as tied to the fence. Finally, the player doesn't seem to be able to do things like break blocks anymore until either disconnecting and reconnecting to the server (for multiplayer) or exiting and re-entering the world (for singleplayer).
I ran into this issue on Minecraft 1.16.5, with Minecraft Forge 36.0.42, AutoRegLib 1.6-47, and Quark r2.4-306. Other mods are listed in latest.log but have been disabled (AutoRegLib, Quark, and Minecraft Forge should be the only things running), and I purged the config file before attempting to reproduce this bug to make sure it wasn't some weird configuration problem.
im using 1.16.5, forge 36.1.0, when right clicking with the lead on mobs and posts, in the nether, it crashes 100% of the times
Hello! Quark's moved to 1.18 now-- unfortunately, this means that (unless your bug is critical and/or game-breaking), we're closing support for issues filed for versions prior to it (e.g. Quark on 1.16).
If your issue still occurs on 1.18, or if your issue happens to be rather critical (e.g. consistently crashing the game with no other mods present), please leave another note or open a new issue. Thanks for your cooperation!
I can confirm this issue to be present on Quark-r2.4-308 in Enigmaitca 6 v0.4.3
EnigmaticaModpacks/Enigmatica6#1622
