Kicked for TK'ing with chemical mortar?

[ZombieRommel]

So I called in a chemical strike in the attack/defense mode on the enemy point. ON THE ENEMY POINT. I put on my gas mask and proceed to move under the cover of the barrage. A couple seconds later several teammates are hit and I am auto-kicked from the server.

Wtf?

Is it my fault for calling in a mortar barrage on an enemy point and them walking into it?

I've lost the will to even play the game anymore if I'm going to get kicked for trying to play the objective.

[Epic Fail Spy]

it's more funny that people still run into poison gas without gas masks

[SSIXS]

Your fault they walked into it? No

But the tk kick system doesn't account for the stupidity of others, just like someone walking right into your firing line and getting tk'd.

[Empress Kaligosa]

I know how you feel, its happened to me a couple of times, do people not understand that the piss yellow smoke is not nice and that you should put a gas mask on or just not walk into it(or run away if the idiot is your commander and calls it on you.)

[ZombieRommel]

Originally posted by Darth Caligo:

I know how you feel, its happened to me a couple of times, do people not understand that the piss yellow smoke is not nice and that you should put a gas mask on or just not walk into it(or run away if the idiot is your commander and calls it on you.)

Exactly. The developers NEED to account for some degree of player stupidity. The commander shouldn't be kicked for this. It basically means that if your team are idiots, you're better off not being the commander at all. It discourages anyone from risking playing the role.

Originally posted by SSIXS:

Your fault they walked into it? No

But the tk kick system doesn't account for the stupidity of others, just like someone walking right into your firing line and getting tk'd.

That's different though. If they run into my line of fire, it's unlikely I'll kill more than one unless I'm not paying attention. The commander abilities give a big visual and audio warning and don't instantly spawn. So people have plenty of time to either go in before the barrage or wait til it's over.

The way it works now, the developers are directly punishing one player (kicking him from the entire server) because of the stupidity of the team.

[Sir Humphrey Appleby]

It is pretty rough when you get saddled with a couple mouthbreathers.

[SSIXS]

Originally posted by Dissonance:

It is pretty rough when you get saddled with a couple mouthbreathers.

Unfortunately, that's always been the case in fps games that are (supposed to be) teamwork and communication oriented.

One of the reasons I detest matchmaking systems, and am looking forwawrd to NWI finally implementing community servers and the browser. At least then we can pw or kick/ban them.

[ZombieRommel]

Originally posted by SSIXS:

Originally posted by Dissonance:

It is pretty rough when you get saddled with a couple mouthbreathers.

Unfortunately, that's always been the case in fps games that are (supposed to be) teamwork and communication oriented.

One of the reasons I detest matchmaking systems, and am looking forwawrd to NWI finally implementing community servers and the browser. At least then we can pw or kick/ban them.

The way the devs have it set up now ruins pub games, dude. I don't think you can excuse them for this. You can't expect perfect coordination in pubs. The devs are punishing commanders for simply calling in strikes. The commander has ZERO CONTROL over whether or not people run into the strikes like mindless idiots.

[SSIXS]

Originally posted by ZombieRommel:

Originally posted by SSIXS:

Unfortunately, that's always been the case in fps games that are (supposed to be) teamwork and communication oriented.

One of the reasons I detest matchmaking systems, and am looking forwawrd to NWI finally implementing community servers and the browser. At least then we can pw or kick/ban them.

The way the devs have it set up now ruins pub games, dude. I don't think you can excuse them for this. You can't expect perfect coordination in pubs. The devs are punishing commanders for simply calling in strikes. The commander has ZERO CONTROL over whether or not people run into the strikes like mindless idiots.

I'm not excusing anything, just stating the way it's always been in (supposed) teamwork oriented fps games... pubs are typically trash as far as communication and coordination goes.

Now instead of just complaining about it, why don't you suggest some specific ways NWI can actually improve the mechanics to be more to your liking. Or at the very least, point to another fps that can provide examples of a better system.

[ZombieRommel]

One of two things needs to happen.

1. The commander abilities need to have friendly fire turned off. Look at how Battlefield 5 does it. When you call in a V1 you don't blow up your whole team. Some of the Insurgency abilities already work like this (example, the chopper - it doesn't indiscriminately target your team). This would be the ideal solution even though it breaks some degree of realism. Make the Insurgents still cough in the smoke if they don't wear gasmasks.

2. Auto-ban/kick needs to be disabled for TKs that result from commander abilities. If the devs wanna keep the realism high, fine, but if players are allowed to call in *INDESCRIMINATELY DEADLY* abilities, THEN the game cannot also auto-kick the player.

It has to be one or the other. Disable FF for the abilities or disable the auto-kick.

[a cheeky yena]

Most folks don't seem to know about the chemical mortars. I'm assuming it's because they're rarely used. Try telling your teammates how to put on their masks as you call in the strike, that usually works for me.

[Mister Maf]

I find a moderately helpful workaround for this is to give a **MASKS ON** alert in team chat when chemical mortars are ordered. Hopefully the tutorial in the full game will teach players about gask masks, but what I'd really rather see is an audio cue on the radio informing the team to put on their masks.

[BlackMilk]

As with everything that you do that can very easily harm your teammates, it's common sense and best practice to let your team know what you're about to do.

Dropping lethal gas on an objective is almost the same as using an explosive to blow up a cache. If you don't give your teammates a heads up, you're likely going to injure or kill them.

Unless I am certain that noone of my team is near a weapons cache, I tell them that I'm tossing on a remote explosive, about to fire an RPG at it or that I'm done planting a charge. Then I give them three seconds (countdown over mic) before I pull the trigger.
Nine out of ten times this gets me a great result with people taking cover. That one other time is when people are stupid - they're oblivious or they are trying to compete with me to get the objective points.

It's the same with gas. You can never assume that strangers are going to be well aware of what's going on, even if they hear your character yelling out commands to HQ and messages appearing in chat about it. Just tell them that you're ordering gas and/or that they should put on masks. Preferably at least the latter. This is going to severely cut down on the amount of people being accidentally teamkilled by you. Won't prevent all of them, but some.

Don't think they have to change the mechanic. Avoid using it if you're certain that you're paired up with a bunch of deaf, blind and dumb players. The punishment should stay in for the inevitable trolling commanders.

[Tactical Testicles]

https://www.youtube.com/watch?v=K9uXLzZyucI