6 new categories and 72 new items added to the shop!Fake forum EC for posting doubled everywhere to help pay for them!
0 Members and 1 Guest are viewing this topic.
The only way these fixes could hurt maintainability are if they 1) confuse your reverse engineering tools too much; 2) break the boundaries of functions you want to hijack (unlikely). Including these fixes is likely to improve maintainability by removing bugs from the code base and so reducing bug reports etc.Scient and others on the bugfixing team did good work over many years on SMACX. It seems pretty daft to me not to build on that work.
Why not load your code as a dll and only modify the stuff you want to? We can hack the .exe to load a common loader dll that will then load all mod dlls in the directory (perhaps identified in a text file?).That's roughly how PRACX works and would allow us to make these binary changes more easily composable and means you don't need to include anyone else's work in your project if you don't want to. It also means you don't need to distribute the updated terran binaries, just your dll, the loader dll and a script to patch terran.exe to use the loader.
> Why you didn't choose Ytzi's patch as a base for your work ?It's just hard to see what those important bugfixes might be in Yitzi's patch.
It's just hard to see what those important bugfixes might be in Yitzi's patch.
Page created in 0.485 seconds with 52 queries.