Tremulous Forum
Mods => Modding Center => Topic started by: F50 on August 26, 2009, 07:39:22 am
-
Sorry if this is a newbie question but...
I can compile the svn (from http://source.mercenariesguild.net/lakitu7-qvm/trunk/) just fine. I can make changes to src/game/admin.c and copy over the vms and I can see my changes.
However, if I make any changes to src/cgame/* it does not appear to apply them. I can completely comment out some code that looks like its vital to the normal operation of tremulous, and copy over all of the qvm files (cgame.qvm, game.qvm, ui.qvm) to base/vm/*, and still nothing happens. What am I missing now?
-
it defaults to 1.1's cgame, probably
-
Do you install it in the server base/vm ? The cgame and ui qvms are only for the client. That means if you run a pure server, you will probably have to put them in a .pk3 that the clients can download.
-
That doesn't make too much sense to me gimhael, but I've done it. All of the qvms are in a pk3 in both base folders now. Still nothing
@Archangel how should I change the default cgame then?
In case this is important: The files I've tried to modify are cg_main.c and cg_buildables.c
-
setup an entirely different folder with a trem install to keep from breaking your current trem install. REMOVE the vms-1.1.0.pk3 file and REPLACE it with your updated vm batch (cgame, ui, and game in a folder called vm/)
-
Ok, I had to move the vms pk3 completely out of the tremulous basepath to get it to look at my qvms. Once I do that I get an error saying that it can't load ui.qvm. Files in the cgame directory shouldn't effect that right? So I grab the original ui.qvm from the original vms.pk3 and try that, which fails in the same way. Also, its trying to find a file called mod.cfg.
I'm going to mess around with this some more and see if I can get rid of this error
-
try putting all of your freshly compiled vms in a pk3, and using it instead of vms-1.1.0.pk3.
-
they already have been put in a .pk3, unless you mean to actually name it vms-1.1.0.pk3
-
i mean to have your pk3 in place of it, i.e. absolutely no vms-1.1.0.pk3 in your basepath. only a pk3 with YOUR vms.