Pimp my tank bitches.
Welcome to PBBans
|Welcome to PBBans, like most online communities you must register to view or post in our community, but don't worry this is a simple free process that requires minimal information for you to signup. Be apart of PBBans by signing in or creating an account.
Posted Jul 11, 2012 - 01:31 PM
Blue tinted maps.
Blue tinted menus.
Posted Jul 19, 2012 - 08:38 PM
Posted Jul 19, 2012 - 08:53 PM
No idea what this contraption is. Looks like a noobus-maximus. No doubt a noobs wet-dream. You'll also notice that the mini-map now displays the flag letters on the icons!
Looks like some sort of super-tank (M1/US variant) with an extinguisher!
The super-tank (T90/RU variant) with armour-plating on the front! (Y) And as the kill-feed reveals it's a Sprut-SD.
Click on the pictures for bigger versions
Edited by Singh400, Jul 19, 2012 - 09:04 PM.
Posted Jul 20, 2012 - 12:56 AM
Now that is what its all about. Can't wait for armoured kill. (with the correct spelling)
Posted Aug 14, 2012 - 11:22 AM
Posted Aug 14, 2012 - 02:08 PM
Posted Aug 17, 2012 - 04:48 PM
At GDC Europe this week, Karl Magnus Troedsson, general manager at DICE, explained why this is the case -- essentially, DICE is scared of the implications of giving players access to parts of the game's code.
He reasoned that, while the company is very much aware of how important modding can be for building up a game's longevity, "we're afraid of all the things that can come with releasing the code."
Giving players access to certain parts of the code would potentially leave it open to hacking exploits, he said, and this is something that DICE is not comfortable with at all.
Adding to this, he noted that Battlefield 3 is not just a PC release, but also available on console, and that if DICE was to accommodate modding tools, it would want to provide these to console players too, which is rather more tricky.
"If we do mod support, we want to do it really, really well," he reasoned. "We are not ready to do this yet."
Posted Aug 17, 2012 - 04:59 PM
Posted Aug 17, 2012 - 05:01 PM
Karl Magnus Troedsson, general manager at DICE, explained at GDC Europe that DICE was afraid of releasing the mod tools for Battlefield 3 because they were scared of giving players access to parts of the game’s code.
As Gamasutra reported, DICE is very much aware of how important modding can be for building up a game’s longevity, but they’re afraid of all the things that can come with releasing the code. This basically means that the release of mod tools would leave Battlefield 3 open to hacking exploits, and this is something that DICE is not comfortable with at all.
In all honesty, this is a bunch of crap. DICE is simply afraid of ruining its DLC plans and that’s why they are not releasing those anticipated mod tools. It’s really sad, because the team behind BF3 and Bad Company 2 are modders themselves, that made their debut in the gaming industry via the Desert Combat mod. These guys should know how important are mod tools. These guys should be more friendly to the idea of releasing mod tools. These guys should not be lying to us.
Those ‘hacking’ excuses are as bogus as the fact that Frostbite 2 was a really complex engine. DICE can easily tweak its netcode, but then again, Battlefield’s netcode was a mess all this time. In fact, there are already a lot of hackers that have not been punished yet, and let’s not forget that each and every patch brings new glitches to the table.
It’s unfortunate, but DICE lied to all gamers about both mod tools and Battlefield 3′s maps. Remember when they said that they would not charge for maps and that they would not follow Infinity Ward’s example? Well, we all got our answers with Battlefield Premium and the awful Battlelog browser.
Unfortunately, that’s the truth behind those rumored mod tools and why DICE is not releasing them. It’s not about hackers invading Battlefield 3. It’s not about Frostbite 2 being a complex engine. It’s because those mod tools would ruin DICE’s and EA’s business plans. And that’s a fact!
Posted Aug 17, 2012 - 05:13 PM
Posted Aug 17, 2012 - 08:36 PM
We've exchanged a substancial list of expectational features, for a browser based game and a kiddie "battlelog" to keep track of stats?
Line from Animal House comes to mind: "Thank you sir, may I have another?"
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users