TeamREPENTOGON / TeamREPENTOGON/REPENTOGON
MC_PRE_GRID_ROCK_DESTROY / MC_PRE_GRID_ENTITY_SPAWN_DROPS
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 345
- Forks
- 51
- Avg merge
- 11h 2m
- Merged PRs (30d)
- 4
Description
MC_PRE_GRID_ROCK_DESTROY with a table return [one of params being SpawnDrops] could've work but would probably be hard to implement?
A separate callback for MC_PRE_GRID_ENTITY_SPAWN_DROPS [with an ability to override drops] would've been fine?
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 reviewing how MC_PRE_GRID_ROCK_DESTROY and SpawnDrops are currently exposed and how callback returns are handled. The requested API shape is undecided, so first confirm whether the goal is a table return or a separate MC_PRE_GRID_ENTITY_SPAWN_DROPS callback; done should include a decided behavior and coverage for overriding drops.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, lua
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100