ggtracker / ggtracker/sc2reader

Units not marked as hallucinated

Open
#120 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
169
Forks
152
PR merge metrics
No merged PRs in 30d

Description

https://lotv.spawningtool.com/56283/

In this game, there are UnitBornEvents for a Colossus and Phoenix near the end of the game (back-calculated to 9:32) by Vibe. If you watch the game, Vibe didn't built either: both were hallucinated. However, neither were marked as hallucinations by sc2reader.

Interesting, these appear to be the anomaly because 2 earlier Phoenixes are correctly marked as hallucinations, so I'm not sure what the difference is.

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the replay at https://lotv.spawningtool.com/56283/ and inspect the UnitBornEvents near 9:32 for the Colossus and Phoenix. Compare them with the two earlier Phoenix events that are correctly marked as hallucinations. Done means both reported hallucinated units are identified consistently with the replay evidence.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.