Only the dismounted Konnik should count as a kill

Bulgarian civ always has a very skewed and inaccurate death count, as the Konnik and dismounted Konnik each count for a kill instead of one kill. This does not reflect on the actual game performance

This is also similar to malay karambit warrior which counts as 1 death where in fact it consumes only 0.5 population

This should be fixed by making the death counter only count the dismounted Konniks

6 Likes

i mean bro… of all the things that need to corrected… im not sure this even counts as one, and even if it did, this is literally at the bottom of the list… soz

5 Likes

Yes you are right, but it is an easy fix.

2 Likes

The game counts the number of units killed, not the amount of population killed. I would say the death count is right, because two units are killed if both the mounted and dismounted Konnik are killed (they are technically different units). Using the same logic, you would need to take care of other corner cases. Do you exclude converted units? Do you exclude free Kipchaks?

Don’t measure game performance by the death count, it’s only one statistic.

3 Likes

This doesn’t make much sense to fix, since units in AoE 2 have vastly different cost anyways. Is it fair that 20 FU Celt siege onagers give you the same number of kills as 20 Goth halbs? If yes, then konnik and karambit should remain the same in terms of kill count. If not, then we would need to rework this stat from scratch.

2 Likes

If you want to get technical about it, the dismounted konnik is just a continuation of the unit in an infantry form. It is a special case.

No other unit in the game spawns more units after its death.

Given an example, lets say 60 Spanish Paladins are against 60 Elite Konniks. Assuming both annihilate each other. Spanish would have 120 kills vs Bulgarian 60 kill. How is that an accurate description of the battle ?

Bulgarian player created 60 unique unites and lost 120 in the process. This does not happen with any other unit in the game

2 Likes

That is exactly why it counts as a death. The unit dies, even if it incarnates as something else.

1 Like

Yes you are right, but it is an easy fix.

How do you know that it is an easy fix? It could indeed be as simple as changing a single number somewhere in the data, or the method the game uses to calculate units killed is so hardcoded that it might require restructuring that part of the gamecode.

Even if it is the former, I don’t want the devs to spend five minutes to track down that number. Let’s just call it a quirk of Konnik, that it creates skewed achievements page. It’s not like the case earlier when it gave twice the score as well, and therefore could have had an actual impact on games with time/score victory condition.

1 Like

1111 Mate, game itself is already measuring death count, your score!

edit: even if its still sounds weird to me seems like dismounted konniks death doesnt affect score 11

No, the score is not affected by killing the dismounted Konnik, because it has no cost. Death count is not a part of the score calculation.

3 Likes

Well if you fight 60 Paladins vs 120 Halberdiers, and they both annihilate each other you have the same. You can frequently see this in 2v2s where the Cavalry player almost always will have a superior K/D over the Archer player.
Units have vastly different cost, a resources lost counter would be much more telling, K/D is meaningless.

2 Likes

That being said, I am of the opinion that a general reworking of the post game statistics should have been part of the definitive edition on release, and together with improved menus (the lack of profiles, or viewing menus while in queue is proof for DE just screams early 2000s )is an important step to elevate DE to a modern game and would not have been that much effort either. Capture Age proofs that most of the desired information is there, it is just not displayed.

Sorry, but before they change that, there are like 500 other changes to the statistics to make it more meaningful. Eg change most numbers to “ressources invested in” and making the timeline readable.

1 Like

Yeah hovering over the timeline should display either the worth, or number of military at that particular point, and the number of villagers/fishing ships.

You have no clue how badly the Scenario Community needs this. In every CBA Bulgarians units give Kills twice, meaning that its bad to play Bulgarian. Also this unit only vanishes when it dies twice, therefore only the dismounted konnik kill should count as kill.
In League of Legends getting killed before being revived by Guardian Angel also don’t give you a kill

2 Likes