Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
It was difficult to find an average Indian call-center salary, so lets use Rs 300k. This was at the upper end but using the high figure makes some allowance for training and other costs.
This is $5610.
Of course you may want differing levels of staff, and can use some software. I would say using a system of software flagging, geared to hit more false positives than risk missing something followed by a review by a human, with a system for them to refer it to someone more experienced/qualified if its not straightforward could reasonably cut the hours requirement in half. So, 199584/2=99792.
Multiplying this by the much more reasonable salary gives 99792 * $5610 = $559,833,120.
Still a hell of a lot of cash, but probably not unaffordable to Google.
You have civilians in game, there are a few options how its handled.
1. No consequences. The anti violence lobby goes nuts, the game is OK, but every time someone opens fire there are screams and civilians running. Probably quite entertaining hunting them down and shooting them but would distract from the main story and the novelty would soon wear off.
2. Instant consequences. You hit a civilian the mission is failed. This is annoying, failing missions from accidentally winging your computerised team mates is frustrating enough, this would be 10x more likely and as a consequence far more annoying.
3. Delayed consequences. You hit a civilian the game goes on, then in the end of mission debrief there are consequences. Either a mission failed redo it (immensely frustrating after spending half an hour working your way through a mission) or some negative impact on your score (but if you put a "number of civilians killed" score in there some people are going to try to max it out. This could actually be quite good if well thought out and there was some method of the computer distinguishing "accidental" civilian shootings from deliberate ones. Differing paths and mission briefings etc. But it means a lot more work from a game design perspective.
The other thing:
What are these civilians doing in my war-zone?
OK in some sort of terrorist event civilians aren't that unlikely. But once the shooting starts you will only find them cowering under tables behind locked doors. In a battlefield/war-zone scenario, the civilians would have had plenty of time to evacuate or lock themselves in the basement etc. So civilians just "wondering around" is highly unlikely.