Does anyone know if they are going to release the server files 1 day ahead of schedule like they did with 1.0? I'd like to know so I can ask my hosting company to upgrade the server when the new release comes out.
coilAmateur pirate. Professional monkey. All pance.Join Date: 2002-04-12Member: 424Members, NS1 Playtester, Contributor
I suspect that if they are released early, only the Linux build will be. There were issues with the Windows build last time that I imagine Flayra does not want to repeat.
<!--QuoteBegin--coil+Jul 3 2003, 11:36 AM--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (coil @ Jul 3 2003, 11:36 AM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> I suspect that if they are released early, only the Linux build will be. There were issues with the Windows build last time that I imagine Flayra does not want to repeat. <!--QuoteEnd--> </td></tr></table><span class='postcolor'> <!--QuoteEEnd--> Really? That sucks for me since I run a very busy NS server on Windows. Damn.
<!--QuoteBegin--Pebbles-TPF-+Jul 3 2003, 02:01 PM--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (Pebbles-TPF- @ Jul 3 2003, 02:01 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> Who do we contact, or where do we look, to get hold of the server files?
Linux server files should be available one day before the official client release. Win32 files will be released the same day as the official client release. I think this has to do with people jury rigging the win32 server files in the past in order to play NS early.
Keep in mind, I'm not the official PR voice for NS, this is just what I assume from past experience.
If we can get the server files just a few hours before the client side that would help a great deal(ideally a day). I don't know about the problem you had last time but maybe we can work around a solution.
Do people actually try invest a lot of time into hacking the win32 server files in oreder to play NS 2.0 less than 24 hours early, by themselves (as I doubt any servers would have the balls to RUN 2.0 early)? Get a life.
Yes, people did hack the server files when 1.0 was released. Guess they couldn't wait to play. In any case the decision isn't mine to make and they still have about a month to hammer out the details.
its really quite simple, if you don't include ns\cl_dlls in your win32 server distribution then you can't 'hack' the server distro to make a working client.
but since NS requires these files, they have to ve included just hold out til its released, sure the servers will come in kinda slow (which i dont think will happen, MonsE does great things)
<!--QuoteBegin--Vadakill+Jul 3 2003, 10:08 PM--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (Vadakill @ Jul 3 2003, 10:08 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> It will be both client and server upgrades. <!--QuoteEnd--> </td></tr></table><span class='postcolor'> <!--QuoteEEnd--> "Upgrades".. Will there really be upgrades so we can keep most of our settings, or will there just be a "new" version of NS, that we have to configure completely again?
Hypergrip, for the server portion or the client portion?
If you are talking about client portion of the setup you can just make a copy of your autoexec.cfg and config.cfg files, install the new NS 2.0 client and then copy them back over to the new NS folder; that should keep all of your binds and settings in tact. From what I understand the NS 2.0 client files will be a full install so people should probably get rid of their old version by deleting the folder, then install the new client.
As for the server files, each server will be a little different. The admin that configures the server for running will have to carefully migrate over to NS 2.0 and make sure his server config files are not overwritten. When I get my hot little hands on the NS 2.0 Linux beta server for testing I will write up a guide to install/upgrade from NS 1.04 to 2.0 on a Linux HLDS server, Win32 admins are on their own.
<!--QuoteBegin--Vadakill+Jul 5 2003, 03:44 PM--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (Vadakill @ Jul 5 2003, 03:44 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> When I get my hot little hands on the NS 2.0 Linux beta server for testing I will write up a guide to install/upgrade from NS 1.04 to 2.0 on a Linux HLDS server, Win32 admins are on their own. <!--QuoteEnd--> </td></tr></table><span class='postcolor'> <!--QuoteEEnd--> Damn you.....you beat me to it
Comments
<i>Pebbs</i>
Really? That sucks for me since I run a very busy NS server on Windows. Damn.
<i>Pebbs</i> <!--QuoteEnd--> </td></tr></table><span class='postcolor'> <!--QuoteEEnd-->
*bump*
Keep in mind, I'm not the official PR voice for NS, this is just what I assume from past experience.
just hold out til its released, sure the servers will come in kinda slow (which i dont think will happen, MonsE does great things)
"Upgrades"..
Will there really be upgrades so we can keep most of our settings, or will there just be a "new" version of NS, that we have to configure completely again?
If you are talking about client portion of the setup you can just make a copy of your autoexec.cfg and config.cfg files, install the new NS 2.0 client and then copy them back over to the new NS folder; that should keep all of your binds and settings in tact. From what I understand the NS 2.0 client files will be a full install so people should probably get rid of their old version by deleting the folder, then install the new client.
As for the server files, each server will be a little different. The admin that configures the server for running will have to carefully migrate over to NS 2.0 and make sure his server config files are not overwritten. When I get my hot little hands on the NS 2.0 Linux beta server for testing I will write up a guide to install/upgrade from NS 1.04 to 2.0 on a Linux HLDS server, Win32 admins are on their own.
Damn you.....you beat me to it