Re: [warzone2100-dev] Current status of 2.3
On Fri, Dec 4, 2009 at 11:08 PM, bugs buggy buginato...@gmail.com wrote: Just a heads up, I am leaning toward the next release to be 2.3 RC1. I'm fine with this. Working on some tickets that were reported for B3 now, but I don't see any real showstoppers yet. There's some guy on the forums who can't run 2.3b3 but is fine on 2.2.4. Go talk to him. I think his username is SCAVANGER or something? With the release of 2.3, we will turn off the lobby server for 2.2. 2.0, and 2.1 have already been disabled. Per our IRC conversation, I feel that one or two weeks is too short. I'm thinking something like six months. The lobby server should be yelling at them to upgrade the whole time. Most large projects support versions far older than six months. While we don't have the manpower to do that, we also shouldn't intentionally refuse to do something as simple as leaving the lobby on. Remember, the latest version of Ubuntu will have no version of Warzone later than 2.2.2 until April 2010. You wouldn't believe how many 2.0 and 2.1 people still hosted (or tried to host) games! All the more reason not to retire the 2.2 server so early. -Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Current status of 2.3
On 12/5/09, Zarel zarel...@xx.com wrote: On Fri, Dec 4, 2009 at 11:08 PM, bugs buggy bugx...@xxx wrote: Just a heads up, I am leaning toward the next release to be 2.3 RC1. I'm fine with this. Working on some tickets that were reported for B3 now, but I don't see any real showstoppers yet. There's some guy on the forums who can't run 2.3b3 but is fine on 2.2.4. Go talk to him. I think his username is SCAVANGER or something? If you mean: http://forums.wz2100.net/viewtopic.php?f=4t=4239 if people don't read up on what they should post, then how can we help them? It gets highly annoying to see posts / trac tickets with basically no real information in them. With the release of 2.3, we will turn off the lobby server for 2.2. 2.0, and 2.1 have already been disabled. Per our IRC conversation, I feel that one or two weeks is too short. I'm thinking something like six months. The lobby server should be yelling at them to upgrade the whole time. It will spit back a message about updating, but 6 months is *way* too long. There really is no reason NOT to upgrade. Most large projects support versions far older than six months. While we don't have the manpower to do that, we also shouldn't intentionally refuse to do something as simple as leaving the lobby on. Remember, the latest version of Ubuntu will have no version of Warzone later than 2.2.2 until April 2010. You wouldn't believe how many 2.0 and 2.1 people still hosted (or tried to host) games! All the more reason not to retire the 2.2 server so early. No, that is the exact reason why to retire it ASAP. We want everyone to use the same version of the game. This will make a bigger userbase that all has the same version of the game, and will make it much easier to find games online. Let me clarify a bit, when I say turn off 2.2 server, I mean, it will still spit back the MOTD message, which will be something like. You are using a unsupported version of the game. Please update today! http://wz2100.net; or whatever... The addg will be disabled, the list will still show games, but it will show the X on the games, because of wrong version. Make sense? ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Current status of 2.3
On Sat, Dec 5, 2009 at 6:12 PM, bugs buggy buginato...@gmail.com wrote: Old way, selectedPlayer = player position, and dpid voodoo to translate back and forth. New way, we try to RemapPlayerNumber(), and while that works for v7 savegames, it breaks for v36 savegames. And the only reason why it works for v7 games is because the data is mostly all set to NULL anyway, so remapping the player has no adverse consequences then. In short, unless I am missing something obvious, we need to use NetPlay.players[].position as the new player2dpid[]. Which means we must bring back the dpid voodoo under another name, or do some clever hacking to get around this...and I am out of ideas right now. Erm, what's wrong with that? Find someone's position from their player number... Makes sense to me... -Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] Current status of 2.3
Just a heads up, I am leaning toward the next release to be 2.3 RC1. Working on some tickets that were reported for B3 now, but I don't see any real showstoppers yet. With every new release we do, it is more stable than the last 'stable' release anyway, that is just how this project works, with the current lack of manpower. With the release of 2.3, we will turn off the lobby server for 2.2. 2.0, and 2.1 have already been disabled. This allows us to move our already small userbase to all be using the same version of the game, and that will hopefully get more people playing, and thus make it much easier to find games. You wouldn't believe how many 2.0 and 2.1 people still hosted (or tried to host) games! ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Current status of 2.3
bugs buggy wrote: With the release of 2.3, we will turn off the lobby server for 2.2. I think we should give people some more time to make the switch. Give them one or two months, not everybody wants to play the newest version when it's out and those people that depend on their GNU/Linux distribution to offer a package need some time as well. If not, then we should announce this as soon as possible so the forums/trac/Buginator's inbox isn't spammed with LOBBY SERVER DONT WORK! pls fix. - Kreuvf signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
