Wed, 22 Aug 2012, 3:09 pm by Rob Clegg, Do Gaming journalist Tags: DICE, Battlefield 3
DICE may be too scared of the implications in giving players access to parts of a game’s code because while the company thinks it is very important, there are also negatives that can come with releasing code.
In an interview with GameSutra, Karl Magnus Troedsson, DICE general manager said that giving players access to certain parts of the code would very likely leave it open to hacking exploits which is something they are not comfortable with.
“If we do mod support, we want to do it really, really well. We are not ready to do this yet,” he said.
Given the history of Battlefield, Battlefield 2 actually had official modding tools in place and the community did nothing but increase the popularity of the game so it’s understandable why the community was in a bit of a rage when nothing was released alongside Battlefield 3.
An argument could be made that allowing modding is essentially a great way to increase popularity despite leaving it open to hackers. A perfect example at the moment is DayZ which is a mod for ArmA 2. Truth be told, if DayZ was never released for ArmA 2, the game probably wouldn’t have made half the sales it has made since the release of the mod.
The problem with online-trackable stats is that it leaves a wide gap for hackers to come in and get great scores.
For those that remember the mod Desert Combat for Battlefield 1942, I would happily subjugate my rage for hackers if I could be given a mod that awesome. It may be worth the risk because even in DayZ there are hackers from time to time, but the overall gaming experience of the community-driven mod is better than having a few hackers spoiling it for a few minutes before they get bored.