Lucius wrote:Things I remember to be a gruelling slog *cough* Sewers *cough* can be finished in about an hour of play.
That is what I was remembering. I forgot some of the issue was the text display. I will have to check it out then. Thanks!
ok, i'll bite.. how will they know what exact situation/set of circumstances to spawn then?
[that's not meant as a rhetorical question, btw, i genuinely don't know the answer..
A program known as a bug trap. It is either a RAM dump for a hard-crash or a log system that tracks certain actions (like spawns) for general bugs. So when they see that spawning a particular enemy results in a CTD, then they load a test (aka blank) map and spawn one for themselves. If they see that object #3659 results triggers an infinite loop when skill #005 is applied, then they spawn the object and a team with all skills, on a blank map.
If the test map does not work, then the load the actual map the error was recorded on and test again. If the result is map specific, then that means there is interference and they get their programmers to activate the variable monitoring to see where the leak is.
If they cannot replicate the issue via console, that means the bug is deeper, most likely coming from an earlier point in the game,and only making itself known later (aka save game corruption). So a saved game is of limited use unless they are tracking everything (all object, people, etc.) encoding most of the world in the save, like a Bethesda game does.
That being said, if you have a small army at your disposal, and want to load and test 10K saves instead of just having a database that auto-sorts and eliminates duplicates, then saved games might be desired. Many forum reports of bugs sound different but turn out the be the same thing, and you have to expect the same from an open beta. Personally, I prefer bug trap reports.
Outlaws, Blood Cultists, Killer Robots, Bomb Worshippers, and now Cyborg Robotnappers! What next?