*NwA*’s 3rd Birthday Party

Dear Members

As you may have noticed it is *NwA*’s 3rd birthday on the 25th October. We the Management would like to say a very big thank you to all our members (past and present) for making us what we are today.

We will be running a birthday event on the 28th October, we will be looking to set up a event server and would like for you all to have your say so please do start posting ideas over the next few days. The servers will run for a full weekend Fri/Sat/Sun for full mayhem madness these servers will be unlocked and open to the public to join.

We will be promoting this event on the PR website also. We will be offering free reserved slots on all servers to ensure whatever battle you wish to play you will be guaranteed access in to all servers, sign up here or on the PR forums. As a masive thank you to all our loyal members the first 30 players to sign up, we would like to offer a free reserved slots for three weeks to any one who wishes to take place in this weekend (one week for every successful year of *NwA*).
Reserveslost list

1. -=ssu=-kerrermanis
   
2. Smurf_cfc
   
3. DudeNukem91
   
4. Tarranauha200
   
5. ULTralViolet.xxx
   
6. Stealthgato
   
7. Hellspawn_Hunt3r
   
8. [OD-S]FelixTugzilla
   
9. _Smurf_1st
   
10. [Xz0r]SwaggerNL
    
11. Mr.Arked
    
12. [PR]NATO|P*Funk
    

Time is curtail as we are only just over one week away from 28th Oct, we will be setting up the servers over the next day or two, we would welcome all suggestions for maps to be added to each server, every map requested will be added to the maplist, in what order we will decide once all maps have been added to the lists.

Any member wishing to help set this up or take part in the running this event please post stating so.


All feedback and help however little or small will be welcome over the next 3-4 days to ensure our members and public players have a great weekend.



Map lists below:

rem |-------------------------------------------------------------------------------|
rem | Conquest (AAS) - Assault and Secure. Default Project Reality Gamemode |
rem |-------------------------------------------------------------------------------|
mapList.append asad_khal gpm_cq 16
mapList.append asad_khal gpm_cq 32
mapList.append asad_khal gpm_cq 64
mapList.append battle_for_qinling gpm_cq 16
mapList.append battle_for_qinling gpm_cq 32
mapList.append battle_for_qinling gpm_cq 64
mapList.append beirut gpm_cq 16
mapList.append beirut gpm_cq 32
mapList.append beirut gpm_cq 64
mapList.append burning_sands gpm_cq 16
mapList.append burning_sands gpm_cq 32
mapList.append burning_sands gpm_cq 64
mapList.append dragon_fly gpm_cq 16
mapList.append dragon_fly gpm_cq 64
mapList.append fools_road gpm_cq 16
mapList.append fools_road gpm_cq 64
mapList.append iron_eagle gpm_cq 16
mapList.append iron_eagle gpm_cq 32
mapList.append iron_eagle gpm_cq 64
mapList.append iron_ridge gpm_cq 16
mapList.append iron_ridge gpm_cq 64
mapList.append jabal gpm_cq 16
mapList.append jabal gpm_cq 64
mapList.append kashan_desert gpm_cq 16
mapList.append kashan_desert gpm_cq 32
mapList.append kashan_desert gpm_cq 64
mapList.append korengal gpm_cq 64
mapList.append kozelsk gpm_cq 16
mapList.append kozelsk gpm_cq 32
mapList.append kozelsk gpm_cq 64
mapList.append muttrah_city_2 gpm_cq 16
mapList.append muttrah_city_2 gpm_cq 64
mapList.append op_barracuda gpm_cq 16
mapList.append op_barracuda gpm_cq 64
mapList.append qwai1 gpm_cq 16
mapList.append qwai1 gpm_cq 32
mapList.append qwai1 gpm_cq 64
mapList.append siege_at_ochamchira gpm_cq 16
mapList.append siege_at_ochamchira gpm_cq 32
mapList.append silent_eagle gpm_cq 16
mapList.append silent_eagle gpm_cq 64
mapList.append wanda_shan gpm_cq 16
mapList.append wanda_shan gpm_cq 32
mapList.append wanda_shan gpm_cq 64
mapList.append yamalia gpm_cq 16
mapList.append yamalia gpm_cq 32
mapList.append yamalia gpm_cq 64

