Because I expect from devs and Gajin to fix this and give us all bug free radar missles… Do I expect too much?
So launch range 100km means nothing and Lock range of 40KM also means nothing?
I get this but when I have 2 hours and 420k reserch points to go I really could not care less…
I think that bug should be fixed, Im not saying it should be used to TK someone…
Not saying you’re wrong, but…I’ll make an assumption here.
Your target audience for the game is rather young, has no military experience and wants a fast, action packed experience.
Gaijin wants to provide a conflict oriented, fast paced action that caters to the (predominantly) younger audience, who is willing to spend disposable income to gain progress in the game or access modules/weapons/features that are locked behind a grind wall.
So if the audience wants action and Gaijin delivers action, then the expectation of people exercising trigger discipline is nothing but wishful thinking.
I’m sure Gaijin has recognised this already, but I fail to understand why a friendly fire mechanic in Air RB is active and in Ground RB it is disabled.
Anyways, I’m not against punishing Teamkillers, but I’m against regarding an accidental Teamkill the same way as a Teamkill made on purpose. Especially, when the mechanics to prevent that exist in the game.
Then instead of 16v16 make its 3v3 with current map size, greatly expand team communication options (i.e. mandatory voice chat), give everyone a free HOTAS and silly costume, then we can pretend we are in the air force. Otherwise that’s not happening
After watching YouTube gameplay of top tier I am honestly terrified to play it. Your description of the gameplay is a very rose tinted glasses version of it.
It’s absolutely not in the player’s hands for a SARH or ARH missile to IGNORE a prior AND/OR current locked aircraft and just go where else it wants to go.
That is not how it functions in real life and that’s not how it should function in the game. The burden is on Gaijin to correct flagrantly obvious egregious bugs such as incorrect missile behavior. That is their duty as developers of the game.
I never said that it would be. I said it’s in the players hand to fire or not fire in such a situation.
I fully agree, and I do hope that this (along with other things) get fixed.
But that still does not change my personal opinion that even if it’s buggy or not optimally implemented, knowing this and still taking the shot makes me responsible for the TK. And such TK’s can be prevented by the player.
If the players fire on the basis of “but it should not be like tis”, they still accept the potential risk that the will commit a TK, and this (as this discussion here shows), even if they’re fully aware of the risk, be that risk based on correct or wrong implementation of real life aspects, or indeed based on faulty mechanics or bugs is quite irrelevant, I find…
So it’s the player’s fault that Gaijin can’t code the game to function properly? So because Gaijin can’t code the game properly I and everyone else have to absolutely play passively in nearly every situation?
Your logic and argument stance in all this is so fundamentally flawed it’s genuinely irritating.
This is kind of the spewed nonsense that makes people doubt whether mods, admins and even Gaijin themselves actually play the game or not.
When you stub your toe on your bedside drawer, you move it. Gaijin says cut off that toe because it’s in the way.
It’s so asinine because I’ve lost count of how many times I fired sparrows at hard locked enemy aircraft in open sky with no friendlies in the zone anywhere and the Sparrow has still done one of two things; Pissed off in a random direction to explode or tracked down an allied aircraft that wasn’t even on the screen and killed them.
But according to these guys, that stuff is still our fault when it happens.
Rrrrriiiigggggghhhhhhtttttttt.
Tell the players to just not play in the BR range with SARH/ARH missiles without telling them to just not play in the BR range with SARH/ARH missiles.
Or Gajin can put this as priority same as they put TK disabled yesterday and FIX IT ASAP?
The likelihood of the missle going dumb like that is pretty low, and even if you are thinking about these points, now matter how good you are, you will not think about them 24/7 when playing.
If you try to prevent that, there is still a chance for that to happen. So you basically just handicap yourself without reducing the risk by a lot.
Also, since I also play top tier air arcade jets a lot, I have noticed that the missle tracking a friendly just does not happen in air arcade, nor have I ever seen this happening to anyone else I play with.
My guess is, that this „bug“ is actually a feature/game mechanic for air realistic. Or at least it’s caused by being able to Teamkill in realistic.
And if it’s a game mechanic implemented on purpose, it really is a shame that there is a chance to get banned for that
I mostly agree with you here minus the little tidbit about bugs. How is a player supposed to compensate for something that typically shows absolutely no signs of occurring until it actually occurs? I’ve seen it happen myself, Sparrows and even AMRAAMs at times will completely disregard the locked target for seemingly no reason.
I fully understand that Teamkilling is prohibited, and rightfully so, but I certainly hope incidents that are caused by bugs outside of player control are not being held against anyone.
Please give us option disable team kill or targeting team in fight or in bvr fast games mistakes happend i hate tk
Oh so you’re keeping track of my grammar mistakes? Congrats, you just earned a double kill on punctuation errors. Keep going, maybe you’ll unlock a tactical nuke of missed commas. GG grammar police lame ahh boi
Another example of the lack of deterrence regarding team kills and the still not solved ramming bug:
In this replay:
Gaijin Entertainment - Single Sign On
You will see at 09:43 play time a friendly F4U firing at me without any provocation - he started his attempt at 9:17. He managed to spray all of his remaining ammo on me - scoring a crit and a few hits. Finally he rammed me (a very slight contact, hard to see in the replay) and crashed on purpose - leading me to be blamed as team killer.
This has to stop - i am tired of low life tanker trash like in this example - his action resulted in getting me charged with 26.793 SL.
Those guys need an instant perma ban; i mean the fact that he tried to kill me by ramming (after he sprayed 619 shots of 0.50 cal ammo on me) is evidence enough that he was fully aware of this faulty game mechanic.
It makes zero sense to check permanent your six when the sole remaining enemy is 3 km in front of you - just pathetic.
Ofc i used chat to inform him about getting reported for griefing and a failed attempt for an intentional team kill - he responded “you t’killed me bro, enjoy the ban”.
This just about sums up the game, it is broken almost beyond fixing and needs tearing down and starting again.
Making the victim go through hoops just to get the correct outcome is reprehensible in the least, not sure if you did get banned because of the nebulous/secret figure that triggers the punishment, whilst the perpetrator gets to play days or months with no consequences to his rule breaking actions is once again a failure by the company.
I expect for you to get any outcome from this event involves hours of e-mailing, sending replays and awaiting replies for more information as the process is stalled, possibly hoping for you to give up and not bother, a standard practice for many complaint procedures in many companies. Make it as difficult, slow and time consuming as possible so nobody bothers.
Coupled to his people wonder why players do not care, play stupidly and often detrimentally to their teams success and one death leave, what is the point whilst this goes on and many other flaws and problems that are rife and endemic in the game.
I hope you did not get any sort of ban, as I expect this is something you never do and this was an anomaly perpetrated by a complete skeleton warrior.
I was never banned for team killing because i assess this as detrimental for the game. I do admit that i would have killed him if i would have been aware of his attempt way earlier, but my plane was literally scrap after his attack, so no way to retaliate.
I am very confident that i won’t face a temp ban as i reported this behaviour via the server replay site, the evidence speaks for itself.
Just a game in SB
Ban it all, maybe then they will learn.
THe safest thing to do if attacked by a team mate is crash into the ground. That way, they get the TK against them and you don’t risk the collision triggering a TK for you. (I know, this shouldn’t be necessary)
I apparently must have killed another flyer while dropping a bomb in GRB which is odd because you can’t kill a friendly tank in GRB. I don’t know why they have one physics for ground vehicles and another for planes. I dont know why they even have the friendly fire thing in GRB/ARB. It does nothing but cause upset in the game.It’s an unrealistic game and friendly fire does nothing to make it any more fun.
A new team kill related thread: