TeamREPENTOGON / TeamREPENTOGON/REPENTOGON
Ambush Class Related Bugs
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 345
- Forks
- 51
- Avg merge
- 11h 2m
- Merged PRs (30d)
- 4
Description
A collection of bugs I have found while testing out the Ambush class.
SpawnWave Crashes in Blue Womb & Greed Mode
The game crashes when calling Ambush:SpawnWave() inside of Blue Womb or while playing Greed Mode. The crash log goes as follows:
No enemy wave found for ambush (difficulty: 1)
Lua stack trace:
[C](-1): SpawnWave
lua(1): ?
Caught exception, writing minidump...
Normally, calling this function in stages where there are no ambush rooms (Home, Chest, and Dark Room) will just spawn four attack flies. It would make sense to have this behavior be present when calling the function in Blue Womb/Greed Mode
SpawnBossRushWave Broken
This function does not work unless an ambush has been triggered at least once while the game is running.
StartChallenge Softlock
Calling this function outside of an ambush room will start the music and close all doors, but no enemies will spawn. This can softlock the player.
Greed Mode Crashes
All of the functions outlined above crashes the game when used in Greed/Greedier mode.
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 by reproducing Ambush:SpawnWave, SpawnBossRushWave, and StartChallenge in Blue Womb, Greed Mode, and Greedier mode, comparing them with stages that have no ambush rooms. Done means these calls no longer crash or softlock, SpawnWave provides the expected fallback behavior, and SpawnBossRushWave works without a prior ambush.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, lua
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100