What makes TTR TTR?

[delerium10101]

Excellent suggestions, keep them coming. Some things I would like to address:

Dynamically interacting with the environment: This is covered. Just, trust me when I say that this is completely covered in every way imaginable. You could come up with the craziest way imaginable for interacting with the environment, we\'ve got it. There are quite a few reasons GG is interested in publishing my bit of tech, that\'s one of them.

Map sizes: This is just part of Torque. The maps extend on infinitely in all directions. While some efforts can be made, it isn\'t reasonable to expect a map that works with 128 players to work with 4, or a map that works with 4 to work with 128. While I can do some magic script-foo, the most I could handle would be to get maps to scale well from, say, 4 to 8 or 8 to 16. Small changes like that.

Respawning time is easy to adjust, and I\'ll take your suggestions into consideration. You\'re absolutely right about this. Having a 5 second spawn delay like Halo is far too short when we\'ve got 128 players, but delaying by a minute when we\'re dealing with 8 is even more insane. We\'ll do some play testing with this to figure out the best way to handle it.

Map time: This is an odd one. What I would like to do is just deviate from the normal \"Do objectives x, y, and z within time T\" and just have \"Do objectives x, y, and z\". However, I\'m not particularly big on multiplayer gaming so what do I know? This will probably be a user set option when the server is started. One possibility for something like area capture is once all the areas are owned by one team, start a count down. Whatever, another thing that will have to be playtested extensively.

Server stabability: When TTR:Torque becomes available to the public, I can guarantee at least one dedicated server running at all times. No guarantees on the ping or performance (it would be the mac that I\'m typing this on). Our master server would be run by GG, which has worked without fail for many games. Also, since we\'re using Torque, don\'t worry about net performance. Really. Torque was built around having the best net performance possible, and it shows. I\'ve performed tests with pings ranging from 2,000-3,000 and a 50% packet loss, and it still managed to chug along. It wasn\'t particularly playable ( the camera is run server side, so a connection like that means the camera lags badly), but nothing went horribly wrong. No walking through walls, no mysterious extreme popping, just a choppy camera. Torque rocks.

Again, thanks for all the suggestions and keep them coming. Come on, suggest a game mode! It might just make it in!