rem |-------------------------------------------------------------------------------|
rem | Skirmish - Small infantry-only battles, aimed at 6v6 to 10v10 |
rem |-------------------------------------------------------------------------------|
mapList.append albasrah gpm_skirmish 16
mapList.append asad_khal gpm_skirmish 16
mapList.append battle_for_qinling gpm_skirmish 16
mapList.append beirut gpm_skirmish 16
mapList.append burning_sands gpm_skirmish 16
mapList.append dragon_fly gpm_skirmish 16
mapList.append fallujah_west gpm_skirmish 16
mapList.append fools_road gpm_skirmish 16
mapList.append gaza gpm_skirmish 16
mapList.append iron_eagle gpm_skirmish 16
mapList.append iron_ridge gpm_skirmish 16
mapList.append jabal gpm_skirmish 16
mapList.append karbala gpm_skirmish 16
mapList.append kashan_desert gpm_skirmish 16
mapList.append kokan gpm_skirmish 16
mapList.append korengal gpm_skirmish 16
mapList.append kozelsk gpm_skirmish 16
mapList.append lashkar_valley gpm_skirmish 16
mapList.append muttrah_city_2 gpm_skirmish 16
mapList.append operation_archer gpm_skirmish 16
mapList.append op_barracuda gpm_skirmish 16
mapList.append qwai1 gpm_skirmish 16
mapList.append ramiel gpm_skirmish 16
mapList.append siege_at_ochamchira gpm_skirmish 16
mapList.append silent_eagle gpm_skirmish 16
mapList.append wanda_shan gpm_skirmish 16
mapList.append yamalia gpm_skirmish 16

rem |-------------------------------------------------------------------------------|
rem | Insurgency - Objective based. Blufor is to destroy Opfor ammo caches |
rem |-------------------------------------------------------------------------------|
mapList.append albasrah gpm_insurgency 16
mapList.append albasrah gpm_insurgency 64
mapList.append fallujah_west gpm_insurgency 16
mapList.append fallujah_west gpm_insurgency 64
mapList.append gaza gpm_insurgency 16
mapList.append gaza gpm_insurgency 64
mapList.append iron_ridge gpm_insurgency 16
mapList.append iron_ridge gpm_insurgency 64
mapList.append karbala gpm_insurgency 16
mapList.append karbala gpm_insurgency 64
mapList.append kokan gpm_insurgency 16
mapList.append kokan gpm_insurgency 32
mapList.append kokan gpm_insurgency 64
mapList.append korengal gpm_insurgency 16
mapList.append korengal gpm_insurgency 64
mapList.append lashkar_valley gpm_insurgency 16
mapList.append lashkar_valley gpm_insurgency 64
mapList.append operation_archer gpm_insurgency 16
mapList.append operation_archer gpm_insurgency 64
mapList.append ramiel gpm_insurgency 16
mapList.append ramiel gpm_insurgency 64

rem |-------------------------------------------------------------------------------|
rem | Command and Control - Objective based. Build and defend Forward Outposts |
rem |-------------------------------------------------------------------------------|
mapList.append battle_for_qinling gpm_cnc 16
mapList.append battle_for_qinling gpm_cnc 64
mapList.append kashan_desert gpm_cnc 16
mapList.append kashan_desert gpm_cnc 32
mapList.append kashan_desert gpm_cnc 64
mapList.append silent_eagle gpm_cnc 16
mapList.append silent_eagle gpm_cnc 64
mapList.append yamalia gpm_cnc 16
mapList.append yamalia gpm_cnc 64

rem |-------------------------------------------------------------------------------|
rem | Vehicle Warfare - Large, vehicle only battles |
rem |-------------------------------------------------------------------------------|
mapList.append battle_for_qinling gpm_vehicles 64
mapList.append kashan_desert gpm_vehicles 64
mapList.append silent_eagle gpm_vehicles 64
mapList.append yamalia gpm_vehicles 64

rem |-------------------------------------------------------------------------------|
rem | Co-Operative - Humans vs Bots. !!!Cannot be run with any other game mode!!! |
rem |-------------------------------------------------------------------------------|
beginrem
mapList.append albasrah gpm_coop 16
mapList.append albasrah gpm_coop 64
mapList.append asad_khal gpm_coop 16
mapList.append battle_for_qinling gpm_coop 16
mapList.append beirut gpm_coop 64
mapList.append fools_road gpm_coop 64
mapList.append gaza gpm_coop 16
mapList.append gaza gpm_coop 64
mapList.append jabal gpm_coop 64
mapList.append karbala gpm_coop 64
mapList.append kashan_desert gpm_coop 64
mapList.append kozelsk gpm_coop 16
mapList.append lashkar_valley gpm_coop 16
mapList.append muttrah_city_2 gpm_coop 32
mapList.append muttrah_city_2 gpm_coop 64
mapList.append operation_archer gpm_coop 16
mapList.append operation_archer gpm_coop 64
mapList.append op_barracuda gpm_coop 64
mapList.append qwai1 gpm_coop 64
mapList.append ramiel gpm_coop 16
mapList.append ramiel gpm_coop 64
endrem

