cgame
- Thread starter RedEntry
- Start date
There are patches for mod loading that remove this restriction, fairplay the anticheat had it aswell. This is dinks mod a clientside mod widely used in 2012 by everyone. Looking inside the mod, I see a cgame file present, it means there is working code for demo/v1.02t cgame pk3 compilation, assuming someone made some changes in the existing v1.00 SDK to make it work with demo, im looking for that. I tried compiling with v1.03 sdk aswell but I get version mismatch.
Was wondering if any of the oldschool modders could tell me how to accomplish this, because I think this knowledge is going down with them, and since its possible to create mods for Silver, Gold, why not for demo?
No official SDK was (quite rightfully so) ever released for MP Test (demo). During 1fx. Mod development, I reverse engineered support for it, taking the official 1.00 SDK as starting point. This effort ended up successful, being named OpenDEMO, making 1fx. Mod 0.82 compatible with demo as well.
I only reverse engineered the game module however, there is no support for the cgame. Seeing as many common structs overlap, you could take that code as a starting point. It is open source and available on my Github here: https://github.com/AJSchat/OpenDEMO
I only reverse engineered the game module however, there is no support for the cgame. Seeing as many common structs overlap, you could take that code as a starting point. It is open source and available on my Github here: https://github.com/AJSchat/OpenDEMO
Thanks for your effort, we are still using 1fx on the server today even though demo might not have the same amount of people as it used to, we have a really close community like here. The OpenDEMO structs overlap with what code? How did you figure out which wrappers to write to make game compatible with demo?
There are many structures shared with the server, that are used by both cgame and game modules. Think of things such as the player state or trace information (that the cgame uses for stuff like client prediction). Many of these structs have already been reverse engineered (present in q_shared.h), making the progress of the cgame module already a little easier. I'm sure though that there are things that the cgame module uses which the game module doesn't, and must therefore still be figured out.
Back with I did OpenDEMO I decompiled the game module (using tools such as qvmdisas and qvmkanker) and made my way through the disassembly, comparing v1.00 to demo, and analyzing the SoF2 1.00 SDK and also vanilla Q3 and JK:JO. It is a tedious process and will require some skill to make your way through it.
Back with I did OpenDEMO I decompiled the game module (using tools such as qvmdisas and qvmkanker) and made my way through the disassembly, comparing v1.00 to demo, and analyzing the SoF2 1.00 SDK and also vanilla Q3 and JK:JO. It is a tedious process and will require some skill to make your way through it.