Controlify currently unusable (due to inability to break blocks)
HasuMigu opened this issue · 11 comments
Describe the bug
Currently as it stands, Controlify has a concurrent issue regarding the inability to hold buttons. I have manually deleted the .json file for controlify as having both steam-input and NS registered causes conflict which is also an issue that the owner of controlify seems aware about. I also want to disclose that switching buttons somewhere else such as the face buttons doesn't solve this issue. Midnight Controls, despite feeling like a hack still does what it needs to do and I hope this issue will get fixed soon. This open issue describes the situation as the most similar to mine despite me using steam-input or Linux's Nintendo Switch controller drivers.
The issue on controlify's repo: isXander/Controlify#74
isXander/Controlify#106
Modpack version
5.1.0-beta.3
Launcher
Prism Launcher
Other things
- I updated FO to a newer version (mention, what version to what version)
- I added/removed some mods or resource packs (mention, which ones)
Additional context
No response
On 5.1.0-beta.7, the oppposite scenario happens. My player cannot stop breaking blocks. I also tested this with Nintendo Switch Linux or Steam Input.
Alright, please comment on the original issue with logs, video or anything else applicable.
I have tested it again on the newest version of Fabulously Optimized, the issue went back to the former -- not being able to break blocks
I have tested this on the steam deck and currently in a party as I'm making this comment, I'll provide logs as soon as I can and report this.
The original issue got closed as it was technically a fix to the issue listed, however as expected a new issue report soon followed.
Issue page on Controlify repo:
isXander/Controlify#106
Too lazy to update FO today but please try v1.4.2: https://www.curseforge.com/minecraft/mc-mods/controlify/files/4635546
Nothing changed in version 1.4.2+1.20 in regards to this issue, the issue is still present.
The bug fix doesn't fix the issue, it does fix the the use being activated twice in the same tick. There was an older version (1.3.2) that was working for someone but I have yet to test that for myself plus it's likely missing many features.