What's going on here?

I finished a match with 18 kills and 1 death. K/D reported as 18.0 as it should. Later, I finished with 18 kills and ZERO deaths. This should produce a nonsensical ratio given the division by zero, but it also displayed as 18.0.

What's going on here? How can the same number of kills but one more death result in the same K/D ratio?

I thought it would divide by 2 if you died once. You know, kills per life, averaged. Guess not...

Most FPS games I've played seem to do this.

I thought it would divide by 2 if you died once. You know, kills per life, averaged. Guess not...

Nope. You can confirm given it gives you 1.0 if you have equal kills and deaths.

What's going on here?

// I hate dealing with edge cases

if(player.deaths==0)
{
   player.kd = player.kills; // Cody Miller will probably complain, but whatever
}
else
{
   player.kd = player.kills / player.deaths;
}

I thought it would divide by 2 if you died once. You know, kills per life, averaged. Guess not...

People would refer to kills per life as the K/L ratio, not K/D.

ZERO deaths

Every man dies.

Not every man really lives to get 18 kills.

// Cody Miller will probably complain, but whatever

Nah. They just put that right at the top of the very first file.

I was about to post this exact thing but you beat me to it : )
Good on ya.

- No text -

What's going on here?

I finished a match with 18 kills and 1 death. K/D reported as 18.0 as it should. Later, I finished with 18 kills and ZERO deaths. This should produce a nonsensical ratio given the division by zero, but it also displayed as 18.0.

What's going on here? How can the same number of kills but one more death result in the same K/D ratio?

Here's how this went down.

"Tester: Hey I went 18-0 and the game crashed with a divide by zero exception!"
"Programmer: fixed: if (deaths == 0) deaths++"
"Designer: I'm cool with it."

- No text -

- No text -