Thank you for the report.
This has been reported previously and it is being worked on. Closing the ticket as it is a duplicate.
Regards,
Geez

Hello HideoutKitty.
Is this the same issue as described here? https://feedback.bistudio.com/T191109

Hello, we have tested this on our end but we were unable to reproduce the issue.
Regards,
Geez

Hello, we have tested this on our end but we were unable to reproduce the issue.
Regards,
Geez

Hello, we have tested this on our end but we were unable to reproduce the issue.
Regards,
Geez

Hello Jaakael.
We have tested the weapon but we could not find any issues.
Regards,
Geez

Hello AJinDaHouse.
This is intended for the time being.
You can find the server you were connected to in the "Recently played" tab of the server browser a minute or two after it shuts down.
Regards,
Geez

Hello TPMTactical.
It does work as intended - with -autoreload disable server should hang on 00:00 timer and never restart until its manually shut down.
For the desired result, the -autoshutdown CLI parameter that was introduced to ensure correct server shutdown process.
Regards,
Geez

Hello Baato.
Can you please show us what is the "unstable" icon?

This is happening more often in 1.3 stable.
Also a variation of this bug is when the handheld radio stops working and you don't even get this red icon on top of speaker icon.
Sometimes respawn doesn't correct this, sometimes it does.

You seem to be having connectivity issues. Inability to fully connect to the server or freezing of the game is usually caused by the Internet. Try restarting your modem and switching servers.

These mass bootings with error 6 STALLED affect all platforms and seems to be more frequent after 1.3 stable. Saved loadouts are gone after reconnecting as well radiobackpacks if you were solo in the squad or all squad members got the boot.
There must be something that BI can do about these mass stallings? It is a everyday scene to see 5-10 ppl get booted at once and then they reconnect and after a while it is time for another batch of ppl to get the boot and this just keeps happening and happening. Every server, every round. Why isn't this talked about more?

These mass bootings with error 6 STALLED affect all platforms and are a pain in the a** for players.

This isnt caused by some random software because this affects PS5 and Xbox as well. Ppl get mass booted from servers every now and then and most of the time it is still STALLED error that ppl get. This should be nr. 1 thing that BI should be looking into.

In T168922#2796021, @C4pt41nNo0b wrote:

But could you be more exact in how the suggested "disable platoon channel" feature/functionality would have to look like or work?

So far tonight, I've had this happen a few times.
I've been able to get back in if I exit and rejoin quickly from the Main menu.

Just add server side options to set minimum values for these settings. This way PVP server admins can limit these "cheats" while in GM/PVE/single player can still enable minimum values if they want to.

There has been a lot of requests in other forums (reddit, steam, discord) to make platoon chat only available for squad leaders.

I have encountered this issue every now and then with Ps5. It is a rare bug.

Dude I shoulda mentioned I'm on a mobile router but it's never mattered! The router doesn't have upnp or anything, so it just had too strict of a NAT type. I reset it a FEW times yesterday to be sure

Oh Lord God no, it was an internet issue

well said

hey @Gabrenth
you can upload video like a file, use upload button (cloud icon on editor bar)

Ahh. Turns out Experimental does the same thing

Any idea of when is 2.20 going to be released? I heard it was expected for February, and here we are in April...

This is the same for cars. You often have to press it twice.

Hello Oleksii.
Is this a community or official server? Does the server run any mods?

In T191304#2796536, @Vextrela wrote:

Yeah all servers and all characters, but it always resets to the dead character in lobby. So with the exp files copied over, I'm just getting a "wrong version" error at this point. Any way I can trick it into thinking it's the current version?

Here's another report using the Experimental

Looks to be fixed. I had to make sure reset="1" to see my changes, without waiting.

Yeah all servers and all characters, but it always resets to the dead character in lobby. So with the exp files copied over, I'm just getting a "wrong version" error at this point. Any way I can trick it into thinking it's the correct version?

In T191227#2796473, @Geez wrote:

We have noticed you do not have it enabled in this line:

<weather reset="0" enable="0">

Could that be the issue?

But you also mention it occurs across all servers. Not all servers share that one character.

Like when the game goes to load the server, the lobby view of yourself acts as if it's going uncon. Like....that's not in my files.

It was just having loading errors and crashing. Really does seem like it has something to do with not hitting respawn after dying. Seems that it's causing an issue on the servers' side. The servers are seeing me as dying.

Hello everyone.
There are some changes in 1.28 which could improve this issue. Can you please test this problem on current experimental version and provide feedback?

Thank you for the report.
This is a known issue and has already been fixed on our internal version. The fix is coming in one of the future updates.
Regards,
Geez

That's a great idea

Can you check if experimental works? And if so, disable the Steam cloud sync, delete the contents of your DayZ folder and copy over the DayZ Exp folder contents into it.

All servers and everything. Bro I reset my entire PC. I've deleted every single file every single where by hand over and over again. I didn't hit the respawn button now it wants to fade me to uncon instead of loading a server.

Hello Vextrela.
Is this just on a specific server or multiple servers are affected?
Also have you tried to disable Steam cloud sync and delete the DayZ documents folder?

How to fix it?

We have noticed you do not have it enabled in this line:

Hello FreaknPwNed.
With the config you have provided we have foggy weather on our testing server. Is there something else that could be wrong?