There should be no issues
there are of course always some issues haha
some entity files always have some problems
but for the most part it should be sweet
and nah, GUID’s dont affect anything, it will just complain
the GUID’s in the exe don’t match the files for some reason so yeah, not exactly sure what is going on
I’m still getting some entries that are not found:
Parsing JSON… using name mappings: NMS 3.3 WARNING: name mapping not found: 8iI WARNING: name mapping not found: ON4 WARNING: name mapping not found: Wv? WARNING: name mapping not found: ATe WARNING: name mapping not found: V1o WARNING: name mapping not found: s8f WARNING: name mapping not found: 1Zr WARNING: name mapping not found: Qyw WARNING: name mapping not found: LgS WARNING: name mapping not found: ?<V WARNING: name mapping not found: FQ3 Finished.
I could open a new issue with a new list, which is easy enough, but I’d rather wait on Monkeyman (MBINCompiler developer) as he was nice enough to create a tool for my wish to have those mappings automated. This list is planned to be included with future MBINC releases, which could then be referenced by GoatFungus (NMSSE) and anyone else needing it.
Note: NMSSE does function fine regardless of having the named mappings.
This is a pre-release for MBINCompiler now built with .net 5. This may require a newer version to be downloaded onto your computer to run, but hopefully there are no issues. If there are please raise them so we can address them.