Platform: PlayStation 5
Issue Type: Gameplay
Game Mode: Online Official
Server Type: PvE
Map: Exiled Lands
Server Name: 3890
Bug Description:
Decay Timers are not resetting under very specific circumstances
Bug Reproduction:
I did quite a bit of searching, and I finally found a link between the number of builds that are not decaying on our server. I was the only player on line early in the morning, and I consistently found builds that were at 240:00:00 or just a few seconds under that.
These are builds where the thralls are gone, and most of these clans had multiple builds. All of the other builds decayed, but they have one that the timer reads almost full to full all the time.
Here’s what I found: The player’s body was completely visible, either engaged in an emote or floating above the ground running in place. After testing, we found that we could replicate this build quitting the game and turning off the PS5 BEFORE we get to the title screen, effectively freezing the logout.
I have found players floating, dancing, and even in the sleeping emote. Yes, I can tell it’s the sleeping emote because their stats are clearly visible, and it does not say “UNCONSCIOUS”
Bottom line is pretty simple. Some of these builds are large. They take up space that an active newer player could use. I think that it will sort itself when the update hits, but you never know.
Interesting and kudos for the detective work, but i just wonder how the hell you can emote mid air.
If you forcefully disconnect by turning off your machine, regardless of what your character is doing it just has you floating mid air and repeating whatever looping animation your character is set to?
Either way, good find. Can’t imagine doing that is risk free for both your character and console but i’ve known people who did that and still do for years, so i guess there’s plenty that treat their hardware like garbage.
Honestly, the more I look into this, the less I think Funcom can actually do. This appears to be a Playstation communication thing, and I think it has more to do with the way the servers and console interact than anything else. An update may reset the characters, but I just don’t know.
Maybe just closing down the app/program forcefully while in an emote is already enough to cause this, then? I know Xbox and PC can both do this. Not sure about Playstation but i assume it’s possible on that as well.
To be clear, I only found 2 players in emotes. The rest are running in air.
That said, last night, I was going to get a picture of one of the players, and I found him laying with “UNCONSCIOUS” over his body. The timer was down 24 hrs as well. So, he was reset. We’ll see if it decays normally in the next week.
Certainly evidence that emotes play into it with those 2 you saw and the rest performed.
It is of course plausible that players were emoting then the game crashed or they force closed it.
Others have reported similar, swimming/falling or emoting logged off players.
But I wonder if there’s a connection with players logging off where wires are crossed somewhere with player animations in general? When you think about it, there’s various states of showing as logged off while lying down. You can be on your back, side, etc.,… Essentially emoting?
Maybe the swimming/falling is that disconnection from the regular sleep state… And if you purposefully emote, it’s also overriding that state.
Then because the game can’t put you into the proper state the server still thinks you’re logged in?
I think maybe unconscious player loses contact with ground after server restart and floats.
You can kick them around and they would move up down or whereever you kick them.
I first thought it has to do with falling through fundation problem.
But then I was finding floating bodies that were not on fundation.
Possible funcom did on purpose for making bv harder?
Spent some time exploring. Here’s some visual evidence of running in air and full timers. I think maybe when the player body disappears, this problem fixes itself.
While I have noticed this bug with players recently, I’m not entirely certain it’s completely connected to the timers. I noticed quite a few bases on siptah doing this refresh for longer than this bug has been present. It was as though I was refreshing their bases for them. Maybe it’s a different bug, but the result is the same? Maybe it’s a coincidence? Idk.
