We all know the problem, and we are all sick of it.
people keep sabotaging killevents in 1 or more of the following actions:
1.) they kill subaccounts.
2.) friendly fire (1 alliancemate leaves the alliance so others from the alliance can make kills on him/her).
3.) spamming cords on global chat (can't call it sabotaging.. but it is sooo irritating and cowardly)
4.) ''agreementkills'' (During killevents, they search a ''killbuddy'' and every TK event, they kill on eachother.
since long and big events, like season 5 only have : Train a thon, Tournament of might, TK events, and alliance might and TK events... i honestly believe that's it's critical to find a solution for this matter, since 40% of all the events are TK events (if you look to season 5). That means, people can sabotage massively. Tournament of might is easy.. you simple login and click some might. Train a thon is easy aswell if you have a alliance bank. But for TK events... you normally have to spend time to search for kills.. and it's not Guaranteed that you will find some.. atleast.. not much every time you look.
Honestly i have no clue what kabam could do against this. But what i do know is, that it's messing* the game up.
Short term ''solutions'':
1.) "7 days Leaving ban" --> when leaving an alliance, you can't join any alliance within the next 7 days. And after leaving, you can not attack your old alliance for 7 days.
2.) "Killevent ban" --> From the moment a TK event is announced with a timer, or from the moment it started, nobody can leave their alliance till a killevent has ended.
3.) ''attack the same player restriction'' When you have attacked a player ones or multiple times on day1, you can't attack that player anymore for the upcomming 6 days.
The Absolute best long term solution for this problem (it needs a lot of programming):
4.) To be able to see on the ranking of the TK event by clicking on a players name, on what players they made kills, and how many kills per player. But only after a TK event has ended, to prevent other people from jumping in to also attack that player.
Example:
*TK event has ended
* "Player 1'' has ended on rank 2 in the TK event with 456m kills.
* Clicking on ''player 1''
* 126m kills on Player 33 from alliance X
* 280m kills on player 66 from alliance Y
* 50m kills on player 99 from alliance Z
*That way nobody can interfere while the TK is still running, because it will only be visable after a TK has ended.
*That way everybody can check after a TK has ended which person made kills on what person and how many.
*This will result in that everybody can check ''strange kills'', build cases, and provide kabam with proof so kabam can take measures against those cheaters.
I'm very interested in what idea's other players have about this case. And especially what kabam thinks of it. It's a wellknown problem so i was wondering if there was already a ''creation'' running in your machines;-)
people keep sabotaging killevents in 1 or more of the following actions:
1.) they kill subaccounts.
2.) friendly fire (1 alliancemate leaves the alliance so others from the alliance can make kills on him/her).
3.) spamming cords on global chat (can't call it sabotaging.. but it is sooo irritating and cowardly)
4.) ''agreementkills'' (During killevents, they search a ''killbuddy'' and every TK event, they kill on eachother.
since long and big events, like season 5 only have : Train a thon, Tournament of might, TK events, and alliance might and TK events... i honestly believe that's it's critical to find a solution for this matter, since 40% of all the events are TK events (if you look to season 5). That means, people can sabotage massively. Tournament of might is easy.. you simple login and click some might. Train a thon is easy aswell if you have a alliance bank. But for TK events... you normally have to spend time to search for kills.. and it's not Guaranteed that you will find some.. atleast.. not much every time you look.
Honestly i have no clue what kabam could do against this. But what i do know is, that it's messing* the game up.
Short term ''solutions'':
1.) "7 days Leaving ban" --> when leaving an alliance, you can't join any alliance within the next 7 days. And after leaving, you can not attack your old alliance for 7 days.
2.) "Killevent ban" --> From the moment a TK event is announced with a timer, or from the moment it started, nobody can leave their alliance till a killevent has ended.
3.) ''attack the same player restriction'' When you have attacked a player ones or multiple times on day1, you can't attack that player anymore for the upcomming 6 days.
The Absolute best long term solution for this problem (it needs a lot of programming):
4.) To be able to see on the ranking of the TK event by clicking on a players name, on what players they made kills, and how many kills per player. But only after a TK event has ended, to prevent other people from jumping in to also attack that player.
Example:
*TK event has ended
* "Player 1'' has ended on rank 2 in the TK event with 456m kills.
* Clicking on ''player 1''
* 126m kills on Player 33 from alliance X
* 280m kills on player 66 from alliance Y
* 50m kills on player 99 from alliance Z
*That way nobody can interfere while the TK is still running, because it will only be visable after a TK has ended.
*That way everybody can check after a TK has ended which person made kills on what person and how many.
*This will result in that everybody can check ''strange kills'', build cases, and provide kabam with proof so kabam can take measures against those cheaters.
I'm very interested in what idea's other players have about this case. And especially what kabam thinks of it. It's a wellknown problem so i was wondering if there was already a ''creation'' running in your machines;-)
Comment