karkand infantry! lol

Qin Ling, i think thats the name. US and Chinese. Tow Hummer and Tank.

Ninja Kits for all on Qin ling! or just mumble only will do me!

British map fest! Or maybe some of the more awesome Insurgency maps. We should get a good turnout of proper players for this!

Also, as many clan members as possible, split us between both teams so we all get a really awesome game, and show the pubbers a good time too!

Make sure you've all got enough beers in the fridge!

CNC mode? Vehicle warfare? Jeep races on different maps? Pistol skirmish?

I'd like to see some of the maps that are never or rarely played (although maybe that's for a reason) stuff like Yamala and Iron Eagle (the one with russian and US inf altough I think it's with Germans now) or maybe the Winter maps from last year?

So are we thinking regular maps here, or scenarios?

Freeing a group of hostages from the clutches of the Taliban (20 Taliban vs 35ish US/UK troops with limited assets etc, with 5 hostages?)

I could probably come up with quite some scenario's if that's something people want. With some very specific rules (Dead=dead or somesuch)

Of course, mumble is a 100% requirement.. just for this weekend.

Woop! I'd like to sign up Don't have any suggestions, though I agree some of the less played maps might be fun!
And I wouldnt mind some of your scenario's Nixy!

Could be good to put up a scenario or two a day during the peak hours.
Shouldn't be more, got to be "fresh" and interesting. Very interested in what you can come up with Nixy.

3 weeks of reseved slots? Gotta get me some of this. do i sign up on PR forums or can it be done here?

As for maps...anything but not too laggy.

Burning Sands, Basra, Kashan(not jets) Fools Road. Quinling. would be nice to see them in there.

Congrats on ur 3rd annivesary

to this event.

I hope members do not need to sign up? =P Otherwise we will have very few slots left for pubbers ^_^

Got a spare hour now, so I'll go tinkering a bit with what would be fun/possible/unbalanced yet balanced

Sounds great! Count me in. Or do I have to sign up on the PR forums?

I like the idea, having a couple of rounds scenarios.

Like Xazper had some ideas, I am in for: vehicle warfare, pistol skirmish, or how about a massive boxing fight once?
But I am in for AAS and insurgency aswell.

Congratz with your three years of existence! Keep it up boyz.

Im in!

What about big maps? Kashan, op arhcer, silent eagle...etc
Or maybe just 24h kashan lol.

mapList.append qwai1 gpm_cq 64, thats the one i ment.

Maybe put up a poll for everyone to vote on the map they wanna play the most? Points the PR forums in this direction too

sign up done on this webby and the pr forum guys

Scenario 1 - Hostage rescue Kokan

*American/Canadian forces versus the Taliban.*


0600, Kokan, Afghanistan:
Men, as of 0600 hours we lost contact with one of our southern patrols. Aerial surveillance footage shows the patrol to be ambushed by a substantially larger force of Taliban warriors. Three of our men were killed in the ensuing firefight and another two were executed on the spot. The others were taken captive and transported to a compound close by the ambush site. It is believed the hostages are still alive, but they might not be for much longer. It is imperative that we get these men out of there before they are shot or taken away beyond our reach.

We will use this location as a forward base of operations. One of our birds is already in the air as we speak, keeping a close watch on the compound. Last we heard everything on the outside is quiet, but that might not stay that way. That is all. Report to your CO and gather at the designated area!


_________________________________________________________________

General rules for Hostage Rescue scenarios:

• All participants are required to be on mumble.
  
• All participants will be in a single mumble channel.
  
• The use of squad-VOIP is to be limited to a minimum.
  
• Squad leaders can talk to the commander using VOIP.
  
• BluFOR will start with more troops than the hostage takers.
  
• Dead = Dead !
  
• Taliban will be allowed to select the 'prison area' for the hostages without knowledge of the BluFOR.
  
• Limited assets for both sides.
  

Explanation for mumble/VOIP rules:
Mumble will be treated as the soldiers talking to each other. This is of course heard by the other team if close enough! Therefore both BluFOR and the Taliban are supposed to keep the VOIP usage to a minimum. VOIP is to be the radio the squad leader uses to communicate with the commander.


_________________________________________________________________

Locations:

I've selected 3 possible locations, each with their own pros/cons. Please tell us which one you'd prefer.

1: The compound close to the Taliban main.
-Pro: Very well defendable for the Taliban.
-Con: Close to the Taliban main. This means no full 360 degree attack vector for BluFOR.

2: The compound close to the BluFOR main.
-Pro: Very well defendable for the Taliban.
-Pro: Possible 360 degree attack vector for BluFOR.
-Con: May require exceptional coordination from BluFOR team.

3: The compound used in the Skirmish version of Kokan.
-Pro: More stretched out than the other compounds. This means more locations to hide the hostages.
-Pro: Possible 360 degree attack vector for BluFOR.
-Con: May be less defendable for the Taliban.


_________________________________________________________________

Rules of Engagement:

We’re here to rescue hostages, not to tear down the buildings. Heavy weaponry will therefore not be allowed!
This means:

BluFOR (general):
-Mortars will not be allowed, except for smoke rounds to cover the advance.
-HMMWV’s/G-wagons may use their mounted weapons to fire into windows to cover their approach. This is only true when there is a reasonable threat though.
-No TOW missiles from emplacements directed towards the structures. However if a high priority target outside a building shows itself they are free to engage. This means technicals or possible SPG emplacements.
-No use of C4.

-The hostages need to be rescued as efficiently as possible. Do not risk their lives! Do some research before you storm in.


American specific:
-Stryker will have to be careful not to wreck the building with its CROWS.
-Possible Kiowa’s will not be allowed to use their Hydra missiles or optional .50cal machineguns.
-Blackhawk is not allowed to fire upon the buildings. Courtyards and open spaces are free to be engaged.

Canadian specific:
-LAV3’s will not quickly be given the order to fire upon the compound, due to destruction with 25mm cannon.



Taliban:
-No Artillery IEDs. The Taliban might not care about the compound, but blowing up an entire section severely exposes them.
-Small IEDs may be used as a ‘plan B’ in the hostage room. They will also blow out walls in the compound, further exposing the Taliban, thus are not to be used in regular combat.
-The Taliban will not possess any anti-air weaponry. They are however free to use RPGs to fire at helicopters and enemy vehicles.
-Claymores and grenade traps are allowed to be used. As are anti-vehicle mines.
-One SPG9 emplacement may be used to fire outward from the compound.

-The hostages are not to be harmed!

The Taliban commander may execute one or more hostages as a threat. Keep in mind that the Taliban need their hostages for whatever purpose they had in mind.



_________________________________________________________________

Assets:

Canadian team:
-One or two LAV3s depending on preference. Keep in mind the rules of engagement.
-One or two Chinooks if preferred (limited usefulness).
-Max of 2 FOBs, each with 1 TOW emplacement and several foxholes.
-No HAT/LAT kits. Combat engineer may be used to remove anti-vehicle mines.
-As many G-wagons as preferred.

--30 to 40 units.
-One commander
-A max of 9 squads/squad leaders
-4 to 6 hostages


American team:
-One Stryker.
-One Blackhawk.
-One or two Kiowa Warriors. Only to be used for recon with FLIR.
-Max of 2 FOBs/Watch posts, each with 1 TOW emplacement and several foxholes.
-No HAT/LAT kits. Combat engineer may be used to remove anti-vehicle mines.
-As many HMMWVs as preferred.


-- 30 to 40 units.
-One commander
-A max of 9 squads/squad leaders
-4 to 6 hostages


Taliban team:
-One SPG-9 emplacement for defence.
-Two .50cal technicals.
-No anti-air weaponry.
-RPG’s are allowed to fire at helicopters and ground vehicles.


-- 15 to 20 units.
-One commander
-A max of 9 squads/squad leaders

_________________________________________________________________





This is the first draft of a possible scenario. Tell me what you think!

Wow, great story/scenario! Seems to be your a professional .

I suggest to use the compound you mentioned from the skirmish layout.

I got some questions though. Like:

1. Just to make sure, so there is no confusing about this. With dead you mean not reviveable anymore?
2. Is there any time/ticket limit for the BluFor?
3. Are the Taliban warriors allowed to use mortars?
4. BluFor Commander allowed to use UAV?
5. Combat Engineer allowed to lay down mines?
6. So if I understand it well, the Taliban is allowed to drive around with their techies anywhere on the map? How about the BluFor haves to
operate in a convoy?
7. HMG's allowed?
8. What if one of the hostages got killed? (Not quite sure about killing them. Because the Taliban ppl will might think "Hey let just kill them, then we win!" if there are no dedicated players on that side. If so, then it will be for the BluFor like: *1 hostage killed* "Ohh, well, who cares they won't kill them all". Can be quite lame for the volunteers being hostages aswell)
9. I think that it can be quite messy if there will be heavy usage of grenade traps.
10. I guess the chat in squad-/teamchat is also limited. Or how about not using chat at all?
11. Is the Taliban commander allowed to set up markers/waypoints? (Which will tell the commander by informants that there are 'infidels' seen. For anyone who didn't know about this)

JDAM is certainly NOT allowed I assume.
Keep in mind that everyone is able to throw a grapling hook in a small window, so ppl can go in any room with a window without using/breaching any door (if I am right, not really sure about this point). What makes it harder for BluFor for instance.

Not to be a d**k but for 0600 hours its a quite bright day @ Kokan.

How is this Operation going to be called? :

This is looking good. And I would love to be participating on this!

EDIT: Question nr. 12. So the sqd leaders and commander are not allowed to use the sl channel in Mumble?

that "Dead=dead" thing means you have to give up after being wounded?

It surprises me how many people still don't know the difference between being wounded and DEAD. There's a difference people.

If you get shot and you can still be stabbed with an epi pen by the medic, you are WOUNDED. Not dead. Adrenaline isn't going to bring you back to life, you know.

When your death counter reaches '1' or when you are 'dead-dead', that means you're out of the game.

Nixy23 wrote:It surprises me how many people still don't know the difference between being wounded and DEAD. There's a difference people.

If you get shot and you can still be stabbed with an epi pen by the medic, you are WOUNDED. Not dead. Adrenaline isn't going to bring you back to life, you know.

When your death counter reaches '1' or when you are 'dead-dead', that means you're out of the game.

I know exactly what you mean Nix but the thing is that people get confused because if you're saying that you're wounded people think that you've just been shot and just need a bit patching up. I think that's the reason people say dead instead of wounded - to remove the confusion. And "dead-dead" when you can't get revived.
I just use "I'm down" instead of wounded and "dead" when I really am dead.

Great scenario. I especially like the Dead=dead thing. Only problem is too many rules! Honestly they need to be simplified. Something like:

BluFor
- When dead you may not respawn!
- Only assets allowed: BH/Chinook for trans (No gunship)
- No APC only humvees/Jeeps
- Kiowa for Recon (maybe gun run but no missiles)
- I like the only smoke mortar allowed,
- Fobs allowed but no weapons (Sandbags are ok)
- Do not camp outside and diminish numbers for prolonged time, every 15 min or so a hostage dies!
- Hostages may not run away unless following BluFor. (Or you can run unless you are called back on mumble, so you can sneak off if they don't see you. We can't exactly stop them or tie them up)

OpFor
- Do not harm hostages!
- Techies allowed (no SPG or bomb cars)
- Stationary SPG allowed? (but should be kept close to hostages. Point is to defend not ambush)
- No mortars
- No Arty IED


Seems like a cool concept, we'll have to see how it works out. Password on server is a given but I think we should do signups for both clan and pubbers (on this site preferably) and the PW will be sent in PM on the night.

Maybe INS should have time to set up before BluFor move out? Something like 20 min to get hostage in place. Then game start and all blufor start in base.

I wouldn't mind being one of the hostages, it sounds fun with 1 chan mumble.

Also to Fill and Nixy I feel the same way.

It goes
1) Bleeding (shot but moving)
2) Wounded (shot and incapacitated)
3) Dead (non-revivable)

