If you then write a generally useful "transform", you can learn how to submit what's called a "pull request" to offer your transform to Forge.įor the less ambitious: Whenever one of your mods encounters a srg name or poorly documented vanilla method, put your own comments into your own code. If you're especially ambitious, then you could study up on the scripting technology that decompiles Minecraft, injects Forge hooks etc. Once you've gained enough familiarity to speak up, then you might be able to offer up a useful suggestion.
First learn the customs for suggestions and contributions so you don't stumble in and bother some very busy volunteers with headaches they've already dismissed. To contribute your own advancement of Forge, you could start by locating the GIT repo and associated discussions. Comments are generally written on methods and fields injected by Forge, but Minecraft's vanilla elements are usually bereft. Each major revision of Forge seems to name several more methods and variables for ease of reading. These things are not done lightly, and they're not done "at home", but they are done by Forge's developers. I think the OP is asking for a more thorough debobfuscation (replacing srg names with meaningful names) as well as injecting comments along with hooks.
0 kommentar(er)
