TeamREPENTOGON / TeamREPENTOGON/REPENTOGON
More new room callbacks
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 345
- Forks
- 51
- Avg merge
- 11h 2m
- Merged PRs (30d)
- 4
Description
The current POST_NEW_ROOM callback runs after all entities in a room layout have both been spawned AND have run their first update, which can lead to many inconveniences.
Variants of the NEW_ROOM callback which would be useful would be:
-One which runs BEFORE any room entities are spawned
-One which runs after all room entities are spawned BUT before any of them have run their first update (if possible)
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 locating the POST_NEW_ROOM callback implementation and tracing the room entity spawn and first-update lifecycle. Determine whether callback points can be exposed before spawning and after spawning but before the first update; done means the requested timing variants are available without changing the existing callback's behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100