If anyone believes the ‘misclick’, or the ‘oops’, have I got a bridge to sell you…
1 Like
Another possible solution to what you describe, that could also benefit many other parts of the game, would be to have a timer at that start of each match. No weapons can fire for “X” amount of time from the start. The mechanic is already in game, as used in the old “Duel” events. Say :20 - :30 secs, depending on the mode and vehicle type would prolly work wonders. No more blatant or accidental TK’s at the beginning of Air RB matches, no more annoying players peppering everyone in sight in tank/air spawns. They could even increase the TK penalties after implementing such a timer, as after the timer runs out, anyone still participating in “friendly fire” activities is doing it to be disruptive and annoy other players who are trying to legitimately play the game as intended. While I’m not sure they can ever completely remove TK’ing, at least these measures, which should be pretty easy to implement, would seem to lessen a great deal of the “opportunity” for this type of bad behavior. Just a thought . . .
‘Stopping’ them doing it by this forcing them not to fire, doesn’t address anything and merely makes it not happen at the start.
It’s not fixing the dumbass player who can’t control their trigger, and is obviously needing to sort themselves out before playing with others.
It’s like Ground RB with no tanks able to hurt each other, yet the idiot can come in flying with a bomb to drop on their teammate, or artillery thier teammate. You can’t stop both of those otherwise people would be impervious to damage whilst being in combat, and you’d be able to have everyone dogpile into a heap to scrap, and have a bomber just drop in the middle of everyone and end up with them just killing the enemy.
Thing is if you do the 20-30 seconds, then it goes further out, are you going to keep making more and more timer, or just outright block the damage, compared to actually fixing the player?
It does amaze me when a teammate shoves someone out of cover, and that player getting killed now being in full view. Not sure what the purpose of that is other than the one being that way just too young to play a game that relies on teammates. It does get aggravating, especially when you have a booster in play - moreso when in AB. I’ve been the victim of this more often that I care to mention and have reported the violator. Not sure what happened to them, other than a GM looking into how many times that player’s been reported?
2 Likes
…thinks that he can shoot at friendlies (in this case at me), spent all hi ammo, needs then to land and rearm and we lose subsequently on tickets - just because he did not fight the enemy and prevented me from supporting other team members as i had to evade his attack and to extend to gain separation.
Example of failed team killing attempt leading to defeat:
-
I flew my first match (replay) in a full stock I-185 (M-71) on Frontline Korsun. I tried to sideclimb and looped back to our airfield as i saw an enemy B-17 flying towards my airfield . The B-17 flew direct into my guns - instant kill.at 3:54.
-
The B-17 was chased by a friendly T-18B, but he never scored a hit on the B-17, so no damage, nothing. This “friendly” tried the in the next 80 seconds to team kill me. As i always check my surroundings i saw his attack coming just due to watching his flight path (4:10) fired all his ammo on me and broke off at ~ 5:30.
-
Actually i was unsure what to do.
-
Following him and kill him when he landed to rearm was one option (just in order to prevent new attacks), the other to extend and hoping that this guy could be useful for my team later in the game the other option.
-
Additionally there was a risk if he did not land on his airfield - the T-18B is actually faster vs a stock I-185 and completely outturns me. And chasing him at low alt makes no sense due to the insane range of his gunner (>2 km).
-
And ofc - i made the wrong decision - i did not team kill him, extended too far and my team managed to lose by tickets vs just 2 opponents left.
It is not solely the team kill it self (supported by the lack of fear to team kill as a result of the absence of severe punishments) what is so annoying - team kills have often also indirect impacts - either due to the numbers game (locally on the map and in general) or by preventing decisive actions of the team killed player suited to win a match.
1 Like
Just in order to be complete - a link to a imho interesting thread regarding harder punishments:
And another thread dealing with team killing of nuke planes in Ground RB:
https://forum.warthunder.com/t/punishment-isnt-harsh-enough-it-seems/91423
4 Likes
I do agree, it’s funny when you see an opposing player bomb a cluster of players and it seems only the enemy team get killed, not their own teammates sitting right next to the victims. I’ve seen that a few times also.
1 Like
My biggest frustration when being team killed in ARB is that I still get charged for the repair of my vehicle! Can that be fixed?
1 Like
The are no repair costs if you get team killed in Air RB, they stopped this some time ago.
1 Like
Thanks, it’s been a few months since I was team killed. Good to know!
1 Like
Whilst it is a bit of a chortle if it were actually accidental, when it’s intentional, someone just screwed over the match and that team, for the sake of it.
I appreciate my opponents, unlike many of those who get upset at dying to things, and others, or losing ‘because the team was bad’ kind of thing.
Can we please introduce the possibility to appeal team kills by arty strikes. It pisses me off to be penalised for the carelessness of others …
1 Like
GAIJIN !!!
I am so tired that you do zero against this team killer SCUM polluting Air RB.
I just came out of a match in which an absolute disgusting piece of sh*t killed 3!!! of my team right at take-off.
Just watch this replay and go into the player view of the B-17 which decided to use an airfield take-off and killed an F4U, a J26 and a P-47 within seconds.
Such guys need an immediate perma ban and not a temp ban via your auto-ban system.
STOP this NONSENSE!!!
Rant out
1 Like
wow he pushed me out from the map what a ass le max_trebog, a complety lowskiller his states 14.000 deaths with tiger 14.000 kills
https://warthunder.com/en/tournament/replay/192200739982576451
I tried pointing that out, and others did too. When I have to chase up a GM to actually show them the seriousness of the situation where a SQUADRON squad takes out an ENTIRE team, and still have to show that they did it to multiple matches to get any action, is that the true ‘system’ isn’t working in any way.
After all, they shouldn’t even be able to kill more than 2 in a quick succession without being stopped or flagged to be checked…
But it doesn’t.
If moderation was to be done effectively though, and with communication, then maybe… But not automatically, or by ‘stopping the effects’ by making FF off as they have done in the past…
I honestly think the removal of FF has actually caused more trouble than it has fixing it in the modes it’s had it removed from.
1 Like
Another team killing and trolling thread:
When playing PvE Helicopters a troll kept ramming into me for 3 times - until I left - and went unpunished every time. Means I had to pay all the repair bills on top of the joy of being bullied out of a match.
Which leaves the question why ramming doesnt result in a teamkill here. He had a very fast and manoeverable helicopter (while I had the opposit) and just kept flying over me to touch down with his gear onto my rotor blades. That meant I would crash every time while he remained undamaged.
With that, take that directly to Game Masters… Whilst you can report it via the ingame reports (Right click, complain feature), that sort of antics needs to be directly raised as actual griefing.
Take the replay link from the server replays section with the timestamp to make it ultimately easy to identify. (You could report it through the server replay report function, but I’d absolutely escalate it directly)
2 Likes
Imho the player who teamkilled you 3 times (i can’t believe that - what a pathetic move) uses a flaw in the friendly fire damage detection.
The old forum thread is full with examples like that - same with the bug report section. Guys deliberately rammed teammates - and if the “rammer” crashed during this attempt, the ramming “victim” was on top blamed as team killer…
Imho the fellow player above gave you the correct advice - the GMs are usually not allowed to interfere with the auto-ban system for “tracked” teamkills - but in this case we can assume exploiting faulty game mechanics and griefing; GMs like @Schindibee are happy to process such reports…
Thanks for the advice guys. I have taken this issue to Schindibee in hope that he can have a look into it to make the gaming experience better for everyone.
Not only does griefing deserve a zero-tolerance policy as it adds to an overall toxic atmosphere but I think the whole mechanic of being able to deliberately ram into teammates without at least having to pay for the repair costs needs to be looked at.
2 Likes