Minimum product viability.
The scale of EVE does not permit half-baked solutions, I’m afraid.
Discord would just die under load of thousands channel switches per minute.
You guys CRY TO CCP “WHY ARE WE GETTING DC’ED WITH SUPER LAG IN MASSIVE BATTLE’S” then when they try to separate the parts that cause the most lag you guys cry again things will only get better with time, wait it out.
The old system worked(ish)
The Amazon Cloud works(ish)
Is there anything that would really suit EVE?
“things will only get better with time…” Say what? Since it’s been 10 months already with no signs of any improvement at all, clearly things will not just get better with time.
When a software company has not fixed or improved a problem in 10 months, it usually means that either (1) they aren’t focusing resources on it, or (2) they don’t know how to solve it. Sometimes it’s both, but there is no such thing as things just “magically” getting better with time when either software or software organizations are involved.
I can also assure you that a constant stream of complaints are pretty necessary in helping to motivate software companies to fix something. Managers have a remarkable tendency to ignore any problem that customers are not actively complaining about right now. Without their support and focus, it’s pretty hard for individual developers to do much about a problem since they don’t usually have much if any discretion to solve a problem on their own. Developers have to account for their time, and if they aren’t making progress on whatever it is that their manager currently cares about, they get in trouble.
Even with active complaints, CCP has a long history of being fairly deaf. Without them it would be even worse.
It’s not “amazon system”, it’s “ejabberd hosted on amazon”.
That’s two separate issues.
What would suit EVE? I said that earlier - move chat servers back to the same datacenter EVE is running from. If not solving the issue completely, it would reduce connectivity issues (both between clients and chat servers, and between chat servers and the game itself) to buy time for finding a more permanent solution.
Yet again: OLD CHAT SYSTEM, DEEPLY EMBEDDED INTO GAME ENGINE ITSELF, HAS TO BE GONE.
EVE is not a chat client, and having core game mechanics being dependent on communication service is intolerable.
Did you submit a support request? No? Then what did you expect?
chat hasn’t been broken for 10 months straight lol your exaggerating like crazy xD, it had a few issues 10 months ago then they sort of fixed it then it broke again and they sort of fixed it and it broke again and they are fixing it, eventually they will get to all the bug’s.
The advantage of wormhole over nullsec is that you don’t happen to have 20 caps on you in like 3 seconds because of cyno. That’s why chat is mandatory in nullsec, to not get caught by a dreadbomb (that can’t happen in WH). If chat should be removed, then the same should go for cyno/jump drive, so you would have to gate a dreadbomb if you wanna drop someone …
If it is the local join and quits overloading the new chat… funnily enough removing local should stabilise the entire system.
Constellation chat might or might not need removal also.
But there is always region chat I think.
Jita chat has been broken for 2 weeks straight during permafrost event and nothing has been done about it. Other chats misbehaved as well. Thats not an exaggeration.
Who cares about JITA chat thou most of those people are muted anyways. Corp chat, intel channel’s and so on I can understand.
It’s not an exaggeration to refer to the problem as having existed for 10 months. That’s when the implementation and configuration changed, and the intermittent symptoms we’ve seen started then. Simply because those symptoms are not omnipresent does not mean that chat is not effectively broken.
CCP may have attempted to fix the problem in the interim, but that does not mean chat is going between states of “fixed” and “broken” for alternating periods of time. That’s not how most software problems work: even when it appears to be working, it’s still broken because those symptoms can manifest at any time without warning or any ability of CCP to stop them. That those problems appear means that local chat is no longer reliable and cannot be fully trusted to show all player characters present in a system.
Although chat has most noticeably manifested symptoms in Jita throughout the 10-month period, I saw occasional problems with local not working in some lowsec systems at least as far back as June of last year. I reported those as a bug at the time. These are still the same symptoms we are seeing now because it’s the same problem. Nothing has changed.
You lost reliability when you migrated to the cloud. Chat is one of those programs that you can’t be less then 100% reliable. It should have been evident the first week when it forced the reset of the game on multiple different occasions.
Take your time and do the updates right. Take the time to test them and keep the team working on it through the patch date instead of new projects like four months out. It doesn’t do anyone any good to keep having to remember how something was done and why it was done a certain way only to forget and have to fix it and break something else.
guys even that we all know ccp lacks the basics in communication towards the playerbase and prefers to ignore us completly from theyr pedestal
still a bit of decency is also important from the playerbase
why not use the old and reliable chat service, which most armed forces of several countries still use, I R C, and is open source.
another thing that migth help with current chat situations. reduce the stress on the chat server by moderating major hubs with a post for each 10 mins.
also another sugestion is that when tidi kicks in to a certain lvl. lets say 50%. local chat gets moderated to NO POSTS. this will also prevents that people involved on the figth and losing it trys to crash the node. to save loses on the on going battle.
Man you nailed that one with one sentence. It was awful. XD
Because there needs to be a way in game to talk to other in game players. The idea that people just migrate to other outside game programs is nuts. Crashing the nod by sending strings of text could should be fixed, but not by eliminating functions of the game. That’s equivalent to too much damage on the damage cap so they don’t let other ships fire because the nod can’t handle the animations.
Be the first one to demonstrate it?