There has been some bugs with the player kill streaks, spar wins streaks and buddy kill streaks. I believe those bugs existed since they added streaks into our profiles.
Obviously, the track of player kill and buddy kill streaks started when they got added as a stat in our profiles. However, the spar streaks were saved before that.
Bugs with spar streaks: For some reason a lot of sparers had a false streak in their profile, their highest streak was actually higher than the streak that is shown on their profiles. I was told by some people if your a sparer broke your streak with a tie, it won't be saved in the database? Not sure if that was the issue and wither it was fixed or not. Anyways, yesterday a friend of mine won 47 spar wins in a row then lost to another player.


Since he lost connection to grail when he was streaking this basically means the win counted to his opponent and it wasn't a tie. I know when the spar streak were added as stats a lot of them were incorrect. But apparently there are still bugs with spar streaks.
Player Kill streaks: There are two type of bugs currently with kill streaks, the first bug is the same as the spar streak bug that I explained above. I experienced it myself and so did other friends of mine. My kill streak is stuck at 6 for whatever reason.
The second bug is having a high incorrect kill streaks when they're supposed to have lower. Few of my friends including the player in the screenshots below has a streak they're not supposed to have. This friend of mine told me he has no clue how he got that streak, he said he wasn't trying to gain a high player kill streak like other players do. He was pking normally without healing when he has low hp low, he said he even died a lot too while they were pking and he definitely didn't get 138 kills in-one-go. There are other examples exactly like this one too.


I don't know anything about buddy kills streaks but It's safe to assume the same bugs with player kill streaks exist with the buddy kills streaks.

In addition to suggesting to get those bugs fixed I would also like to suggest this:
Players should not be able to get a couple of kills, go to a safe zone to heal then come back to get a couple of kills again and repeat. Usually in action games, a player gain a streak when he/she kill (or whatever it is) a specific number of players in a short amount of time without dying. How can you count a 1000 player kills a "streak" that took that player probably more than 12 hours, using the method I described above when players heal in a safe zone before dying. There is more than one player who actually has +1k kills streak. Both kill streaks and buddy kills should be broken after a specific amount of time of not killing anyone. This specific amount of time defiantly should be less than 180 seconds.
If that does happen some players might find it unfair because they can't get those high kill streaks that other players has. That's why I also suggest to reset all the player kills streaks and buddy kill streaks after the bugs are fixed and my other suggestion is implemented. I know few players are going to complain (Wouldn't be many because there are very few players who has a high kill streak) because they lost their very high streak, but trust me more players are going to complain in the future because of the way kill streaks work right now. So a fresh start is needed.


I would also like to address this bug with player kills milestones: My 50k player kill milestone didn't show in my profile even thought I got my 50k kill two weeks ago. I never actually saw someone with a player kill milestone who has above 40k. I'm not sure if the same applies to spar wins milestones. Can we also fix that please?  

I really like the timer idea even though I was fantasizing on going on a year long pk streak if the logging off resetting it ever changed.  

idk if trying to heal before 0.5 in baddy kills makes u lose streak since I've been doing that for the past few days but my baddy streaks still stayed in 43 when I've killed more than that but I just tried to heal myself before 0.5 ;(  

I think a reset for Player killing streaks would be the best. I don't really know about baddy kills. And yeah the kill milestones are badly broken but I have seen people with a 180k+ milestone.
Also I think you should be able to choose if you'd like to display them or not.  

Is that spelling of baddy supposed to be funny?  

42 is the meaning of life, the universe, and everything.  

Posted by Ark

Is that spelling of baddy supposed to be funny?

No, I actually thought it's "buddy kills".

Posted by Agonee

Also I think you should be able to choose if you'd like to display them or not.

I agree with this too @ the milestones. Also in my opinion milestones should be displayed for every 10k pks rather than for every 1k. But the first 10k player kills can be separated into 10 milestones till the player reaches 10k player kills. Either every 5k or every 10k should be displayed as a milestone because 99% of the pkers don't care who is their 22k,117k (just examples)  

Green hair streaks.  

Also I want to make a suggestion for the season sparring streak record. If the player who owns that streak breaks it again, it doesn't announce that the streak was broken. In addition to not adding firework in the spar room.
This is what I suggest:
After the sparrer breaks the sparring streak record for the first time (the season sparring streak that is recorded in the BA library), his name should be announced in addition to adding firework (this already happens) this should happen only once till his streak ends. Then, if that same player broke the highest season sparring streak record that is owned by him, his name should be announced and firework should be played in the room. Just like when any other player breaks that season sparring streak record.  

After I beat my friend for my 12k win milestone, rather than having her name next to my 12k win the number 0 appeared. When you click on the number 0 a random player appears. She lagged out when we were sparring maybe that's why?

Player kill milestone still don't work.