TroubleshootingFix it

Reporting bugs

How to file a bug report that can actually be acted on, and where to file it.

2 min readInputBooster 4.1.2-alphaMinecraft 26.2 / 26.3

A good report is short. The log file and six lines of context are worth more than a paragraph of description.

Where to file

Issues go to the project repository:

External referenceInputBooster issue trackerOpen externally

InputBooster issue tracker

Open a bug report here. Include the log, the versions and the exact reproduction steps.

For a security issue, use the process in the repository's SECURITY.md rather than a public issue.

What to include

1. The versions

Field	Where to find it
Minecraft version	The launcher
Loader and loader version	The launcher
InputBooster version	The jar name, or the `Starting v...` log line
Java version	`java -version`

2. The log

Attach latest.log, or paste the lines between the mod starting and the problem. The lines that matter most:

Line	Why
`Starting v...`	Confirms the version
`All client hooks present.` / `Missing vanilla method(s): ...`	Says whether the mixins applied
`Screen hooks: setScreenAndShow=..., setScreen=...`	Says whether the screen router applied
`Config entries reset to defaults (...)`	Says whether the config was reset
`[Compat] Keyboard/mouse event hooks are live.`	Says whether the event source works
Any `[SafeMode]` line	Says whether a module was disabled
Any `failed:` line	The exception that was thrown

3. The reproduction

Numbered steps that someone else can follow. The issue template asks for exactly this:

text

To Reproduce
1. Launch Minecraft 26.3 with Fabric
2. Join a singleplayer world
3. Open the InputBooster settings screen
4. Toggle the overlay mode
5. See the error

4. The expected behaviour

One sentence. "The overlay should stay visible when F3 is closed."

5. The other mods

List them. The compatibility detector only knows six input mods by name, so an unlisted mod is the most likely explanation for a strange input problem.

6. Screenshots or a short clip

Only for a visual or timing problem. A clip of a missed input is far more useful than a description of one.

A good example

text

**Describe the bug**
Typing a space in chat jumps my character, even with the InputBooster
options button open.
 
**To Reproduce**
1. Minecraft 26.3, Fabric Loader 0.19.5, Fabric API 0.161.0+26.3
2. InputBooster 4.1.2-alpha-fabric-mc263.jar
3. Java 25
4. Join a singleplayer world
5. Press T to open chat, type a space
6. The player jumps
 
**Expected behaviour**
The space should be typed and nothing else should happen.
 
**Versions**
OS: Windows 11
Minecraft: 26.3
Loader: Fabric 0.19.5
InputBooster: 4.1.2-alpha-fabric-mc263.jar
Java: 25
Other mods: sodium 0.6.9, iris 1.7.3
 
**Log lines**
[Mixin] All client hooks present.
[Mixin] Screen hooks: setScreenAndShow=false, setScreen=false

Before you file

Check	Why
Is it a known issue?	The common issues page covers the frequent ones
Is it a published jar that is known to crash?	`4.0.2-stable`, `4.1.0-alpha`, `3.1.2` and `3.1.3` all crash at launch
Does the log show `Fatal init error!`?	That is a mod bug — include the stack trace
Does it reproduce with other mods removed?	Otherwise it may be an interaction, and the report needs the other mods named
Is the setting one of the five inert ones?	If it is, it is a known limitation, not a regression

What happens next

The maintainer reads the log and the versions. A report with the log and the reproduction usually gets a diagnosis on its first reply; a report without them usually gets a request for the log.

Contributing a fix

If you want to fix it yourself, the contributing guide describes the branch, test and pull request expectations, and the code conventions describe the rules the mixin code has to follow.