MemoryKey - expose all available keys from NMS registry
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Is your feature request related to a problem?
Yes, as it currently stands Bukkit MemoryKey only provides a small handful of the current memory keys available from Minecraft.
It appears the Registry.MEMORY_MODULE_TYPE is hard coded to return MemoryKey.values() rather than actually grabbing from the Minecraft registry.
Describe the solution you'd like.
I would like to see the MemoryKey and registry re-written to actually return things from Minecraft rather than a small percentage of hard coded values.
Describe alternatives you've considered.
Other than grabbing from an NMS registry, nothing I can think of.
Other
No response
Contributor guide
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 Bukkit MemoryKey implementation and Registry.MEMORY_MODULE_TYPE mentioned in the issue, then compare their current behavior with the Minecraft NMS memory registry. Determine how registry-backed keys are exposed through the Bukkit API and identify relevant existing tests or registry tests. Done means the API exposes all available Minecraft memory keys rather than only the hard-coded subset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100