Hi, I'm not sure if if it is a result of the recent updates regarding latency, but a number of players are experiencing unusual issues with fighting bots, especially guardians.
For example jittery movement, hits not being registered or hits from the side when facing opponent.
I understand that you like specific info, but screenshots are not effective in portraying the problem. I have noticed that if I leave the sector in skirms and return to the same bot I was targeting, the game runs as normal.
It is not a consistent issue, but it only recently become apparent.

/ping seems to be a lot more inconsistent now used to be stable 110 now jumping between 120-170

To add to this, I have been seeing the jittery movement, which I have reported in a ticket prior. We've kind-of narrowed that one down. However, there have been reports of invincible NPCs here and there, and I have a video of unrats to back that now. Something wonky is going on. It clears up if you jump out and the sector is allowed to sleep.

https://www.youtube.com/watch?v=X3QUUR-mKbY

Screenshots would not be useful, but location (in game), time and date would be.

Guys, please read the "how to report a bug" sticky thread:

https://www.vendetta-online.com/x/msgboard/2/37483

The information you're reporting is far too vague to result in any kind of improvements. We need specifics. Dates, times, platforms, device types, etc.

For the video I posted, I probably can't get the exact time but I can get pretty close. I have had another instance of this since but was unable to gather data at the time, so irrelevant. Hopefully this helps some.

Fedora 39, kernel 6.7.8
Ryzen R7 7700x
Radeon RX 6700 on AMDGPU kernel module, Vulkan in-game.
Vendetta fully updated via updater
That video was uploaded at around 12pm CST, the event there was just before, so I'd estimate 3/26/24 at around 11:50 or 11:55am CST?

Thanks. We are going to look into this further. In the meantime, if people encounter specific issues, please state the date/time and in-game location, at least.

If possible, please try to rule out any normal "network lag" and only report situations that are really extreme. Like, whether your "ping" is inconsistent is not that meaningful, routing on the internet changes all the time.

But, in-game NPC situations that are really extreme, and occur even with an ostensibly "low" and stable ping, those are more useful to examine.

We've identified some potential problems, but it's a bit complicated and will require further examination and data-collection before we can narrow down the exact issue.

Please continue to report dates/times of specific problems with being unable to hit NPCs.

Sunday 31st March at 17:47 GMT

I was playing with the character "Evil the Bat" and killing the unrat trident. I jumped in and fired a out half my payload at the dent, watched them hit, but got no hit beeps or inflicted any damage. I fired the other half and got the same result. I jumped out to reload at the station and the dent took damage as normal when I returned to the sector but still showing no damage from the previous attack.

No other players in sector.

Im playing on a windows pc, its hotspotted to a mobile connections which I know is far from ideal.

So, yeah, we are still struggling to figure out exactly what the #@!$ is going on here. There may be several different problems with similar symptoms, we aren't quite sure. We can't reproduce any of the reported issues, and our logged data is not proving as helpful as we hoped.

Please continue to post dates + times + sectors of cases where you cannot damage NPCs.

Okay, after some further analysis, we think the actual problem that started this thread was addressed last Friday, March 29th. The restart on this date caused a major drop in spurious problems we were having with basically "Hit-check confirmation", which is an anti-cheat function of the sector, as well as time synchronization issues on the sector-side.

The problem had been induced by a bug released on March 6th, and then was fixed on March 29th.

Everything in here, other than the issue reported by mybeatsarebollox on March 30th, can be explained by the known-bug (and not like "hands-wavey" explained, we have definitive logs that show the issues, and map to the bug specifically).

So, I'm going to go ahead and call this issue "fixed". And then also raise that some OTHER issue may exist (what mybeatsarebollox experienced).

But, if that happens again, please create a new Bugs thread for it.