Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 49

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 97

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 101

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 109

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 120

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 124

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 132

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 201

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/init.php on line 421

Deprecated: Assigning the return value of new by reference is deprecated in /home/gameadm/public_html/forums/includes/class_core.php on line 2384
<br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/archive/global.php</strong> on line <strong>26</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3249</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><br /><strong>Warning</strong>: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in <strong>/includes/functions.php</strong> on line <strong>3436</strong><br /><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en">
<head>
	<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
	<meta name="keywords" content="Switch between realdamage / normal damage, vbulletin,forum,bbs,discussion,jelsoft,bulletin board" />
	<meta name="description" content="[Archive] Switch between realdamage / normal damage Quake Trilogy" />
	
	<title>Switch between realdamage / normal damage [Archive]  - Main</title>
	<link rel="stylesheet" type="text/css" href="http://www.gameadmins.com/forums/archive/archive.css" />
</head>
<body>
<div class="pagebody">
<div id="navbar"><a href="../index.php/">Main</a> &gt; <a href="f-25.html">GameAdmins.com</a> &gt; <a href="f-4.html">Server Setup Forums</a> &gt; <a href="f-12.html">Quake Trilogy</a> &gt; Switch between realdamage / normal damage</div>
<hr />
<div class="pda"><a href="?pda=1" rel="nofollow">PDA</a></div>
<p class="largefont">View Full Version : <a href="http://www.gameadmins.com/forums/showthread.php?t=4879">Switch between realdamage / normal damage</a></p>
<hr />

<div class="post"><div class="posttop"><div class="username">MontauK</div><div class="date">04/20/05, 07:27 pm</div></div><div class="posttext">Good day.<br />
I've got the following &quot;problem&quot;.<br />
With Soldier of Fortune2 (SoF2), which has the Q3 engine I believe, I want to switch between realdamage weapon and normal damage.<br />
<br />
It's no problem to switch between MODs (fs_game dirofmod), but how can I use different command lines to start a server in normal damage or real damage without clients having to download complete directories including MOD files (e.g. OSP)?<br />
<br />
Thanks in advance for any help :) .</div></div><hr />


<div class="post"><div class="posttop"><div class="username">BENSTER</div><div class="date">04/20/05, 10:02 pm</div></div><div class="posttext">For each mod you play, if there are client side files, they will need to have them installed.  If by chance you have a server side mod, you might be able to extract the qvm from the pk3 file so the client does not have to downlaod the  pk3.  If the mod has skins, different graphics, sounds, or complete pk3's, then this won't work, and they need the mod.  <br />
<br />
About the only thing you can do is  place all the map files in yoru main folder, and each mod  can call up those maps.</div></div><hr />


<div class="post"><div class="posttop"><div class="username">MontauK</div><div class="date">04/21/05, 04:24 am</div></div><div class="posttext">Thanks for your quick reply :)<br />
<br />
Isn't it possible to call on a .pk3 file within a .cfg file? So that I can put the .pk3 file in a different folder in the main map of the game?</div></div><hr />


<div class="post"><div class="posttop"><div class="username">Unregistered</div><div class="date">04/21/05, 05:32 am</div></div><div class="posttext">Hi... im KjellviZ... and tryin 2 resolve this problem together with Montauk... =)<br />
<br />
What we are trying to accomplish:<br />
<br />
Starting the server with and without loading a RealDamage (RD) modification in the form of a pk3 file which alter the damagemodel for weapons.<br />
This should be done just from choosing between 2 different configs for startup. In both cases we want the server to be running OSP 1.0h.<br />
<br />
The following has been tested and works to some extent:<br />
<br />
Moving the RealDamage pk3 file to a subfolder, and using &quot;fs_game dirofmod&quot; to launch it.<br />
The server starts fine, the damage is RD but the server doesent load OSP !<br />
<br />
Making 2 copies of the entire OSP folder, 1 with the RD pk3 mod and 1 without.<br />
This works fine, both RD mod and OSP load fine when we want, but the client is forced to download OSP again, causing the client to have duplicate OSP folders as well as the server.<br />
<br />
---<br />
<br />
I know this should be possible to accomplish, as ive seen a server-host which had the ability to choose wether to start server with or without the RD pk3 mod from their cpanel.<br />
<br />
I hope you guys can help us out, as we need the ability to swap between Normal and RealDamage on the fly...<br />
<br />
Sincerely...<br />
KjellviZ|PFL</div></div><hr />


<div class="post"><div class="posttop"><div class="username">Unregistered</div><div class="date">05/12/05, 01:19 pm</div></div><div class="posttext">Have a read of the OSP docs, specifically the History file.  From v1.0d they added a new cvar to let you set the weapon file that you want to use.<br />
<br />
Basically, you need to have two cfg files. In those cfg files set osp_weaponsfile to point to whichever wpn mod you want and switch between the two. No need ot have two separate installations of OSP. :)<br />
<br />
-={DX}=-Ronin{uk}<br />
www.dxclan.pri.ee</div></div><hr />


<div id="copyright">vBulletin&reg; v3.6.9, Copyright &copy;2000-2012, Jelsoft Enterprises Ltd.</div>
</div>
</body>
</html>