Platform: Steam
Issue Type: Crash
Game Mode: Online Official
Server Type: PvP
Map: Isle of Siptah
Server Name: 6441
Mods: =MODS=
Bug Description:
Every Tuesday, of EVERY single week - Steam patches and takes down EVERY connection to EVERY official Conan Exiles server. It happens like clockwork. Even if this is not Funcom’s doing - it is incumbent upon Funcom to address this regular outage of its game property.
Bug Reproduction:
Log into an official Conan Exiles server on Tuesday at 5:45pm et. Either map. At 6:00pm et, or very shortly there after, you’ll be punted from whatever server you were playing on. Every week. Every Tuesday. Clockwork.
Please take some OWNERSHIP and some ACCOUNTABILITY and go fight the battle with Steam to make their platform redundant enough to not punt every Conan Exiles (and any other) players from their game.
The issue with WEEKLY, SCHEDULED crashes is due to a flawed gaming infrastructure. They are caused by the Steam platform. And the lack of redundancy either in the Steam platform, or in the game itself to tolerate the failure of the Steam platform.
Are you saying that you would rather us bring these very repeatable and very trackable issues to your attention via the ticketing system? I can certainly do that. However - I do not believe that would be good use of your ticketing system and your operational teams’ energies.
Please confirm that you want a flood of Zendesk tickets every Tuesday at 6pm ET from every player ever that gets punted due to Steam recycle… and I will make sure that happens.
This reminds me of the SOLVED classification of the BattleaEye issue even as tikets were pouring in.
But, not to worry, there was also community members being chastised for submitting a ticket each time it happened, even though the issue was reported as solved for each ticket.
The Official Server Performance requests are turned into alarms that go directly to the team responsible for server upkeep so they can look into the issue and try to fix it.
These are then closed by customer support to keep better track of the already-triggered alarms.
Please provide an update, or a statement, about how the Funcom team is working with the Steam platform to address this Single Point of Failure for the Steam infrastructure and the Funcom Live Service availability.
I have opened Zendesk tickets as @ZahMaiatt has asked. I have included all of the bug details here for reproduction of this issue.
YOUR authentication infrastructure takes a hit. Every Tuesday. Sorry - you are not going to pass this off on me. This is Funcom’s problem. I suggest that YOU ALL contact Steam at help.steampowered.com. And negotiate with them how they are going to make their infrastructure non-SPOF (single point of failure).
You know the beauty of regularly scheduled things? They are scheduled regular so you know they are going to happen. If you know some thing is going to happen you avoid it.
I know my server shuts down daily at 7AM, so I wait till 7:30 to log in. If you can’t manage to be ready for something you know is going to happen, that is on you. If you know a door you like to stand next to opens at a certain time daily you have two option, step back, or lean in face first. Seems you choice is to blame the door man or blame the door for you leaning in face first.
So I’m going to give you some perspective on this from someone who has been in the same place as @Cauthey.
No amount of preparation and planning makes up for what actually happens with this.
You’re probably thinking, “well why? I explained logically what you should do.” But yet again you speak without considering PVP. Let alone that there could be solutions.
Not everyone gets the boot
Not everyone gets the boot right away
Not everyone can log right back in
If you’re already logged out, you’re screwed until Conan servers adapt
Not everyone knows not to close the game fully
Not everyone knows to keep trying over and over
Not everyone knows that the error can be ignored while attempting to log in and just try again
Sometimes you get a second boot!
So there’s a bit of education for you.
Now as for PVP.
Means that the ones who don’t get the boot get free reign for however long it takes before others can get back on, this means potential offlining
It’s so random that it can even happen after the beginning of raid time while being raided
You might be logged in and alone defending your base, while your clanmates are desperately trying to log back on
No amount of trying to log in will make a difference during this process, so if you finished dinner with your family and promised to be during raid time but can’t actually play?
Backing entirely out turns into 4.
Most give up right away
Sometimes you have to press ok so many times
The second boot is the worst because it is completely unanticipated and can result in 5, 6 and 7.
This is for PVP NA EST, simple solution to prevent raid issues would be to postpone Tuesdays on those regional servers to 6:30 or 7.
But we are not talking about everyone. We’re talking about some one that seems quit experienced with it, aught to know what to expect, and what to do to prep for it, yet carrying on like every time it’s surprise.
The point I made is that doesn’t matter if you prep for it, it is never the same. Never the same exact time, never affects everyone the same, access elapse is different every single time.
It doesn’t matter if you have everyone on and remain idle doing nothing of substance so you don’t evoke risk. That is about the only prep you can do.
And if you decide not to log in to avoid it as a rule? The likelihood of getting offline raided is high, very high. Players watch the behaviours of others.
It would be different if it was a scheduled shut down.
