magefree / magefree/mage

SERVER - game error

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

Description

Error type: SERVER - game error

Client version: 1.4.56-V3 (build: 2025-02-09 16:02)
Java version: 1.8.0_201
Default charset: UTF-8

Game error occurred:

java.lang.IllegalStateException: Wrong code usage: method must find real card name, but found nothing
Server version: 1.4.56-V3 (build: 2025-02-09 16:02)
Stack trace:
mage.players.PlayerImpl.moveCardToExileWithInfo(PlayerImpl.java:5235)
mage.players.PlayerImpl.moveCardsToExile(PlayerImpl.java:5013)
mage.abilities.effects.common.ExileTargetEffect.apply(ExileTargetEffect.java:122)
mage.abilities.AbilityImpl.resolveMode(AbilityImpl.java:226)
mage.abilities.AbilityImpl.resolve(AbilityImpl.java:210)
mage.abilities.TriggeredAbilityImpl.resolve(TriggeredAbilityImpl.java:254)
mage.game.stack.StackAbility.resolve(StackAbility.java:85)
mage.game.GameImpl.resolve(GameImpl.java:1815)
mage.game.GameImpl.playPriority(GameImpl.java:1738)
mage.game.turn.Step.priority(Step.java:73)
mage.game.turn.Phase.playStep(Phase.java:205)
mage.game.turn.EndPhase.playStep(EndPhase.java:60)
mage.game.turn.Phase.play(Phase.java:91)
mage.game.turn.Turn.play(Turn.java:141)
mage.game.GameImpl.playTurn(GameImpl.java:1157)
mage.game.GameImpl.play(GameImpl.java:1064)
mage.game.GameImpl.start(GameImpl.java:1040)
mage.server.game.GameWorker.call(GameWorker.java:35)
mage.server.game.GameWorker.call(GameWorker.java:16)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with mage.players.PlayerImpl.java at lines 5235 and 5013, then follow the call into mage.abilities.effects.common.ExileTargetEffect.java at line 122. Use the reported stack trace and server/client versions to investigate the failing exile operation; done means identifying a reproducible cause and confirming the server no longer raises this error.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.