Alright, whats all the fuss about? If you know people are getting trouble with it, you might explain it. That's why I was asking, just to make sure . Don't get me wrong that I didn't understand it, or you could be talking in general.

On-topic:
I like the idea of Xazper that hostages can run away and the fact that the Taliban gets 20 minutes to prepare.

But how do you guy see the things about grenade traps? They could place grenade traps all over the place and camp inside an be patient.

sorry to be the advocatus diavoli, nixy...

But WHO do you think should play the hostage?
If they are from the INS team, BluFor will not be able to tell who's'who (hostage or hostile).
If they are BluFor, they would be shown on the map...

What do?

Cool scenario Nix, I also agree with Xazper, simplified rules are better otherwise organisation will be a pain.

Nade traps are a legit tactic imo, Blufor already have the upper hand!

Hostages should be some INS with drop kits/unarmed? EDIT( or in the setup phase, give them BLUFOR pilot kits/unarmed/something kits) Able to shout out to blufor on mumble, but not able to provide exact intel (ie being seen on the map) Imo we'll need clan members to play as hostages or trusted pubbers just to ensure rules aren't broken?

Haha.. hmmm, that's a good one @Chris. But what's wrong if they just drop their kits and occupy none. And held their hands up all the time?

Or
they could take the LAT kits, to recognize them. And what about the hostages, is the Taliban allowed to separate them in divided rooms?

