Does anyone have info on how the Rust.opj file is maintained and updated for each Rust server patch? I know we can use the patcher to incredmentally add new hooks of our own and review the existing hooks by loading the file into the patcher GUI, but is there any info available or reference to another tool on how the file is maintained as patches are released. With so many hooks, I cannot see how this file is being maintained by hand and think there is probably a tool or script somewhere that helps. TIA
How is the opj file created and updated?Solved
Oxide Patcher edits the file
Yeah I get that part, but I can't really believe after each patch, someone goes into the patcher and verifies each hook by hand; there are hundreds. Plus I see the Rust.opj file changes in at least few lines almost every patch, so this is a common operation before a new Oxide/uMod version is released
It shows the ones that were modified IIRC.
The majority of hooks are not changed each update, but ones that are affected by changes in Rust are flagged for someone to review and adjust as necessary.
So they use the OxidePatcher GUI alone to do that and not some other external tool or script? I'm only really asking because I'm interested in the MSIL stuff and how to best keep those kinds of injections organized as a source application changes
Yes, Calytic and I generally only use the patcher. A .NET decompiler can also be useful if you haven't memorized the previous index location as well.KolymaSo they use the OxidePatcher GUI alone to do that and not some other external tool or script? I'm only really asking because I'm interested in the MSIL stuff and how to best keep those kinds of injections organized as a source application changes
Thanks. That's really helpful info. You guys do a great job of keeping that thing current. Kudos
Locked automatically