Are you suggesting to post this to the "poor netcode" subforum then? This doesn't belong in bug reports? It's "not a bug" to you?
Server desynchronization is when the servers network connection drops typically from power outages, overloads, random drops etc.
a replay is just recounting things that were confirmed to have happened in the match. it is replaying them. it cannot recount desync because it would just take what the server believes happened as truth. the server has authority both over what happens in the game and what is recounted as true in the replay. the server believes i meleed the soul.
Replays are not client side, you genuinely don't know what you're talking about. Have you ever looked at the replay viewer for any source title?
Desync is not a bug. This is not a bug. Which is what everyone has been pointing out. I'm not saying it's not an issue, but it's not a bug. It's like playing a fighting game that doesn't have rollback and complaining that everything that happens is a bug because the netcode sucks.
A replay pulls from the server, you even said, "this is not a playerside issue as it is present from the server's pov in the replay. " So are we walking that statement back right now?
"when the servers network connection drops typically from power outages, overloads, random drops etc"
Where would you post this then, if it's clearly not a bug and clearly doesn't belong in bug reports? It's a "netcode desync" (even though you can download the replay yourself) and should be posted where? Maybe stop posting definitions and start focusing on reading comprehension instead.
The entire argument started because someone said it wasn't a bug and Kitty got their feelings hurt because they were corrected. I just wanted to reinforce the fact that it wasn't a bug. No one at any point said it doesn't belong here as we are aware there is nowhere else to post issues.
yes i do know how to code and yes i know quite a lot about game networking. the replay is not from the pov of the player but rather a recount of what happened in that match according to the server, which has the final say on everything that actually happens in game. things like this may seem like desync when you are playing it live and communicating from client to server, but once its taken into the replay environment these factors that may cause desync are removed. the replay documents that the server fully recognized, with no possible desync issues, that i meleed the soul.
You are still dodging my question. If this belongs in bug reports, it is a bug.
Bugs can be replicated because it's an abnormality in the code. Which means if you fix the code, the issue goes away. That means that everytime you try this it should have the same effect. However I couldn't replicate the issue, which points towards it not being an issue with the code.
When are you going to download the replay and see that it is replicable literally every time you view it? Do you think that just because a bug only happens in some situations that it isn't a bug? I get this bug frequently, other threads report it, just because it doesn't happen literally every time doesn't mean it's not a bug and persistent issue. Even the server reports it as a hit without claiming the soul in the replay, and it does so upon every single viewing on every single machine. Why are you arguing semantics when everyone is just trying to get a gameplay BUG fixed?
just because you are unable to replicate the issue does not mean it does not exist. you are also testing this with a bunch of factors removed.
Thanks for posting clips of the serverside replay with sound!
No problem! It seems this bug is still persistent and thankfully easy to replicate after the patch! Hopefully it gets fixed soon, since it seems you're not the only one encountering this issue.
Did you watch my clips of the replay? It plays the audio and visuals of hitting the soul. The crosshair was directly on top of the soul during the melee audio and visual hit confirm, in slow motion, in my second clip.
