Mod configuration with linux server

[ismo 1]

Hi all, been trying to find out if there is a way i can startup a 1.96 linux server with additional mod folders. Tried some fiddling with the config but it seems ofp will not start with more the one added mod folder

tried this setup

set config = "server.cfg"

set basadd = "@bas"

set ecpadd = "@ecp"

set extadd = "@ext"

screen -A -m -d -S ofp ./server -config=${config} -ip=${ip} -port=${port} -mod=${basadd} -mod=${ecpadd} -mod=${extadd}

or tried also the

set mods = "@bas;@ecp;@ext" with the -mod=${mods} settings, both wont work and server wont start.

both settings running just one modfolder worx fine, adding more runs into difficulties

any thoughts on this would help

TIA, ismo

[Lobanak 0]

screen -A -m -d -S ofp ./server -config=${config} -ip=${ip} -port=${port} -mod=${basadd} -mod=${ecpadd} -mod=${extadd}

tried the following?

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">

screen -A -m -d -S ofp ./server -config=${config} -ip=${ip} -port=${port} -mod="${basadd};${ecpadd};${extadd}"

you need -mod="mod1;mod2" on linux as I know.

Greets

[CiA]Lobanak

[benu 1]

I always start mine (from within a script) with a line like this:

./server -mod=$MODS

(i guess on the commandline you would have to use -mod="$MODS"), where MODS get defined elsewhere like this:

MODS="gdt;rts3"

Actually i have a script that allows my co-admins to change mods and that writes to the MOD variable, but that should not invalidate anything of the above.

I never used a construct like -mod=a -mod=b, but i have seen it often enough from others to think it will work too.

[ismo 1]

tanx for your replies but either theres is a verry buggy addon in my folders somewhere or sumting else.

both settings you guys are tellin work fine, but when i add 3 diff mod folders, ofp wont run.

Now these mod folders are really specia, one has all bas in it, one with most russian addons, and one with extra like winterpacks and so on, all tested addons no funny stuff, i have em all running on a i386 server no problem.

im getting sick and tired of this shit, got a great 100mbit server now which i cant configure proper. Upped 1.2 gigs od addons which i cant use this way.

Next ill just drop all addons into one big addon dir and be done with it, or someone should have another solution or fix.

greetz,

[benu 1]

Try putting the addons into the normal addons folder and see if it works then, there are a lots of broken addons floating around that will not work on (linux) decicated servers, especially when put into a modfolder.

[mr.kowalskii 0]

hi, i try to make this, the mod works fine, but some mpmissions do not work with the addon not in <dir game>\addons.

i have started the server with ses addons in foldes ses,

and folder into have the kegsw44.pbo, some mfcti do not recognize in this folder. When i move to principal addons folder works ...

OS: linux redhat 9.0

[ismo 1]

well im now in the process of moving all addons in the default addons dir, will keep u guys posted on how thats working

[benu 1]

That "some mission will not work" popped up when addons were missing or there were some broken addons. The problem with broken addons is that SOME missions NOT using them will stop working. So most probably some of your addons are broken. This explains your problems with modfolders too, as the server will most likely not start if you have those addons in modfolders.

[ismo 1]

promised u guys an update, well i moved all addons to normal default addons dir and most maps are working, problem is that a non working map will never show why it aint working, unlike when u run em tru the MP mission editor of OFP itself .

I tried some mission on my home pc (wich i setup as a 1 on 1 copy of the server as far as addons goes) and the non working maps on the server run fine at home......

Could it be that cos of the server running on linux its all gotta do with case sensitivity, i know linux is but does the actual name of an addon need to be excact same or is upper/lowercase in this case not important?

im on the case u mite say :-)

greetz,

ISMO

[benu 1]

All files on the linux server have to lowercase, which the tolower tool does. How you call them in the mission.sqm is not really important.

If a mission you select throws you back to mission selection screen then an addon for that mission is missing. If you get to select a slot and it goes back to mission selection (with an error message) when you hit start, then you got broken addons on the server. It gets pretty ugly from there on, as most broken addons will cause errors only missions where they are not used and it does not have to be the addon mentioned in the error message. Eg an dependency in an addon may give you an "missing addon bis_resistance" error messsage (cause it builds on bis_resistance without declaring that dependency in the requiredAddons[] array)

And sadly there are a lot addons out there that are broken in this way, even from big teams like bas or dkmm.

Good luck, i am just now looking for one or more broken addons myself cause i noticed some missions on the server stopped working...

[ismo 1]

copy that Benu, all em addons are a bitch, specialy if peeps not using addons packs i made ROFL. but im gettin there, tanx 4 all the help