So i think youre misinterpreting when i told another person in the thread that they dont use local for their core gameplay meaning i said he didnt have friends to communicate with, im really sorry it went over your head but maybe you also dont communicate regularly enough to have it trained! so sorry!
Chat is currently working for me, and out of the 35 people I’m flying with at the moment only three were reporting issues. I had hoped that wasn’t an anomaly.
My chat has worked for 10 minutes starting at downtime, nothing since then. Restarted 10 times and every time the only channel that loads is “Rookie Help”. I haven’t even used this channel in months but consistently is the only one loading.
There are millions of lines of code and algorithm in the game. Localization alone can be tens of thousands of lines long. Trying to keep that consistent is impossible, and is why every game older than a year tends to suffer from spaghetti.
You’d only think that anyone would understand every line of code and algorithm if you have no idea how it even works. People leave, people forget, a comment isn’t left that doesn’t explain the purpose of a line of code but deleting it breaks the game so you leave it in, you have to do weird stuff to get things to work such as a seemingly useless IF statement. Etc.
True, expecting any one dev to know all of Eve’s source code is unrealistic. Being able to simply look at a commit diff to see what things they changed in the patch that broke the universe on the other hand…?
Bug fixing isn’t that simple. They likely are looking back at what changes they made, but it may not be due to those. It could be a random bug that spawned in the servers or a piece of code that corrupted, somewhere. Maybe there was a 1 that was meant to be a 0. There are any number of causes, but since the chat going in-and-out, it isn’t a static cause which makes it all the more difficult to pinpoint.
It seems like they might just replace the chat entirety with the new local that actually works. That’ll probably be simpler than trying to track down whatever rogue code is causing the issue.