TeamREPENTOGON / TeamREPENTOGON/REPENTOGON
[META] Online coop checklist
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 345
- Forks
- 51
- Avg merge
- 11h 2m
- Merged PRs (30d)
- 4
Description
Existing issues from REP- discovered while working on REP+
- Isaac.Get/SetDwmWindowAttribute - Set->Get returns weird values
Known issues in REP+
- Co-op menu must be sufficiently blocked off while REPENTOGON is active (mostly done, need to block invitations, maybe other stuff?)
- Isaac.SetIcon can break if called too many times
- Decoration grids are not spawning naturally (likely related to grid entity spawn patches)
REP+ issues that might get fixed by nicalis
- https://github.com/epfly6/RepentanceAPIIssueTracker/issues/599
- https://github.com/epfly6/RepentanceAPIIssueTracker/issues/598
Things that could maybe use some more fleshed out tests
Honestly, if you feel like adding some tests for ANYTHING, especially rgon features, go for it. But in particular there were a few things I thought could be worth a look for writing tests, either due to complexity or awkwardness in actually writing tests for it.
- GenericPrompt
- Custom Item Pools
- LootList
- Ambush (weird to set up a testable state mid-test)
- EntitiesSaveState / GridEntityDesc (savestate related)
- ASM patch etc stuff if not covered yet, like ASMCallbacks/ASMXMLItem/CardsExtras
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
Treat this as a tracking checklist rather than a single task. Read the listed REP and REP+ items, then inspect the linked TestMod repository for the named test areas such as GenericPrompt, Custom Item Pools, LootList, and savestate coverage. Before starting, choose one item and define its affected behavior and passing test; done means that item is implemented or tested and checked off.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, lua
- Domain
- game-dev, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100