Re: [Warzone-dev] New repository open for business

2009-04-07 Thread Dennis Schridde
Am Dienstag, 7. April 2009 00:18:22 schrieb Per Inge Mathisen: > *) You need to check out all your working copies again. I am led to > understand that this has something to do with gna.org screwing with > the repository UUIDs. I am very sorry for the inconvenience. Would be my fault only, not Gna's

[Warzone-dev] trunk & 2.2 changes for ports/ server code/ config directory

2009-04-07 Thread bugs buggy
Speak now before we do these changes. They must be done all at once! In short, game server port is now 2100 Master server port is now 9998 config dir is now "Warzone 2100 2.2" (for mac/windows) and ".warzone2100-2.2" The bot will need updating. Anything else? http://developer.wz2100.net/ticket/

Re: [Warzone-dev] trunk & 2.2 changes for ports/ server code/ config directory

2009-04-07 Thread Elio Gubser
Am Dienstag, den 07.04.2009, 15:49 -0400 schrieb bugs buggy: > Speak now before we do these changes. They must be done all at once! > > In short, game server port is now 2100 > Master server port is now 9998 > config dir is now "Warzone 2100 2.2" (for mac/windows) and ".warzone2100-2.2" > The bot

Re: [Warzone-dev] trunk & 2.2 changes for ports/ server code/ config directory

2009-04-07 Thread bugs buggy
On 4/7/09, Elio Gubser wrote: > Am Dienstag, den 07.04.2009, 15:49 -0400 schrieb bugs buggy: > > > Speak now before we do these changes. They must be done all at once! > > > > In short, game server port is now 2100 > > Master server port is now 9998 > > config dir is now "Warzone 2100 2.2" (f

Re: [Warzone-dev] trunk & 2.2 changes for ports/ server code/ config directory

2009-04-07 Thread Per Inge Mathisen
I don't think adding version checking code to 2.2 is a good idea. Let's not do a lot of changes to it, so that it can be released. Instead, I suggest that for trunk we use port 2100 for game, port 9990 (or something else) for master; for 2.2 we use port 2100 for master, and port 9990 (or something

Re: [Warzone-dev] trunk & 2.2 changes for ports/ server code/ config directory

2009-04-07 Thread Zarel
2009/4/7 bugs buggy : > We also may want to change GAMESTRUCT, so the master server can take > care of  games that have a password, and other stuff we want to check > for? YES. The master server should also save the version number, and any mods loaded. I'm sick and tired of people joining my Reba

Re: [Warzone-dev] trunk & 2.2 changes for ports/ server code/ config directory

2009-04-07 Thread bugs buggy
On 4/7/09, Per Inge Mathisen wrote: > I don't think adding version checking code to 2.2 is a good idea. > Let's not do a lot of changes to it, so that it can be released. Um, I think your wrong on this, it isn't *that* much that has been changed/modified. The lifespan of 2.2 is more than likely

Re: [Warzone-dev] trunk & 2.2 changes for ports/ server code/ config directory

2009-04-07 Thread bugs buggy
On 4/7/09, Zarel wrote: > 2009/4/7 bugs buggy : > > > We also may want to change GAMESTRUCT, so the master server can take > > care of games that have a password, and other stuff we want to check > > for? > > YES. First, let me explain a bit. typedef struct { uint32_t GAMESTRUCT_VERSION; //

Re: [Warzone-dev] New repository open for business

2009-04-07 Thread bugs buggy
On 4/6/09, Per Inge Mathisen wrote: > I've successfully(*) moved the svn repository to sf.net, and you can > start committing again. > > However, you need, obviously, an sf.net account to do so. If you lack > one, contact me or gerard_ for the time being. > > The new URL is: > https://warzone

[Warzone-dev] [Warzone 2100 Trac] #371: Trac needs fixing for the new svn repo

2009-04-07 Thread Warzone 2100 Trac
#371: Trac needs fixing for the new svn repo ---+ Reporter: Buginator | Owner: Type: task | Status: new Priority: critical | Milestone: 2.1.3