[TERA PC & Console] En Masse is closing, but TERA lives on! We will continue to support TERA PC (NA) and TERA Console until service is transferred. Stay tuned for more information.
[TERA Console] The Grotto of Lost Souls update (v85) is now live! Read the patch notes here: https://bit.ly/TERACon_v85
[TERA PC] The 64-bit update (v97) is now live. Check out all the changes delivered on August 11 here: https://bit.ly/tera64_patchnotes
[TERA PC & CONSOLE] Summerfest Part 2: The Beach Bash is on from August 11 until September 1! Participate in event activities to earn tokens redeemable for costumes, consumables, mounts, and more! Details: https://bit.ly/tera_sf20
Comments
They did put it in the launcher.
As an systems architect and engineer I can quite confidently state that old accounts (assuming unused) would "stack" (as you say) only for storage. Unused accounts should then only account for data at rest. There should be no impact on server CPU or memory utilization for such accounts.
I dont mind them taking however long they need to fix this but obviously they arent fixing anything. Servers are up now and there are ping spikes for over 100+ms every few seconds making it horribly unplayable , at least for me .
Before all the smart people come and tell me its my connection or whatever dont bother, i've tried everything and i also played other online games while this one was down and guess what. I had 0 problems with ping or random disconnects.
This game never ceases to amaze me of how unplayable it is every single day.
EME is incapable of even touch 3 nines (99.9%) which is a downtime of 10 minutes per week. Their server availability is somewhere between 98% and 99% (2 nines), just over 3 hours per week and just over 1.5 hours respectively.
You're making a big assumption about the cause of crashes in this case. Keep in mind that the server tech for this game is ancient (and, we can safely say, poorly-written). For these types of legacy apps, "Platform as a Service" is not all that much more than a more-automated colo, and when the server crashes... it still crashes. Deploying updates is still a matter of stopping the server, installing the patches, running DB update scripts, doing your other maintenance tasks, and then bringing the server up -- the oldschool way. There's no rolling upgrades, no seamless failover, no container replicas in Kubernetes/Swarm, or anything like that.
If they moved to a different PaaS provider, at least perhaps they might have better routing, so that's a thing. But I'm not convinced it'd have much impact on uptime for a legacy server app like this.