isXander / isXander/Controlify

[Bug] Crashes game before launch with any mod that interacts with merchant screen/trading GUI

Open
#719 2 comments 0 reactions 1 assignee View on GitHub

@isXander is already working on this.

Since Nov 22, 2025.

bug
Dominant language
Java
Stars
341
Forks
97
Avg merge
1h
Merged PRs (30d)
1

Description

Current Behaviour

I've attached a crash log. As far as I can tell, Controlify crashes the game on startup whenever there's any mod that modifies the merchant screen?

This is the bit that I'm referring to:
Critical injection failure: Callback method accumulateScrolling in controlify.mixins.json:feature.screenop.vanilla.MerchantScreenMixin from mod controlify failed

Through process of elimination, I've found that it seems to be triggered by Adorn, Traveler's Backpacks, Cooking for Blockheads, Farmer's Delight, and several others, as any one of those being enabled causes the crash and they all share this injection failure. The issue is persistent across Steam OS and Windows 11 with any or no controller connected.

Expected Behaviour

I launch the game, and it launches with Controlify enabled.

Screenshots

No response

Reproduction Steps
  1. Install Controllify with MC v1.20.1 and Fabric
  2. Install any of the affected mods
  3. Attempt to launch the game
Logs
[crash-2025-11-22_03.24.05-client.txt](https://github.com/user-attachments/files/23688824/crash-2025-11-22_03.24.05-client.txt)
Mod Version

2.1.2

Controller

Steam Deck

Bluetooth
  • Yes
Operating System

Linux/SteamOS

ARM
  • Yes
Additional Information

No response

Just to make sure...
  • I have made sure I am using the latest version of Controlify for the latest version of Minecraft.
  • I have made sure there are no other issues describing the same problem on the issue tracker.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.