Schubz

dear sir, you may consider to take a second look at the date you provided for that event. cheers anyway

Task Force Ahoy - Prologue Pt. 1.5
Modset required
AW TF AW Halloween.html
 
Situation
On your escape you setup camp in the forrest nearby. After a prolonged talk around a makeshift camp fire you wonder why the intel was a bit sketchy. Meh.. you fall asleep, but out of nowhere, you wake up with a sudden sweat wondering what you're hearing. A voice. A voice telling you to reach the drop zone... move.
 
 
Friendlies
- x4 Hunter team elements
 
Enemies
- Unknown
 
Mission
Listen to the voice. Reach the drop zone.
 
Special Mission Specific Notes
- I don't know what is happening.
- What's that voice?

The next instalment of the CHADS franchise is starting next Friday, 4th November.
 
In the small African nation of Anizay the Military has joined forces with a local insurgency to overthrow the democratic government.
In a small stroke of luck the police force has stayed loyal to the government and the people and thanks to the insurgency they are heavily militarised.
 
Government forces have managed to hold control over what is being called the "Green Zone" which is the area in the North East.
The UN and the African Nations are bogged down in bureaucracy and military aid is slow to be provided.
 
Through back channels our partners have agreed to fund our activities in the region.
The CHADS are being tasked with disrupting and dismantling the COUP forces in an effort to stabilise the lines and provide the government enough aid to hold out until a multinational force can arrive to help.
 
Modset:
Arma 3 Preset CHADS Stabilise.html 
 
 
A Police Squad preparing for a patrol
 

 

A Police QRF force leaving FOB Obeh

Task Force Ahoy - Prologue Pt. 1
Modset required
AW Task Force Ahoy.html
 
Situation
The world has escalated into conflict. China, Russia and USA is mobilizing and every country is in play. Each nation must thread carefully to avoid stepping on toes, which could result in all-out war. Knowing their stance, the majority of NATO countries has agreed to use their military power to defend their own and allied borders, however knowing the threat of what could come, the military intelligence agencies within has created a specialized task force, made of the very be-... made of soldiers to carry out missions with no liabilities.
 
A special military grade decrypting tool has been let loose. Its function is to decrypt military cyber defenses, leaving it vulnarable to hacking and interference. One such tool cannot be left in the hands of our enemies. Intelligence points to a trade being made in Georgia between a known cyber group and a militia group. We need to interdict the trade and get our hands on that tool.
 
 
Friendlies
- x4 Hunter team elements
 
Enemies
- Unknown
 
Mission
Interdict the trade and acquire the tool.
 
Special Mission Specific Notes
- This mission is pure stealth. Something we're VERY good at.
- Your cover must NOT be blown. ROE and tactics must reflect this.
- No support are available.

This whole conversation seems to be making a proper mountain out of a molehill. Ignoring any personal connections to rules, I agree with Artemis' comment that ' I do not feel this has ever been unclear for 99% of the players '. We have a lot of players rotating through the server, and even new pilots tend to get it right first time, and even the ones that don't usually adjust after a reminder or some guidance from a member of staff (or even just one of us spartans or a player) it is rare that we have to remove a pilot for anything that's not related to wasting assets or fire support.
 
Your argument still seems centred around the 'awaiting request' rule, which as I mentioned is not about logistics assets (it's in a different section of the rules, does not specify pilots anyway, and relates to fire, not logistics support, and as it's all part of the same rule you can assume it relates to the same thing) so for the majority of this argument we can ignore it, changing it to fire support may clarify this.
 