@Capitan:
You convinced me.

Are hostages allowed to take gun if they find one?

Imo grenade traps are a no go. There's no way to remove them and they make storming a room or area impossible as you HAVE to crawl through them or sacrifice a soldier. Yes BluFor have the advantage and honestly I don't mind that. Ins can camp inside the compound and IMO the point of this event is to get some good firefight going, not just to hold out the BluFor. Remember according to MY rules (which are in no way the only way to go) the BluFor can only use grenades and jeeps to shoot from the outside, other than that they have to physically ENTER the compounds.

I like the idea of the hostages being INS using pilot kits or whatever. It'll be a little tricky but they'll just have to yell "Don't shoot" or something.

I don't think they should be able to pick up kits. They are more of a movable player controlled objective than players fighting FOR the objective.

Of course the hostages will have to be NwA or trusted pubbers, further more I think most of the INS team should be NwA, of volunteers of course. INS will have all odds against them and they need some competent players to hold off the BluFor and to make sure no one break the rules and put IED's and traps all over.
(actually I think we should disallow normal IED's too. They're tiny but have a huge explosion in close spaces and there's again no way to remove them other than sacrificing a guy)

EDIT: Also if we have 4 hostages maybe only allow to split in 2? If we have 4 hostages all over the place there's no way they can be extracted without killing nearly all of the ins and It'll just turn into a deathmatch.

Think we are to assume this, hostages are hostages, you won't find a hostage that isn't tied down. Not in a warzone. Therefor i would presume that a hostage is allowed to take a gun, when freed by Bluefor. (EDIT: actually no, they can see the names of "friendlies" and it also works the other way round when moving out, so a single Opfor can see the movers).
As of the kit thing, Opfor should therefor not be allowed to drop their kits, only switch them between each other.

Thats how i would lay out the rule from what i read.
I like the idea of having to check all 3 locations which will indeed give the opfor a bit more time to prepare, but APCs might become a bit powerful on the map. They would force the Opfor into being fully heads down, not showing a thing.
I also don't mind playing hostage.

I love the idea of kiowas being used for recon and reporting to commander.

This scenario sounds really good! How many rounds will be played? Just 1 or two or 3? So that hostages can be normal tali aswell as blufor?

Oh and I wouldnt mind being hostage for a round

ill be around for this i hope op barracuda an quai used to love playin those maps if im working ill try to get on in the afternoons

DudeNukem91 wrote:
1. Just to make sure, so there is no confusing about this. With dead you mean not reviveable anymore?

As explained. If you 'go down' and can get back up with a medic stabbing you with an epi-pen, then you're good to go. If you're 'dead-dead', you're out of the game.

DudeNukem91 wrote:
2. Is there any time/ticket limit for the BluFor?

We could look into this. Depending on what people like. As far as it is right now, it's either until all the USMC are dead (except commander) or the hostages are freed. As they can't respawn, ticket losses are not important. A time limit could be good for the people playing the hostages. Otherwise they might get bored if stuff takes 2 hours

DudeNukem91 wrote:
3. Are the Taliban warriors allowed to use mortars?

I don't quite think you'd be willing to sit in a mortar pit in the compound, when you have snipers and APCs scouting for your heads.. and you wouldn't set up mortar pits when you're locking yourself up in a building, I don't think.

DudeNukem91 wrote:
4. BluFor Commander allowed to use UAV?

Why not?

DudeNukem91 wrote:
5. Combat Engineer allowed to lay down mines?

Yep, I said earlier that anti-vehicle mines are allowed.

DudeNukem91 wrote:
6.
So if I understand it well, the Taliban is allowed to drive around with
their techies anywhere on the map? How about the BluFor haves to
operate in a convoy?

Again, I don't think the taliban will stray too far from the target building, so 'roaming around with technicals' isn't really part of the plan. Remember that the Taliban only have a limited number of people. Maybe half of the BluFOR in total. They can't spare men on roaming the countryside.

DudeNukem91 wrote:
7. HMG's allowed?

Can be, but most likely not very useful. You can't go spreeing into the houses.

DudeNukem91 wrote:
8.
What if one of the hostages got killed? (Not quite sure about killing
them. Because the Taliban ppl will might think "Hey let just kill them,
then we win!" if there are no dedicated players on that side. If so,
then it will be for the BluFor like: *1 hostage killed* "Ohh, well, who
cares they won't kill them all". Can be quite lame for the volunteers
being hostages aswell)

It's not the idea to kill the hostages. Let us just see it as the hostages being needed by the taliban to trade for their own prisoners or something. They are valuable. Of course, once they are on their way out, being rescued, they can be shot down as the taliban has already 'lost' them. If they can manage that, of course!

DudeNukem91 wrote:
9. I think that it can be quite messy if there will be heavy usage of grenade traps.

Heavy use would indeed hamper assault. Might have to restrict it.

DudeNukem91 wrote:
10. I guess the chat in squad-/teamchat is also limited. Or how about not using chat at all?

No chat, indeed. You have mumble for a reason. Chat will only be used for global coordination of the event.

DudeNukem91 wrote:
11.
Is the Taliban commander allowed to set up markers/waypoints? (Which
will tell the commander by informants that there are 'infidels' seen.
For anyone who didn't know about this)

I think this should not be allowed. I doubt they would have informants standing about on every corner of the map.

DudeNukem91 wrote:
12. So the sqd leaders and commander are not allowed to use the sl channel in Mumble?

They can communicate with their commander through VOIP. Squadleader to squadleader info will have to be relayed through the commander that way. SL might be used for the BluFOR squadleaders+commander only though. Need some feedback on that one.

DudeNukem91 wrote:
Not to be a d**k but for 0600 hours its a quite bright day @ Kokan.

I never said it was dark, was it? And they might not attack until a full hour (or two) later.

DudeNukem91 wrote:
How is this Operation going to be called?

Operation .. ehm.. I'm no good with names.



As for the hostages. I do think they need to be on the taliban team. As pointed out they are indeed visible on the map if BluFOR (I totally forgot about that one). They could just be unarmed and lie on the floor with their hands on their head. They can't use pilot kits, as I don't think they are accessible for Taliban?

It is totally up to the taliban to 'hide' the hostages. Whether they put them all in 1 room or split them up should not be restricted I think.

Upon exfiltration, I don't think the hostages should be given weapons. Main reason being: if they kill someone, it'll be a 'teamkill'. This could alert people to their escape. However the map will also display the hostage 'squad' on the move..


As for set up time: Yeah, of course both teams need time to set up.

Taliban:
-Needs to prepare ambushes/mines/traps.
-Might need to spawn in a technical inside a closed compound.
-Hide the hostages.

BluFOR:
-Needs to make squads.
-Needs to decide on asset use. How many APCs/Choppers and who to crew them.
-Needs to set up one FOB near the target compound, unless it's the compound close to the US main (D5). Then they can use that as a base of operations.

I'm up for this 100%. I can't wait for some of these scenarios!

PS - I'd love a slot.. I'm fed up of moaning about not being able to get in!

Thanks, for the answers. Good to share thoughts.

Again, I don't think the taliban will stray too far from the target
building, so 'roaming around with technicals' isn't really part of the
plan. Remember that the Taliban only have a limited number of people.
Maybe half of the BluFOR in total. They can't spare men on roaming the
countryside.

If the Taliban goes All-in. Some brave men could set up an ambush with technicals and rpg to harrash the convoy/vehicles. (But like you said this is most likely not going to happen, but you never know)

I don't quite think you'd be willing to sit in a mortar pit in the
compound, when you have snipers and APCs scouting for your heads.. and
you wouldn't set up mortar pits when you're locking yourself up in a
building, I don't think.

Hmm, I dont care. You can place mortars so that youre in cover.

The thing about the waypoint markers. The commander of the Taliban side can set up waypoint markers. These waypoint markers tells the commander when there is BluFor crossing it. Its not something I just made up, its in the actual gameplay.

How about a rule on the usage of the UAV. UAV after 20 minutes?

Sign me up! ^^



As for maps, I only request Battle for Qinling AAS alternative, Shijia Valley AAS standard and Kashan Desert C'n'C alternative.

EDIT: Also Silent Eagle AAS alternative pl0x (#AASmasterrace)

i wouldnt mind playing some skirmish...

Can we not just give them pilot/blufor unarmed kits at the start of the map during the setup process? Hostages will be some of us anyway so there will be no rule breaking, just get them to come meet in VCP or something and give them US kits... while talis are setting up

Taliban can only use BluFOR rifleman kits. Not pilot kits. That's the point.

Imo just let the hostages drop their kits and let them held their arms up all the time. In real life rescue teams have to be carefull with freeing hostages aswell. But the disadvantage is that the Talibs probably use them as human shields or being in front of the hostage. That could be extra difficult, I think. Could be disallowed.

EDIT: And if the hostages are escaping BluFor can swap kits with the hostages, while the BluFor take a remaining talib/blufor kit. The main thing the hostages have to keep close to the blufor. Otherwise it can be seen as enemy/talibs with blufor kits.

Or hostage not allowed to get kit. Stick close to blufor.

Maybe the team have to use teamchat, and say something like: "Got hostage(s)" or if they are divided "Got 1/2/3/4 hostage" etc. So the blufor is aware to be more carefull with shooting.

Btw on my prev post talking about waypoint markers not sure if it works for taliban(Kokan)

This sounds awesome, sign me up pls! (Hellspawn_Hunt3r)

Also, great scenario with the hostage rescue, might I add a few more?

#1 Armed Escort

Simple, Team 1 must escort a specific man (VIP) or vehicle from A to B without losing it to the enemy. Considering how easy it is to blow stuff up in this game, I'd allow respawning and team 1 would get a limited amount of tries/vehicles to get to point B.
It could go both ways in a Dota style gameplay, where each team much reach the target destination and at the same time make sure the enemy doesn't reach his.
The vehicle could be a suicide vehicle for the insurgents.

#2 Assassination

Team 1 must eliminate it's target within a set amount of tries and time. "Last known" locations of the target will be given at regular intervals. Team 2 can/have to move the guy they're protecting to a new location once every 30mins for example.

#3 Search and Destroy

Pretty much like CS or the CoD game mode, Team 1 must escort their Combat Engineer to Team 2's "bomb sites" and plant the c4. If the combat engy goes down his teammates can pick up his kit (picking up the bomb).
Works best in small areas (fe silent eagle's missile silo or several kokan compounds) and with small unit sizes.

Those came to my mind when seeing this thread. If I get any other ideas I'll make sure to post 'em.

Assassination sounds cool.. But then more in a Scout/sniper kinda gameplay

kerrermanisNL wrote:Assassination sounds cool.. But then more in a Scout/sniper kinda gameplay

Not necessarily. We can limit that with rules. Everything can be changed if people want to.

Hunt3r xXx wrote:This sounds awesome, sign me up pls! (Hellspawn_Hunt3r)

Also, great scenario with the hostage rescue, might I add a few more?

#1 Armed Escort

Simple, Team 1 must escort a specific man (VIP) or vehicle from A to B without losing it to the enemy. Considering how easy it is to blow stuff up in this game, I'd allow respawning and team 1 would get a limited amount of tries/vehicles to get to point B.
It could go both ways in a Dota style gameplay, where each team much reach the target destination and at the same time make sure the enemy doesn't reach his.
The vehicle could be a suicide vehicle for the insurgents.

#2 Assassination

Team 1 must eliminate it's target within a set amount of tries and time. "Last known" locations of the target will be given at regular intervals. Team 2 can/have to move the guy they're protecting to a new location once every 30mins for example.

#3 Search and Destroy

Pretty much like CS or the CoD game mode, Team 1 must escort their Combat Engineer to Team 2's "bomb sites" and plant the c4. If the combat engy goes down his teammates can pick up his kit (picking up the bomb).
Works best in small areas (fe silent eagle's missile silo or several kokan compounds) and with small unit sizes.

Those came to my mind when seeing this thread. If I get any other ideas I'll make sure to post 'em.

i kile theese ideas, esp. #2

Assasination sounds good, i.e Jabal, the job of US is too assasinate 2 AA dudes(they have to always have the AA out so they can be seen).

MEC can have some time (10 15 min) to organise a defence, 1 AA could be in jabal, 2nd AA DAM(or anywhere apart from Jabal). Or.....2 AA dudes could be inside Jabal, MEC set up a defence and US job is to fight through too Jabal, havent thought of ze rules but no CAS and trans, maybe only to west beach where they will establish a fortified FOB.?

This sounds awesome, I'm down 200%!

oh i forgot my nick has changed from _Smurf_cFc to _Smurf_1st forgot my password for cFc (( prob kop is gona have a drink over this.

but could u change it plz " DA BOSS" cheers

The AA guys would just hide and it would took forever to find em.
If that would not be allowed, they would be sniped.

Tarranauha200 wrote:The AA guys would just hide and it would took forever to find em.
If that would not be allowed, they would be sniped.

thats the whole point tarra...its assasanation...if he gets sniped US wins easy...if they will be inside Jabal due to the rules why its gona take forever? I assume the AA dudes will have heavy protection so when u see s**t loads of people than u prob found the "target" no?