SP mods .. howto ...


(Hewster) #1

Hi,

Well I’ve just been playing with compiling a SP mod, and have the
following tips:

Ok, there is 1 huge problem getting SP mods to work under Windows,
that being, the sp dll’s are in the root folder, so Windows will always
use these dll’s, as they are the first ones it finds, no matter if you add
fs_game or not :frowning:
However under Linux, the binaries are in the main folder !!!, and running
your SP mod is a breeze.
Solution… move the original sp dll’s from the root folder to the main
folder, put your mod dll’s in your mod folder, wolla… everything works
fine… normal SP works & your mod will too :slight_smile:

I guess the easiest way to achive this is to write a windows installer script
with your mod install, that moves the standard SP dll’s for you, as to
expect players to move the files manually is asking for problems !! hehe

Perhaps this is a cock up in the windows installation of wolf ?

Hewster


(fretn) #2

cool, been looking for that one :slight_smile:

fretn


(Hewster) #3

:slight_smile:

oh, and I should add that I had to put the scripts & ui folders that come
with the source into a pk3 in the mod folder… and to make sure it worked,
I named it pak0.pk3.
When I didn’t do this, the menus didn’t show the graphics properly.

Hewster


(DiaZ) #4

As it’s been said in another topic I posted about this, by moving the dll’s into the /main folder mods that don’t come with DLL’s will stop working. I downloaded Operation Evil Eye a couple weeks ago when my folders were set up like this and the map refused to run. It would crash the game. Putting DLL’s back into the root folder fixed it.


(Hewster) #5

ok, then an easy way would be for mods that don’t change the source, to
include the the standard dll’s in their installation :slight_smile:

I believe this is the only way we are gona get round this problem.
Overwriting the standard dlls in the root really isn’t good practice, in my
opinion.

We might get a patch for SP… But I got a feeling that isn’t gona happen !

Hewster


(kat) #6

it ain’t… :confused:
Would this cause errors with the MP side of things and punkbuster? Does that only check for missmatched pk3 files or does it look more deaply into the installation folders at other files, if it does then would moving or ‘re-installing’ standard dlls could cause problems with that as well??


(SCDS_reyalP) #7

it ain’t… :confused:
Would this cause errors with the MP side of things and punkbuster? Does that only check for missmatched pk3 files or does it look more deaply into the installation folders at other files, if it does then would moving or ‘re-installing’ standard dlls could cause problems with that as well??[/quote]
It should not. The MP and SP games use different .dlls and .pk3s. In fact, you can completely delete the SP stuff from your install without hurting MP, or upsetting punkbuster.


(kat) #8

really? wow I didn’t realise they were so independant from each other, always just assumed some wizzy jiggery was going on that it needed both to be there… thnx for the info


(fretn) #9

it ain’t… :confused:
Would this cause errors with the MP side of things and punkbuster? Does that only check for missmatched pk3 files or does it look more deaply into the installation folders at other files, if it does then would moving or ‘re-installing’ standard dlls could cause problems with that as well??[/quote]
It should not. The MP and SP games use different .dlls and .pk3s. In fact, you can completely delete the SP stuff from your install without hurting MP, or upsetting punkbuster.[/quote]

pak0.pk3 is used by both games imo

fretn


(SCDS_reyalP) #10

Ooops. You are correct. None of the executable codes is shared though.


(Hewster) #11

Yeah pak0.pk3 is shared, but I was suggesting that you put your own
pak0.pk3 in your mod folder…

I feel I also need to add these tips:

Line 9 in ui_shared.h, change the path to menudef.h to your mods
path.

And line 13 in g_local.h change GAMEVERSION to your mod name.

OK, I not certain that not doing this will effect the mod, but I do know
it doesn’t stop it working & it makes sense to me :slight_smile:

Hewster