Blocklings Revival

Bug fix — Tasks screen crash

What was broken

Opening a task configuration (for example a fighting/hunting task) could crash the game with: java.lang.StackOverflowError: mouseReleased event handler This often happened on the Tasks screen when a task name was longer than 32 characters — common with some translated names (Italian, Dutch, Portuguese, etc.).

Cause

The task name text field could enter an infinite loop: setText → EditBox.setValue → responder → setText again. Minecraft's EditBox stores truncated text but notifies listeners with the full string, which retriggered the update forever.

What we fixed

• Added a guard in TextFieldControl to stop recursive text updates.
• Increased the task name field limit to 64 characters so long localized names are kept correctly.
• Fixed name field setup order on the Stats screen.
• Shared fix in the common module, so NeoForge and Fabric are both covered.

How to verify

1. Open a Blockling's Tasks screen.
2. Configure a combat task (Hunt, Retaliate, Attack Owner's Target, etc.).
3. Use a language with long task names, or rename a task with a long custom name.
4. The screen should open normally with no crash.