[2020] Netcode issues today.

I have noticed that sometimes my rockets go straight through my enemy even if they deal damage like a direct hit.

There is a known issue where the visuals of the rocket will keep going if that rocket kills the player. We'll fix this. This is a cosmetic issue with no logical side effects.

Also I have seen enemy rockets go straight through me without dealing damage to me. I play on 20-30 ping.

A lag episode may cause this. We are going to implement a lagometer component into the hud and it should allows us to understand and act upon feedback like this better.

Consensus seems to be that the particular issue this thread is about is fixed, so I'm assuming you have older issues. Regarding the shaft, we have identified a potential problem that would make hit registration specially bad with shaft among other things if you are having some lag/packet loss to a server. Look for a patch note mentioning shaft in the next versions.

Regarding the ghost rocket, there is a known ghost rocket issue about rockets that kill somebody then continue on but it's purely cosmetic and it's not a real rocket at that point (we'll still fix it as soon as we can anyway, of course). Lag could also potentially cause some other issues described as "ghost rockets". We are going to add a lagometer and you should be able to see if you are having lag episodes to our server or packet loss.

Regarding anticheat, the person that is in charge of that was swamped this week and we haven't been able to process all cheat reports during the week. These reports take time to process because we want to avoid banning people wrongly. We are doing some changes to our backend so that this process is more efficient. Enforcement of anti-cheating should be way better in the future than what you've experienced. Really sorry that you had such a bad experience.

About the netcode issues that you mentioned in your DM, the netcode as you experienced it last night is not a true representation of the game, in case that weighs into your negative impressions. There are other general issues with the netcode that we know about and we have a few fixes coming that should give you, at the very least, a sense of progress.

We'll win you over some day Mr_Picky. Appreciate your passion for the genre.

I would like to see it if you can find it to add it to what we have, thanks.

Yeah I know the issue, just collecting evidence, that way when it's fixed we can go through all and check that they all match what has been fixed.

Pretty sure in most cases this is about the way we present projectiles/beams in 3rd person. They come from the actual muzzle of the rocket launcher in the case of the rockets as the weapon is animated at that moment. This makes it so that you can get rockets going through corners if the weapon of the shooting eggbot is occluded by the corner. The severity of this is exacerbated by the wide span of the eggbots and the way they pose for shooting. Then the severity can increase beyond that due to network conditions that make that position diverge from the position of the eggbot. The severity can also increase even further if there's a visibility problem when determining the position of the muzzle (as an optimisation we don't resolve joint positions in things that are not visible, in that case the logical position of the player is supposed to be used, but there could be an issue in the logic that manages this switch of positioning mode.)

What we are going to do pretty soon is just have the rockets come from the centre of other players. We'll probably do this with all projectiles and beam weapons except shaft. This should address or alleviate most of these scenarios.

Don't get heartbroken yet man :) We are gonna add a lagometer to the game, when we do if you haven't given up on the game feel free to drop me a screenshot on DM either on Reddit or on Discord. I think you must have some packet loss issues that are exacerbated by an issue that we are planning on fixing. Whatever the case, we'll get it fixed.

TY for reply

You are welcome. And fair enough Mr_Picky, I see you are not ready to accept my theory that the package loss issue is making you think all that. Let's agree to disagree, and I will keep your advice in mind :)