1.15.2 - Mouse inputs being eaten
Tawling opened this issue ยท 9 comments
Litematica occasionally eats mouse inputs for both left and right click. I can't tell the specific cause, though it seems that it might be when an input is performed while focus is being moved to another block or entity. This applies to both breaking and placing blocks, as well as attacking mobs. Sometimes the input will simply be eaten. It is most obvious when spam clicking in creative mode to break or place blocks, and it doesn't appear to have a pattern to when it happens.
Which litematica and malilib are you using? And if you have other mods, can you send a list?
I've just narrowed it down to an interaction between litematica and mousewheelie. Removing either of the two from my mod list fixes the issue. This is the minimum mod list I have found that causes the bug:
Jumploader is only because I'm running fabric through the Twitch client, so that can be disregarded.
the issue is mousewheelie. I used to have the same problem, that my input from mouse and kb was being eaten, and by trial and error I found the culprit was mousewheelie. imo, delete it, and dload masa's itemscroller instead. hope this helped
That is good to know. Odd that it only happens with Litematica though.
I actually don't use mousewheelie for the item scrolling, but actually for inventory sorting. Is there a different fabric mod that allows for inventory sorting? I wasn't able to find one.
i never use inventory sorters, but afaik you can do it with item scroller (masa, fabric) or tweakeroo (also masa, fabric) i'm 99% that one of them has it, as i know i saw it somewhere in the config menu but i can't remember exactly. my bet is that it's on item scroller.
There is no item sorting yet, but it's on my TODO list for Item Scroller.
This issue was reported a while back on CurseForge, and I tracked it down to the Amecs mod. More info here: https://www.curseforge.com/minecraft/mc-mods/litematica?comment=643
I have already changed how this part of the code works in the main development version on 1.12.2, so this issue should be fixed once the next merge happens. I could also take a look if I can also temporarily fix it before then, as I still don't know when I'll have everything ready for the next merge.
Great thank you! It's not dire, I can find other solutions. Just making sure it was reported. :) Great work on all the mods.