It is important to also remember we have other rules in place that often cover the edge cases, i.e. 4.4. play your role, 4.8. Being AFK for prolonged periods of time in the server is not acceptable. (Being at your computer does not necessarily mean you are at your keyboard, being at your keyboard means you have almost immediate response/control over what's happening, being at your computer but doing something else does not, therefore AFK) etc.
 
It seems all the problems brought up have adequate provision in the rules, with the ability for staff/admins to make decisions covering any small gaps left. Rules shouldn't be a guide on how to play (we have enough of those elsewhere on the forum) they should be an outline of how to behave on the server. They don't tell any other role how to play (requirements for medic kit on medics etc does not make them play that role, it just makes the role more appealing to those who will use it as intended) so why should we add in that provision for pilots, especially in a case that so rarely comes up, and when it does, can usually be solved by a quick chat in game or TS.
 
The 'unwritten rule' appears to be, as far as I can tell, 'transport pilots should be ready to give transport if needed, and should be somewhere that players can tell they are waiting' which seems to be completely covered by 4.4. Play your role, and 4.3.5. Pilots are required to land in designated areas in base, and 4.3.1. For example, if you're waiting for a support request at pilot spawn, people won't call you (as there's usually other pilots on) even if they did know you're there (but it's quite possible they won't) and you're both not playing your role, and not prioritising logistics support.
 
(Calling me Possum's fine, but i don't think there's any more to discuss about this, it's never really been an issue except in cases that people don't listen to staff, which is covered elsewhere)

You got warned then grounded, congratulations your not the first. 
 
Having been grounded for *checks notes* 60 minutes, having gone AFK (or just sat there eating, more on that at the end) in the slot then on return refusing to go get inside a helicopter and sit still
on the helipads in favour of stand at pilot spawn and attempt to argue the awaiting request and trying to quote rules to the staff member warning you. *of which you got plenty of warning*
 
You got told you were not playing your role, refused to move from standing in spawn to sitting in a helicopter on the pads, with plenty of warning from staff. It was made clear no grey areas plain and simple, staff has the final say. 
 
In conclusion you are not happy that you were grounded and you are now writing out 3 page essays to make it look like it’s an everyone problem when it’s a you problem, at least that’s my takeaway. 
 
On a whole we have “grey areas” in the rules on purpose as EU1 is a public server and all sorts comes up and no one line in a rule will cover everything, it’s why we have moderators that can make decisions on the fly in the moment that best suite the mission/server. 
 
Just before I sign off, is this whole stand your ground and argue awaiting request and grey areas in the rules so you could sit at base, do nothing and keep the limited pilot slot while you eat your meal?

12/08/2022, 17:38:46 : (Group) [A1] Cold: Currently eating dinner, will be activly flying soon again

I understand the problems with grey areas in rules, however I think some ambiguity in rules is important, as it allows people to actually play the game.
 
As I'm sure we all know we're not attempting to strictly milsim our way through playing a game, so specific rules defining specifically what players should be doing with their time become pretty restrictive pretty quickly(as opposed to rules defining what not to do, or giving an area for players to work in, allowing people to execute the rules how they think best). 
 
The grey area also gives staff a bit of leeway as to dealing with players, it's pretty obvious if someone doesn't know what they're doing, as opposed to intentionally messing around or being malicious (in most cases at least), so the grey area allows both guidance to new or unsure players, or punishment to players intentionally getting in the way or acting with bad intentions.
 
Focusing on the pilot rules, requests for logistical support rarely happen, and almost never happen for transport from a FOB. Requests for logistical support are also not required or mentioned in the ruleset (4.4.1 refers to fire support, not logistical support assets, as shown by the first sentence, so isn't relevant, it's a separate topic) because of this, like Artemis I don't see an issue. Maybe changing rule 4.4.1 to specify 'fire support' may remove the perceived link between the rules, which seems to be where your confusion comes from, and as far as I can see would remove all the ambiguities you mentioned (which seem to be contrasting the different rules for transport pilots and fire support assets, which though similar, are not the same.
 

Mission Name:
PMC Ops Recovery Week 2
 
Server Details: 
IP: 116.202.224.207
Port: 2302
 
Mods Required:
Arma 3 Preset CHADS Recovery.html (Plus usual optional mods)
 
TS address: ts.ahoyworld.net
TEAMSPEAK MISSION BRIEFING FOR ALL PLAYERS WILL BEGIN AT THE TIME STATED IN THE TITLE
Expected Mission Length: 120+ minutes (may go over or under expected mission length)
 
Player Slots: 36 
Platoon // 4 man element (Commander, medic, UAV and Pilot)
Alpha - Charlie // 8 man elements
 
 
 
Situation
 
Thanks to the efforts in the previous mission the data from the flight recorder is being analysed and a cause for the crash should be discovered soon. 
Their is still one mission to complete until then. Three Ukrainian service men remain unaccounted for.  There is intel pointing towards 2 locations where items from the crash site were moved. They are to be searched for signs of the missing air crew.
 
 
Assets:
Indigenous vehicles and others acquired on site
 
Friendly Forces:
Local contacts 
 
Enemy Forces:
None
 
Neutral Forces:
Altis Armed Forces
 
Civilians:
Civilian presence to be expected, concentrated in built up areas.
 
Mission
Scout and search the target locations. Recover any information relating to the crash and or the missing servicement. 
 
 
Execution
Objectives:
Scout and search the 2 target locations for the remaining 3 bodies Continue to investigate the cause of the crash where possible
 
 
Movement Plan:
At Commanders discretion
 
Rules of Engagement:
Enemies may be engaged on sight based on current squad orders
Civilians are present in the area so collateral damage is to be kept to a minimum.
 
 
Admin & Logistics
 
Equipment & Resupply:
At the commander’s control, assets are available at base to facilitate this.
 
Reinforcements:
Unlimited
At commanders discretion, transport assets are available.
 
 
Command & Control
 
Command:
Overall command lays with codename "Overlord" who will set objectives and ROE.
Operational control on the ground lies with the Platoon Commander.
 
Communication:
Radio channels are set for each element and can be viewed as part of the map. Platoon has limited discretion for change but structure is to be maintained.

Hey whats up. Im Valentine or Thomas im 23 and from the cold north that is Norway. I’ve been playing on AW servers on and off for about 3 years now and i really enjoy it.
 
I have to say AW Invade & Annex is the best server ive played on so far in Arma. Ive had my fair share of Altis Life, KOTH, etc but Invade&Annex really stuck with me. Anyways im not much of a writer so if you catch me in game come say hello. 
 
Cheers
Valentine

Stuff I wanna see for next op in regards to equipment
Guns
Steyr's Grots/promet HK416/spar FAMAS 1911/custom covert
Headgear
Boonie hats Headsets Beanies Bowman elites(with cap) current headpieces with headset MICH
Uniform
  Vest
TAC RRV Plate  

was always good fun to play with him very positve guy. i will miss him for sure

The now infamous paradrop from the early days of frontlines (caused by an oversight where non-pilot roles got ejected from parachutes automatically):
 

Here's everyone lined up

Many of us have clips, screenshots & audio clips of the great times we all had with Mikael.
 
Time to share them in this thread so we can all look back on those moments. 
 
At the end we can look at compiling these clips into one large montage.
 
 

Hey all,

We have arranged flowers to be sent to Mikael's family on behalf of Ahoyworld with the following message
 
"Rest easy Mikael, 
Your friendship and kind example will not be forgotten.
From your friends at Ahoyworld"
 

Mikael was an absolute incredible soul. Always lit the room up wherever he was and was an absolute joy to be with. He left incredible memories within this community and it will be a real loss without him.

We will forever cherish the time we got to spend with him and undoubtedly he will be sorely missed. 
 

@Sfinx Thank you for letting us know, we've lost an incredible person, had a few deep conversations with him, he will be sorely missed 🙁

It's a real shock to hear he is gone. I will miss him.

Dear members of Ahoy World,
 
It is with great sadness that I have to inform you of the passing of @Mikael on Friday July 15.
He was involved in an motorcycle accident and succumbed to his injuries.
 
I know Mikael was a big part of you community and he often talked about how much enjoyed the ARMA sessions he had with you all.
 
I will come back with more information about the funeral arrangements when I get them.
 
**Update
The funeral will be held July 26.
There has also been created a memorial page for Mikael LINK (page is in Norwegian). Here you can light a candle and leave your name ( Tenn et lys ) or write some words in his memory ( Skriv et minneord ) 
 
And thank you all for your kinds words, it is really appreciate. He will truly be missed by all those who were lucky enough to know him  ❤️ 

To start, the last clip I have from the last Frontlines Wednesday. Will be taking a dive into everything I have later on this week.
 
 

Mission Name:
PMC Ops Recovery Week 1
 
Server Details: 
IP: 116.202.224.207
Port: 2302
 
Mods Required:
Arma 3 Preset CHADS Recovery.html (Plus usual optional mods)
 
TS address: ts.ahoyworld.net
TEAMSPEAK MISSION BRIEFING FOR ALL PLAYERS WILL BEGIN AT THE TIME STATED IN THE TITLE
Expected Mission Length: 120+ minutes (may go over or under expected mission length)
 
Player Slots: 35 
Platoon // 3 man element (Includes 1 pilot)
Alpha - Charlie // 8 man elements
 
 
 
Situation
 
A Ukrainian cargo plane has crashed, without warning, North of Kavala on the island of Altis, there was no contact prior to the crash from the 5 man crew, who were travelling back to Ukraine with much needed supplies.
 
Altis is a heavily militarised nation, which while unaligned, has always been slightly Russian leaning.
The Military Government of Altis is refusing outside officials access to the site and have stated they will perform the investigation and release all data when the investigation is completed. Neither Ukraine or it's NATO backers want to push the matter too far for risk of alienating this small strategically placed nation.
 
The CHADS have been contacted as they are a non state actor and provide plausible deniability to their contractors.
The mission is to enter Altis and investigate the crash and if possible recover the Ukrainian air crew.
Arrangements have been made for the advance team to be inserted via HALO in the early morning, followed shortly after by the support elements. As such no vehicles can be delivered and all assets will have to be acquired on site. Local assets are being cultivated and will hopefully bear fruit.
 
 
Assets:
Those acquired on site
 
Friendly Forces:
None
 
Enemy Forces:
None
 
Neutral Forces:
Altis Armed Forces
 
Civilians:
Civilian presence to be expected, concentrated in built up areas.
 
Mission
Insert by HALO, make contact with the local asset and move to the crash location to discover any information relating to the crash.
 
 
Execution
Objectives:
Find the Ukrainian crash site Investigate the cause of the crash If possible recover the 5 members of the crew    
 
Movement Plan:
At Commanders discretion
 
Rules of Engagement:
Enemies may be engaged on sight based on current squad orders
Civilians are present in the area so collateral damage is to be kept to a minimum.
 
 
Admin & Logistics
 
Equipment & Resupply:
At the commander’s control, assets are available at base to facilitate this.
 
Reinforcements:
Unlimited
At commanders discretion, transport assets are available.
 
 
Command & Control
 
Command:
Overall command lays with codename "Overlord" who will set objectives and ROE.
Operational control on the ground lies with the Platoon Commander.
 
Communication:
Radio channels are set for each element and can be viewed as part of the map. Platoon has limited discretion for change but structure is to be maintained.

What happens when the troops on the ground have been fighting tirelessly for too long? They run out of ammo and general supplies like medkits, explosives, etc. To save a trip for the squad back to the base to restock, they can request a resupply drop filled with custom items that the squad needs or a general multi-purpose pre-filled option. This guide will cover the two types of resupply drops, how to carry them out and also talk about the pros and cons of each. I have given each method a self-explanatory codename only used in this guide so it's easier to reference them.
 
Method 1
SPECIAL DELIVERY
Pros:
Can accomodate custom requirements (missiles, mortar backpacks, static launchers, etc) Cons:
Can only be loaded from main base (very far to most objectives) Slingloading is flimsy so need to take time hooking Harder to indicate it's precise location when unhooked in the air (can bounce and roll when airdropped) Takes time to load the supplybox  
Obtain any helicopter capable of slingloading.
Majority of the larger sized helicopters are capable of slingloading. If you are unsure if your helicopter can slingload you can check by looking for the hook icon in the top left hud element whilst inside a helicopter. I will be using the UH-80 Ghost Hawk.
 
 
Navigate to the main base Supply Crates zone.
Area is outlined in the image below. This is the only place available where an empty supply crate spawns which can be filled with ease.
 
Location of Supply Crates zone at main base:
 
Overlook of what the area looks like:
 
Use the arsenal to fill the supply crate with whatever supplies necessary.
Grab any backpack with a decent load stat and use the arsenal (soldier standing near the 3 supply crates) to select what you need and then transfer it to the single supply crates closest to the landing pad.
 
Soldier NPC who acts as an arsenal:
 
Transferring example supplies from backpack to supply crate closest to the landing pad.
 
Open the slingload panel, fly above the loaded supply crate and hook onto the crate.
If you do not know how to slingload I recommend seeing a separate introduction tutorial about this.
 
Opened slingload panel with indication of a slingable object nearby (green dot):
 
Supply crate hooked to helicopter.
 
Fly to suitable drop location, land or airdrop the supply crate and mark its location.
Ensure you mark an accurate location so the crate is easier to find. You can use the ping ability to ping the crate on the ground from your helicopter and then mark the ping on your map using map tools although you can always estimate a location too.
 
Landed crate at drop location:
 
Marked drop location on the map:
 
 
Method 2
EVERYDAY PACKAGE
Pros:
Very available (can be loaded from any FOB) Takes less time to load and drop (no need for fiddly slingloading) Drops with orange flare for clear location indicator (in intense situations) Cons:
Can only contain the default pre-set general supplies (cannot be adjusted)  
Obtain any helicopter capable of loading a supplybox from base landing pads.
I am still unsure of which helicopters are capable of this however assume it is only helicopters that can slingload for now. Same as the special delivery method I will be using the UH-80 Ghost Hawk.
 
 
Land at any landing helicopter pad with a solid white square.
These areas are commonly used to pick up units from the FOB's or main base. They exist usually on every FOB.
 
Example of solid white square helicopter landing pads at main base:
 
Load the supply crate into the chopper using the interaction menu.
Select the green text "Load Supplybox" option and hold Enter to load. Once loaded you will see a message in the bottom right saying "Supplybox loaded.".
 
Interaction menu option to load supplybox:
 
Airdrop or unload the supplybox at the required location.
Make sure you are at least 300m away from a friendly base. To airdrop a supply crate you need be at least 50m in the air. To unload a supply crate on the ground you must be landed. Either land on the ground and use the interaction menu to unload the supplybox or simply fly high (above 50m) and use the interaction menu to drop the supplybox in the air where a parachute will attach and the supplybox will fall to the ground slowly.
 
Dropping the supplybox using the interaction menu in the air:
 
Airdropped supplybox parachuting down to the ground with orange flare:
 
Mark supply crate position on the map.
Use any method you prefer. Best way I have mentioned is to ping the airdrop once it has landed and then marking it on the map based on the ping location.
 
Map marking of aidropped supply crate:
 
 

and for the privacy consious, discord has no end-to-end encryption, not even in direct messages, plus their voice comm quality is abysmal

Yeah, starting this mission with ACE loaded was kinda dumb, ... Frontline ModSet to have all the choppers available. 🤦‍♂️
Anyways... Played tonight (with the recommended mods) and it feels like PERFECTION. JJ Cakes - great work! Thank you! 👌

 

@Tommy_ you can post any idea or guide in the I&A section and mention the staff who will review it. You will also get feedback from the community and any additions or edits can be done. Staff can then decide if the guide is ready to be moved to the Official Guides section. Hope this helps and looking forward to some new/updated content.