+- Renegade Projects Network Forums (https://forums.renegadeprojects.com)
+-- Forum: General Forums (https://forums.renegadeprojects.com/forumdisplay.php?fid=1)
+--- Forum: The Renegade Inn (https://forums.renegadeprojects.com/forumdisplay.php?fid=2)
+--- Thread: APOC: "make a community patch for YR, we might endorse it." (/showthread.php?tid=941)
Pages:
1
2
RE: APOC: "make a community patch for YR, we might endorse it." - Banshee - 14.02.2008
Bob, that still wouldn't affect RPCE, because it doesn't change the position of the tags, functions, classes, etc.... Changing from 1.001 to 1.002 is to modify one byte with the hex value 31 to 32. If RPCE is compatible with YR before this change, it would be compatible with it after the change as well.
RE: APOC: "make a community patch for YR, we might endorse it." - Marshall - 14.02.2008
Ummm... no, because the file checksum will have changed - anything that checks this would have trouble. Launch Base uses it, and I'm pretty sure the patching software that RP-Gen uses uses it.
Changing the exe for the sake of the version number is not a good idea, imo.
RE: APOC: "make a community patch for YR, we might endorse it." - Banshee - 14.02.2008
They'll change it, if a new version goes live.
RE: APOC: "make a community patch for YR, we might endorse it." - Blade - 15.02.2008
Why will it be a problem in all honesty? TFD exe is already slightly different so the patcher has to know about 2 possible exe files already.
RE: APOC: "make a community patch for YR, we might endorse it." - Marshall - 15.02.2008
Fair point, wasn't thinking.
RE: APOC: "make a community patch for YR, we might endorse it." - Renegade - 16.02.2008
In the end, one could just change the version string to say "Community Patched" instead of "Version" or whatever it is - then you'd have "Community Patched 1.001" in the menu, which is the most honest statement anyway.