Do you have a link to your source for this? I've not heard of a court case about a ban for ingame profanity let alone Blizzard losing one. That said the rules (here and other games) are quite clear on what is and isn't allowed. The profanity filter argument you claimed was used as defense can be countered by: The rules clearly say no swearing, he agreed to these rules. Most mmo's with comparable rules to TOR (and WoW) don't tend to ban for profanity straight off the bat preferring warnings or limited suspensions first giving the player ample time to realise what they're doing and take more care.

True, but posting only positive or discouraging people from posting what parts of the game/service/product they feel need improved is not good for the game or the consumer. Rather than discouraging people from complaining, calling them names or saying "others have it worse so don't complain" it's far better for us all if people are instead encouraged to post their complaints constructively. Encourage people to discuss the good and bad so that Bioware/EA can get an idea of what people enjoy and don't. What they'd like to see etc. Yes I find the game fun, yes I've encountered very few bugs personally and while parts of the game do frustrate and have room for improvement the games still worth (imo) the money I choose to pay to play it. That doesn't mean I can't expect improvements and it doesn't mean I shouldn't criticise or complain when my expectations aren't met. 2 recent examples are the cartel coin issues (players not getting complimentary ones or ones they've purchased) and the companion gear bug that makes them very frustrating to use.

No. They said you would get the gametime by 11.59pm cdt on the 25th & it would then be added onto your current gametime. No. If your next payment was due before they added the current gametime you would have been automatically charged for your next months gametime as you agreed and then when it was credited the free gametime is added to the end of that. If your next payment date was due after the gametime was added then you wouldn't have got the 30 days without being charged another month. No scam, no having to buy more gametime to get your 30 days just timing that could have been better on handing out the free gametime.

Did they add the 30 days onto the subscription you just paid for?

I haven't really seen the "iso 8601" format used much, and didn't know it was a stndardised format. If so it's one that isn't used much. Personally I'd prefer it if they stick to the unambiguous DD <shortened month> YYYY format. It can't be misunderstood (well easily...). The credit card expiration date doesn't seem ambigious however. That's how the dates are written on the cards and it's fairly clear what it stands for so I don't think it needs changing. Best keep it the format on the cards/payment system to avoid confusion.

On what grounds? The email originally stated you'd get the gametime credited by 11.59pm on the 24th (a deadline that hasn't been reached yet). Even without the change you wouldn't have received the gametime yet and still been billed as it wounds like your next month was due earlier today Like what? What are they doing that's so evil? They're giving us 30 days gametime. Sure the investor report is soon, but so was patch 1.2 where they chose to remove something that was being planned to give max level players more pvp. So really you're just assuming that it's down to the investor report and making wild exaggerations and frankly laughable claims that they're evil because your irritated that you got billed today when you didn't expect to.

Well your banks opinion is all well and good but they still changed the valid date including updated information on the forums and the webstite. You believe giving people 30 days gametime is evil because it's around the time of the investor report? Well far be it for us to suggest you go against your conscience. I suggest you stand up for your morals and refuse to log in during your free 30 days as your protest against their evil ways.

Well they changed it to the 25th so you're not being charged the same day they're crediting the 30 days. Although if they bill the people the same day the 30days is due to be credited then I'd agree they could have handled it bettter.

Originally it was by 11.59pm CDT today ( a deadline that hasn't been reached yet so it was likely you would have been charged anyway) but now it's 11.59pm CDT tomorrow

Not quite. It was originally the 24th by 11.59pm CDT

But the app still works and provides the security it's meant to. Yes if you upgrade, replace or have to reset your phone to factory default you can't put on a new app. But that's not a reason to advise people not to get the app in the first place. It's a reason to advise people that there's currently a problem that's being investigated and if they're planning on upgrading soon they should consider this when choosing which app to get.

Yeah it's annoying that if you want to switch phones you can't remove your current mobile app and put a new one on once you've switched. That said I don't see why just because you can't get a new mobile app if you remove the first one is a good reason not to get the app in the first place. The app itself works fine, it protects your account and in the event of a problem with the app can be sorted by calling customer service. Why does the current problem of not being able to switch to a new mobile app justify not getting it in the first place?

http://www.swtor.com/community/devtracker.php http://www.swtor.com/community/forumdisplay.php?f=11

They are involved. They're involved in fixing those bugs and issues. Generally if they need information to help troubleshoot an issue they alert the community team who can then request the info, monitor the thread and then pass what's been collected onto the appropriate dev team. Sure I can understand why having the devs chat away on the forums might be nice, but all the time they're chatting away on the forums they're not getting involved in fixing the issue by working on fixing the issue.

http://www.swtor.com/patchnotes