Forum

I'm sorry, but it's more or less the same story this time around.  I'm still going to school (full time graduate school... going on 7 years of college), but am also working part time to pay the bills, as well as the usual compliment of projects.  I can certainly try and remember specifics of the original builds, but I haven't had a UE2.5 engine game installed for quite some time.

That all being said, If you're willing to dive into the source code there may be a couple of hints I can offer:
Unrealscript is very similar to C++ and Java in syntax, if you can code in either, it's not difficult to pick up.  The class structure of the content is basically textbook examples of object oriented programming.  I don't believe the online documentation of the game's scripts is still available where I was using it, but if you're going to code, use the editor to extract all of the Unrealscript files into a directory and use them as a reference.  If you're working with GoodKarma, it may be worth exporting UT2004's scripts, since that's what it was designed to work with.  I also liked using the Context editor... it's basically just notepad, but you can download a highlighter plugin for Unrealscript which makes things visually easier to keep track of.  You can also link run commands to the function keys, so you can compile a mod and capture the output of the compiler all in the same window.

With UE2.5, and quite annoyingly, the physics are done externally through the Karma engine (whereas the collision detection is done entirely in the game engine...), so there is relatively little control you actually have in Unrealscript.  I used the KActor class (which I could verify worked in online play) as the basis for my work and at least once I had to go back to the original and paste in my added content carefully because it had stopped working.  For debugging it's an absolute must to run a dedicated server on your machine, then connect to that server with your client - even when it seems to be working in single player, the whole point is that it gets replicated over the server to all of the clients.  I think my earliest releases actually didn't work online because I wasn't testing this way and didn't know.

Take a look at the different releases and changelogs, to see which of the added features you want to be able to use - then compare the source files.  Generally, you can tell what chunks of code were added, and if you can isolate them, you can add that functionality to your own existing KActor class (or whatever your working base is) without having to tackle the whole mod.  I don't know what version of the engine your current build is, but it is entirely possible that my existing code will not function properly on it, so I would stick to working code and then try to splice in the extra functionality.

Finally... if you can find an old build of Killing Floor as a mod (before it was a separate game), for at least a little while they used GoodKarma for their physics stuff as well.  He may have moved on to something else (or even a different engine), but the mod's developer had continued using GoodKarma into the commercial stage, so there should be probably close to a year worth of Killing Floor builds (as a mod for UT2004) that have working versions of GoodKarma which may have different functionality or may be more of what you're looking for.  Generally the editor can unpack .u engine files into their Unrealscript (.uc) components, so if you can find the .u files for the mod, you can probably get the source code from them, even if it wasn't explicitly released.

Good luck, and while I don't have time to be a legitimate developer, I can certainly take some sporadic time to answer questions.  I don't know if you have the files the original email mentions, but if you need another copy, I think they've moved to here:
http://www.medpants.com/pages/projects/GoodKarma/GoodKarma.zip

-Jon