Migrating between versions

Quandrastorm

I know how source controll systems work but i was wondering how do other modders / mods do this?
if a new version of NS2 is released its likely a lot of current mods break as its build upon the code of the old version

ofcourse i dont want to redo each change manuely, automerging probely works best here.

however i dont thier main code as a ropository.

MCMLXXXIV

I have a local Git version control repository on my PC which just hosts the 'lua' folder. Whenever a new version of NS2 comes out I make a new commit on it and it allows me to see a log of what has changed on each version of NS2 (very handy for debugging stuff when a new version comes out).

In terms of keeping your code maintained in the long-term, by far the easiest way to do it is to make sure to use hooks, (either fsfod's or sewlek's framework) or to change as few files as possible so that you don't need to keep updating often.

fsfod

Previous build's Lua files are zipped up in the "builds" folder if you want to create repository to merge you modified files into.

Quandrastorm

hmm yeh i was thiking of creating my own git repo t host the clean lua source, and put by own code in a different brance and just keep rebaseing the changes.

but hooking is also a nice idea i didnt consider before

lwf

Anyone got a copy of the build 235 code you could zip up and send me?

UWE managed to ship the some half updated frankenbuild 236 in both build_235.zip and build_236.zip, which I relied on to find if anything has been broken in mods...

Edit: Got it, thanks.