Go to file
pegasust 6ff22c6d47 feat: add ilspy dump for ror2.dll 2024-10-04 00:26:37 -07:00
ilspy_dump feat: add ilspy dump for ror2.dll 2024-10-04 00:26:37 -07:00
scripts init 2024-10-04 00:26:18 -07:00
.gitignore init 2024-10-04 00:26:18 -07:00
README.md init 2024-10-04 00:26:18 -07:00

README.md

R2mods

Knowledge dumping on ror2 modding community - how I can improve everything, as well as keeping all of the code (or disassembled) dump in one place - tracking with a modpack that me and my frenns are playing, duped choncc

Merging codebase across multiple sources

This is the ultimate test for Git knowledge, you can't just go and submodule everything. I'll maintain this along with choncc and dump as many versions of the mods being tracked

Disassemblies

Use this IN CONJUNCTION WITH original code if available. This is mostly because code quality from conventional codebase is no simpler than the disassembled code (surprisingly?).

Will go onto ilspy_dump, before we figure out how to use ilspycmd, we'll just use the GUI.

For now, no naming convention yet, I'll try to export both a singular C# file AND the whole C# project

  • ror2.dll is in //SteamLibrary/steamapps/common/Risk\ of\ Rain\ 2/Risk\ of\ Rain\ 2_Data/Managed/ror2.dll

R2 profile footprint

Per the code (TODO: ADD SOURCEGRAPH QUERY AND CODE HERE), it only contain mod manifests and configurations, very little non-configuration files are in here because file extensions are hard-coded for filter during profile sharing process.

Locations of mod profiles