2 ms·
The upside for the simulation problem is that many multiplayer games have something approaching bot AI to begin with - enemy AI - so you can use that as a start
by kevingadd 14y ago
The upside for the simulation problem is that many multiplayer games have something approaching bot AI to begin with - enemy AI - so you can use that as a starting point for those sorts of tests. I'm not sure if that was ever done at scale for GW testing, but it would have been possible...
My understanding is that the replays were possible because the game engine was architected from the beginning with the server 100% in control of game events and the clients relying on message-passing to communicate with the server. This means that the recording captured on the server is a definitive recording of what actually happened in the game. Clients could desync, so a replay might not reproduce that, but otherwise they were pretty accurate.
I'm not sure how the unchanging content problem was solved. I think everything was revision-controlled aggressively enough that it would have been possible to set up a local server instance using old content, and it's also possible that most ordinary changes (altering a texture, a map, etc) wouldn't actually change the results of a replay. Definitely a challenge, though.
Replays came in handy later on for other features (like letting players watch others' PvP matches in-game) so they probably ended up carrying their weight in terms of development effort. I do wonder if they felt like a burden initially, though, before their value became clear...
- endianswap 14y agoDealing with the many scenarios that could break replays was problematic, but being able to run several instances of the same game at the same time and compare them occasionally for desyncs can help alleviate that. For example, using a pointer value (address) as a hash table or sort key means that depending on allocation order, iteration of game entities may be different from one run to another.