Scenario 08 atlantis stuck in mission state
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 869
- Forks
- 222
- Avg merge
- 18h 33m
- Merged PRs (30d)
- 1
Description
I rechecked the code and it looks like we stuck here, because we never triggered it:
https://github.com/daid/EmptyEpsilon/blob/1716e22743101136c289947ef8e267c520411c3e/scripts/scenario_08_atlantis.lua#L413-L419
Because we went through the wormhole, in to the territory with a lot of Kraylor:
https://github.com/daid/EmptyEpsilon/blob/1716e22743101136c289947ef8e267c520411c3e/scripts/scenario_08_atlantis.lua#L403-L409
And then we headed down/south for about 25-30U to get out of the enemy territory. Then continue to fly to B20 to reach the jump carrier. After we were next to it we could dock it at (B20), but it did nothing. Headed back to the HQ, still no option to do something.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in scripts/scenario_08_atlantis.lua, examining the state logic around lines 403-419 and the reported wormhole, Kraylor-territory, B20 docking, and HQ route. Reproduce the route if possible and trace why the mission remains stuck; done means the expected next mission interaction becomes available after docking or returning to HQ.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100