Re: DRM in Dragon Age II:
Dragon Age II does not use SecuROM DRM. Any statements made to the contrary are false. The confusion stems from the use of Release Control which is also made by Sony. Release Control was employed to protect the game against usage prior to its release date. These are two different technologies with different purposes. Release Control in no way affects users’ rights to access after launch, and its executable automatically deletes itself once the Release Control process is finished. For more information, please visit: http://support.ea.com/app/answers/detail/a_id/4921.
Re: the account issue from one player at Social.BioWare.com:
EA strictly enforces the code of conduct at Social.BioWare.com. If a player violates the rules by using profanity, they will be temporarily banned. Unfortunately, there was an error in the system that accidentally suspended a user's entire account. Immediately upon learning of the glitch, EA took steps to restore the user's macro account and apologized for the inconvenience.
Golwar wrote on Mar 14, 2011, 06:27:And you are going to trust EA or other developers to accept a certain level of profanity rather than a zero tolerance policy? EA just said they "strictly" enforce it. Remember that free speech doesn't apply on forums such as these, whoever owns the boards can enforce as restrictive or as loose of a policy as they want. There's going to be a wide range of acceptable behavior on game forums. Some will tolerate just about anything or ignore or not bother to police them. Others (especially where they think they could get in trouble if kids read it) are likely going to be far more restrictive.
Imho a developer has to accept a certain level of anger and bad mouthing from its customers. If players break rules and attack each other, ban the initiator. If the developer causes the mess with his product, show at least some style and don't ban left and right.
Dev wrote on Mar 14, 2011, 06:15:Golwar wrote on Mar 13, 2011, 19:18:You realize that the above word is profanity and could have gotten you banned from playing a game you owned had you posted it on the EA/Bioware forums?
And as we didn't hear from more similar cases, why not trust them that it was a unique mistake? I'd be more pissed about being banned for such simple shit as in that case.
Golwar wrote on Mar 13, 2011, 19:18:You realize that the above word is profanity and could have gotten you banned from playing a game you owned had you posted it on the EA/Bioware forums?
And as we didn't hear from more similar cases, why not trust them that it was a unique mistake? I'd be more pissed about being banned for such simple shit as in that case.
D4rkKnight wrote on Mar 13, 2011, 17:16:
Gamers are losing control of the products they purchase, this was not about a bug, its about the company stance. EA and Bioware defended this position, to them this is entirely expected and normal. Arguing with them is not going to change that, hurting their reputation and damaging their sales will.
Teddy wrote on Mar 13, 2011, 17:04:
Irony is such an interesting thing.
If there are bugs in an EA released game, gamers will say "Of course there's bugs, EA can't release a game without bugs. They don't quality test worth a damn!"
Yet when EA says their website software had a bug in it, all of a sudden to these same gamers, it's inconcievable that EA's programmers could have made a mistake, or that the positively thorough testing that EA puts their software through didn't catch it.
Yes, it must be EA lying to hide their nefarious plots and couldn't possibly be related to ineptitude or lack of Design or QA attention.
Kosumo wrote on Mar 13, 2011, 16:45:
Same as the nice try of Reclaim Your Games (still m.i.a.) at slandering the game with claims of SecuROM, which have not even close to be proven right yet people are posting it like it was a fact.
Just like ASeven, I hope this leads to a lawsuit, one in which EA sues Reclaim Your Games for slander.
there was an error in the system that accidentally suspended a user's entire account. Immediately upon learning of the glitch, EA took steps to restore the user's macro account and apologized for the inconvenience.