GamersCrib
12-22-2008, 02:42 PM
CyberGamer (http://www.cybergamer.com.au/) posted up an interview with Karl Magnus Troedssen: Executive Producer and some of the guys on the Battlefield team. Lets look at what they had to say:
Q: Is the dice team looking to address one of the issues in BF2 where users are binding their mouse wheel to their forward key and getting a "turbocharged" Vodnik or APC as a result? Most servers just classify it as exploiting and ban for it but is it going to be rectified in the 1.5 patch?
A: We are aware of the increased speed that people are able to drive certain vehicles at and are currently investigating. We'd also like to thank the community on the Official Battlefield forums for providing us with plenty of information about this.
Q: Another item that seems to be heavily debated in Australian Battlefield is the use of macros, we know evenbalance put some work into preventing the use of these but is DICE looking into the issue aswell? with some of the end results being the M16 being used at massive fire rates whilst in single shot mode.
A: With the emergence of programmable keyboards like the G15 macros have become a bigger part of gaming with both wanted and unwanted macros being used. We work closely with Evenbalance to prevent the unwanted effects appearing in game and this is something we will continue to do.
As for whether we will change game code to prevent macros is dependent on what we can achieve with Punkbuster. Each issue is dealt with on an individual basis, so yes; we do look into the macros and will look to update Battlefield if and when required to deal with them.
Q: We were lucky enough to get a sneak preview of some of the new enhancements coming up in the 1.5 patch and one thing that was good to see was a new map being made. Is that the only map in production? or planned?
A: At this point it is the only official map currently in production. We are always looking at ways to bring more gameplay to the Battlefield games. We never rule out adding more content to either Battlefield game and may even consider including community content as we did with Battlefield 2142 Update 1.50.
Q: Battlefield 2142 we were all to believe that 1.5 was the last patch being released by DICE for that title, if you could for the BF2142 community let us know what was the motivation behind the upcoming patch?
A: Part of the reason for Update 1.51 is obviously the security fixes for the game servers and clients. We also had the map waiting for release as it unfortunately wasn't ready in time for Update 1.50. So Battlefield 2142 1.51 was always planned to be released if only to let everyone get their hands on the new map.
While we can't always tell everyone the specifics of what we are working on we do have future plans for Battlefield 2 and Battlefield 2142 in 2009.
This is a great interview and even better than some others that were done in the past weeks! So be sure to stay tuned to GamersCrib.net (http://www.GamersCrib.net) as we focus on the soon to be released patches for both Battlefield 2 and Battlefield 2142!!
You can check out the original source of this interview here (http://www.cybergamer.com.au/article/331/).
Q: Is the dice team looking to address one of the issues in BF2 where users are binding their mouse wheel to their forward key and getting a "turbocharged" Vodnik or APC as a result? Most servers just classify it as exploiting and ban for it but is it going to be rectified in the 1.5 patch?
A: We are aware of the increased speed that people are able to drive certain vehicles at and are currently investigating. We'd also like to thank the community on the Official Battlefield forums for providing us with plenty of information about this.
Q: Another item that seems to be heavily debated in Australian Battlefield is the use of macros, we know evenbalance put some work into preventing the use of these but is DICE looking into the issue aswell? with some of the end results being the M16 being used at massive fire rates whilst in single shot mode.
A: With the emergence of programmable keyboards like the G15 macros have become a bigger part of gaming with both wanted and unwanted macros being used. We work closely with Evenbalance to prevent the unwanted effects appearing in game and this is something we will continue to do.
As for whether we will change game code to prevent macros is dependent on what we can achieve with Punkbuster. Each issue is dealt with on an individual basis, so yes; we do look into the macros and will look to update Battlefield if and when required to deal with them.
Q: We were lucky enough to get a sneak preview of some of the new enhancements coming up in the 1.5 patch and one thing that was good to see was a new map being made. Is that the only map in production? or planned?
A: At this point it is the only official map currently in production. We are always looking at ways to bring more gameplay to the Battlefield games. We never rule out adding more content to either Battlefield game and may even consider including community content as we did with Battlefield 2142 Update 1.50.
Q: Battlefield 2142 we were all to believe that 1.5 was the last patch being released by DICE for that title, if you could for the BF2142 community let us know what was the motivation behind the upcoming patch?
A: Part of the reason for Update 1.51 is obviously the security fixes for the game servers and clients. We also had the map waiting for release as it unfortunately wasn't ready in time for Update 1.50. So Battlefield 2142 1.51 was always planned to be released if only to let everyone get their hands on the new map.
While we can't always tell everyone the specifics of what we are working on we do have future plans for Battlefield 2 and Battlefield 2142 in 2009.
This is a great interview and even better than some others that were done in the past weeks! So be sure to stay tuned to GamersCrib.net (http://www.GamersCrib.net) as we focus on the soon to be released patches for both Battlefield 2 and Battlefield 2142!!
You can check out the original source of this interview here (http://www.cybergamer.com.au/article/331/).