I'm making great progress on this beta, getting good data from these games and tracking down some nice bugs. I appreciate everyone who's taking the time to come in and hammer on it for me.

I wanted to clarify that some of these games are being managed by certain testers and are therefore subject to their whims. At the moment, Helix and Cruncher are moderating games, and Helix asked for access to games for his personal use. So if you're playing in game G or H, keep in mind that those are Helix's test games.

If you'd like to run your own test game, for you personally or for a group, let me know and I'll set you up with a personal admin login. I'm also looking for feedback/testing on the remote admin features, so that would help.

In general, it seems that the testing is focused quite a bit on cashing methods and other heavy scripting operations, which is good, but we're lacking a bit of interaction. At some point, we need to have a game or two where we can test some major base attacks and pvp. I also think we're at a point where we could start a serious game with the intent to play it from start to finish, if we can get enough serious players to give it a live tournament-level test. Once I feel that the game is stable enough for a live tournament, I'll go ahead and open it up to wide beta and public release.

Anyone wanting to test their invasion skills can come into game B and give it a shot. My door is in sector 9075. I'll even give them assets they need or cruncher can edit them what they need.

Oh, I want to clarify something for those who are wondering why I'm limiting the beta to just this small set of servers when in the past I've allowed other gameops to join in the beta when they want. I've created a special debug build that generates a ton of debug info about the game. If it crashes, I get the list of functions that were called so I can pinpoint what operation was active when it happened. Also, special code is in place to cause the game to crash immediately whenever there is data corruption. I can even get a list of function calls for a game that locks up but doesn't crash. There's so much debug data generated, I really need to focus on one or two servers and watch that data closely. Having more servers would be overkill. Plus, I don't want to do a public release of a heavy debug version.

So if you can help us crash the 21-6.com server, it will give me more insight into the bug than if you crash it later on your own server. And as soon as the bug reports slow down (they're slowing down already, but we need to make sure everything is tested), I'll put out the release version for others to run.

Are there any limits on what you want us to do to 'crash' your server? Because I've got a big hammer....

Try not to do anything that qualifies as an internet attack

I'm actually more interested in crashing the game than the server, anyway. I don't have any debug code in the server so I won't get much info out of a crash. However, if it crashes, I want to know about it so I'm aware of it.

Ok its a good thing you said something....



cuz we can really put a load on it if ya want

if the images are inappropriate i can remove them.

I've run rapid connect tests locally and it's holding up. Once it's released, if you want to do some of this kind of testing and let me know what you find out, that would be awesome.

I think I'd rather you or I give them assests within the game. I want to stay out of tedit because that may cause problems outside of normal play.

I got my first L5 today in Game B baby.. watch out! LOL


Just for the record, I've gone into tedit once to change the citadel upgrades on the Super H in game "High Edits" then I did reset that game. The Super H bangs full of assets and upgrades in one day to L6.

So, if anyone wants to get a team together and all of you run around with L6 Super H's that will be cool too. That game does however have a 12 hour time limit. I've pushed it once running a CIM.