Kill and damage recording

[dandare9]

I have made quite a few .bugs about this issue of non recording of kills/damage.  I can confirm that this issue of my kills and damages not being recorded are being copied exactly without correction to the CS&R page.

It's more than a bit irritating as I am having problems where I think I may have killed a tank or an ei but have now to mark it up, just in case, as when I despawn I get no record of the action that took place.

Why I get one damage when I have definitely killed 2 and damaged at least one other contact and despawned later beats me. Logic says it should be all or nothing during one mission.

I hope you find out what is happening soon. 

Thankyou.

Dandare9.

[FRISBONE]

This is at the top of our list.  

[GrAnit]

I think that if you despawn before the other person you killed despawns, it 1) may not show up ever, or sometimes 2) it shows up after your next mission. It is a very wanky system, however, and needs to be fixed.

[VICTARUS]

Damn stat hos, distracting me from working on the fun stuff...

I can't give an ETA on the fix yet, but I'm hoping a little insight based on what QA has determined so far might assuage some concerns:

• The issue seems to occur when crossing between cell hosts: If you're on A and hit someone on B, the actual record of that hit is being lost for some reason.
• This does not actually affect damage in any way: The only thing affected is the hit being recorded so it can be added to your stats.
• This also doesn't affect kills: Kill reporting is its own thing, which is why you may see 0 hits and 1+ kills until we fix this.

So yeah, that's where we're at right now. Hopefully it won't take too long to figure out the underlying cause and deploy a quick fix to the host.

[dm79]

5 minutes ago, VICTARUS said:

Damn stat hos, distracting me from working on the fun stuff...

I can't give an ETA on the fix yet, but I'm hoping a little insight based on what QA has determined so far might assuage some concerns:

• The issue seems to occur when crossing between cell hosts: If you're on A and hit someone on B, the actual record of that hit is being lost for some reason.
• This does not actually affect damage in any way: The only thing affected is the hit being recorded so it can be added to your stats.
• This also doesn't affect kills: Kill reporting is its own thing, which is why you may see 0 hits and 1+ kills until we fix this.

So yeah, that's where we're at right now. Hopefully it won't take too long to figure out the underlying cause and deploy a quick fix to the host.

That must be the same thing causing the fire and engine bug, players on different hosts not picking up the stop command?

[Merlin51]

11 minutes ago, VICTARUS said:

This also doesn't affect kills: Kill reporting is its own thing, which is why you may see 0 hits and 1+ kills until we fix this.

Not to toss more on your plate, but it kind of is doing the 0 hit + 0 kills things

The dead things are still dead, the other guy has lost the units, you just get no score or feedback about it.

Last night at Cobreville i wacked 4 tigers, in rapid succession (Frontally with the S76, range 400m) and several EI before losing my gun to a stug and having to run back to the FB for a refit.
On RTB i scored 2 kills 0 hits. (CSR reflects same)
(video to come soon)
Its ok because there were no more tigers for them to spawn on our attackers, which is of course the actual goal, but it was a little deflating.

And yes, i do know no one else hit them, i was first on scene with the advanced FM group.

Again they were gone never to come back, which is the best part, but the score is a little bit of a let down.

Edited September 1, 2017 by merlin51

[OLDZEKE]

15 minutes ago, dm79 said:

That must be the same thing causing the fire and engine bug, players on different hosts not picking up the stop command?

No the firebug/engine bug is not a cell host thing. That is being looked at, has been for awhile but both those are not being easy to replicate or nail down.

[dm79]

4 minutes ago, OldZeke said:

No the firebug/engine bug is not a cell host thing. That is being looked at, has been for awhile but both those are not being easy to replicate or nail down.

its got much worse since the cell change tho.

[OLDZEKE]

Just now, dm79 said:

its got much worse since the cell change tho.

Yea but being it's present when a server is only running one cell host means it's not multi cell host caused or dependent but rather that multi cell hosts may amplify the cause.

 

[dm79]

2 minutes ago, OldZeke said:

Yea but being it's present when a server is only running one cell host means it's not multi cell host caused or dependent but rather that multi cell hosts may amplify the cause.

 

My thinking as well.

[VICTARUS]

37 minutes ago, dm79 said:

That must be the same thing causing the fire and engine bug, players on different hosts not picking up the stop command?

Unrelated, unfortunately: The message is going between the cell hosts, and the damage is being forwarded correctly afterward. It's just the stats part that's being lost due to... reasons. (Still in the process of tracking that down.)

[Merlin51]

Firebug engine bug, start stop state bugs I can replicate easy. They definitely not a cell host issue

 

[OLDZEKE]

Keep a eye out for oddities, but this seems fixed.