magefree / magefree/mage

Server log indicates /fix command not in game thread

Open
#14,812 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
2.4k
Forks
940
Avg merge
2d 12h
Merged PRs (30d)
160

Description

> WARN 2026-03-04 03:05:20,755 FIX command was called for game 12dabfc4-096c-49e5-b74f-aa31cdfa180e by inuenc; players: inuenc (play), NOMASTER1021 (play); !!!NOT GAME THREAD!!! Two Player Duel; T9.M1; active: inuenc; stack: 0; FINISHED: Game is a draw =>[CALL - 428] GameController.attemptToFixGame
WARN 2026-03-04 03:05:20,756 FIX command result: active fix, priority fix =>[CALL - 428] GameController.attemptToFixGame

Four instances of FIX command being called and all logged this warning. Not sure if relevant.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the GameController.attemptToFixGame entry point named in the log and trace the /fix command calls that produce the "NOT GAME THREAD" warning. Reproduce the four logged calls if possible, then identify why the command is reported outside the game thread and verify that the warning no longer occurs for the affected scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.