"You've launched this game on too many devices in the last 24 hours...."
Really?! This kind of lock in an age when people use cloud services to play their games?!??!
This is the most absurd error I've come across in my 30 years of gaming.
I've always had a bad experience with EA, but this takes the top! It's not a mistake a programmer skipped, or a bug, or rushed development. This is intentional!!!!
I've spoke with the technical Support and they couldn't help my with this issue.
The 'excuse' was that DRM is used to protect IP from piracy. But this has exactly the opposite effect. Next time instead of being a customer, I'd rather try to pirate the game (or not play at all) since it provides a better customer experience not having to deal with such problems arising from 'owning' the game.
Specially when considering cloud services, with many users only having this option available for them. As a consumer, I'm inclined to stay away from EA for the rest of my life. If at least the support team could lift this lock, I would be feeling better than now. Since they can't, it feels like I've been cheated. Therefore in a business context, I'm not a returning customer!
This is a terrible business proposition, and some execs might even argue that it affects only a small share of their revenue, but this small-shares little by little will cut away a huge share of the business. Specially considering that EA has had a long bad rep in the last decade, being awarded 'the worst company in America' multiple times. EA needs to reconsider it's policy!
Penalizing customers while trying to secure revenue IS NOT a sustainable business practice!
Average EA stupidity. Hope they'll find a fix for this, but it's EA, they don't care about us.
EA Play subscribers roughly doubled from 6.5 M in 2020 to 13 M after bundling with Game Pass, a period coinciding with explosive growth in cloud gaming usage and infrastructure.
Strong correlation in timing: cloud gaming ramp-up and Game Pass bundling align with a doubling of EA Play users.
From SurveyMonkey (circa 2021)
* 21% of gamers subscribe to a game subscription service (e.g., Xbox Game Pass, PS Now).
* 10% play via cloud gaming.
* 7% subscribe to both a subscription pass and a cloud gaming service
Although there's no much data to prove a causation link between the rise in cloud services and EA Play subscribers, I'd argue this is no mere correlation! Given that with a cloud service, users can now play games without a high-end device (and also users coming from systems such as MAC and Linux can now play as well), I'd argue that the rise in subscriptions and sales is caused (read CAUSATION in statistics) by the rise of cloud gaming services!!!
Community ManagerHi neubern,
If you see a message like: "Too many computers have accessed this account’s version of [game name] recently. Please try again later." - or something similar - this means you’ve hit the limit for the number of computers that can access your game within a 24-hour period, as outlined in our Terms of Service.
Here’s what can count as a “new” computer:
You’ll need to wait up to 24 hours before you can launch the game again.
This is NOT a solution. This seems more like a work-around than a solution!
The problem still persists! AND the problem is: Consumers are penalized by bad though business practices.
I'll most certainly continue having this problem, since as I stated before: I play using cloud
And I'm not the only cloud user around. The feeling we have at the end of the day is: Stay away from this company, because they prioritize pirates rather than their own consumers! And truth be told, this is a stark reminder WHY there has been a surge in piracy in the last years! Bad service which pushes consumers to seek alternatives.
The solution, and ONLY solution, is take this "feature" away, and let people install and play in multiple computers, SPECIALLY if they are cloud users. At least whitelist the computers which are cloud based! It's so easy, and yet the real solution seems to be in a galaxy far far away.
Community ManagerI appreciate the feedback, but since there’s unfortunately no way to change this behaviour in the client or its connected services, this thread will now be closed as the correct solution has been provided.
