Guardian

See OP Edited with Mission Details. We've listened to the discord and forum polls. If you're not happy with it, make sure you have your say next time!

Good point.... 14 April 19

Server Start Time: 5pm AEDT (Server time)/7pm NZT Mission Start Time: 5:30pm AEDT (Server time)/ 7:30pm NZT Location: StrayaGaming I and A Event Server (search "straya" to find the server, which will be active 30 minutes before the operation commences). Password: straya Situation: Community Zeus: @Guardian, Using Snohman’s Op Hammertime as an idea template. The Russian 10th Armoured Brigade has deployed in to the east of Altis. They have established several outposts to maintain control of the area, while the US Army desperately repels their offensive east of the main airfield. They have several successive lines of defense along the peninsula, and their naval presence east of the island has ruled out an eastward assault. In order to break the deadlock, Task Force Straya has been tasked with conducting an amphibious landing in the North East of Altis, and advancing south with an armoured spearhead to drive into the enemy base of operations. Mission: Task Force Straya is to complete the following objectives: 1. Clear the Molos Airbase 2. Break the Sofia Defensive Line 3. Destroy the Delfinaki Outpost 4. Break the Ioannina Defensive Line 5. Destroy the enemy’s main base 6. Find and kill the enemy commander Execution This operation will be conducted in a free-reign manner. Personnel are free to attack the objectives individually if they wish. However, group management will be as per standard I&A, therefore grouping up and teamwork is highly encouraged. Intentionally interfering with other teams’ plans will not be tolerated. Control Measures: Respawn markers will follow the unit forward at certain undefined points Logistics: Dress: NATO. Equipment: Individual preference. Weapons: Individual Preference in accordance with the above. Vehicles: M1 Abrams and other US/NATO Tanks will be provided upon landing. Mods: RHS USAF AND RHS AFRF (Russians) will be required Blastcore and JSRS Sound Mod are optional Timing: Group on the I&A Events Server this Sunday 14 April at 5pm AEDT/7pm NZDT for a 5:30pm AEDT/7:30pm NZDT start time. Late entries are acceptable - just tie in with a group or fight your way into the fight. Feel free to message @Guardian at any time on discord or in the forums for more info. This thread will be updated with more info for the mission in due course. May the Force be with you all. We have decided to use the RHS AFRF Modset for this mission. This is available here: http://www.rhsmods.org/ These missions are for you, and we can make what you want to see! We will be seeking feedback on how this went from your perspective in order to make it better in the future. More details will be updated in the coming days.

Given how these need to run in order to be effective, if you would like previously posted ideas to be considered; please consider the points covered in my reply from March 26 in this thread and adjust the previous ideas accordingly. There are some awesome ideas from the community, and adjusting them will help the I&A staff immensely. This will allow for your contributions to become reality in our events. @Snohman's last two mission ideas in this thread are great examples of how it can be done. Any questions, feel free to sing out.

Poll to determine the preference for timing of the I&A Zeus Events

Are you able to explain what you're after? Do you want a more diverse range of classes available?

See this topic for an updated mission brief

Server Start Time: 12.00pm AEDT Mission Start Time: 12.30pm AEDT Location: StrayaGaming I and A Event Server (search "straya" to find the server, which will be active 30 minutes before the operation commences). Password: straya Situation: Community Zeus: @Snohman CSAT has set up a naval battery along the Western Coast of Malden, severing trade routes into the Mediterranean and endangering our naval assets. As part of the spearhead to reopen the sea lanes into the Mediterranean, Task Force Straya has been assigned to take out this gun battery as well as a key radar guidance station in the centre of the island. This should cripple CSAT efforts on the island. CSAT is assessed to be well prepared, with a heavy use of minefields and concrete casemate bunkers protecting their naval guns. These bunkers must all be cleared to ensure that CSAT have a difficult time re-occupying their positions. Reinforcements are likely to come from the main airbase in the East.` Mission: Task Force Straya is to complete the following objectives: 1. Clear the Moray Island Airbase 2. Destroy the 3 Naval Gun Emplacements 3. Destroy the Radar Guidance Tower 4. Defeat any counter-attacks 5. Commandeer CSAT vehicles to extract Execution This operation will be conducted in a free-reign manner. Personnel are free to attack the objectives individually if they wish. However, group management will be as per standard I&A, therefore grouping up and teamwork is highly encouraged. Intentionally interfering with other teams’ plans will not be tolerated. Control Measures: Respawn markers will follow the unit forward at certain undefined points Logistics: Dress: NATO Equipment. Equipment: Nil NVG/Thermals, Nil HE 40mm Grenades (Flares and Smoke are encouraged), Nil Bergen Backpacks, Nil Guided Launchers. These are to align with the mission intent which is that it has occured in an earlier point in the overall conflict. Weapons: Individual Preference in accordance with the above. Mods: RHS USAF will be required Blastcore and JSRS Sound Mod are optional Timing: Group on the I&A Events Server this Sunday 31 March at 12pm AEDT/2pm NZDT for a 1230pm AEDT/2:30pm NZDT start time. Late entries are acceptable - just tie in with a group or fight your way into the fight. Feel free to message @Guardian at any time on discord or in the forums for more info. This thread will be updated with more info for the mission in due course. May the Force be with you all.

With the I&A Zeus Mission suggestions, it is recommended that the following guidelines be followed: 1. Objectives and mission flows that you set should be simple and easy to follow by a larger group that may not be operating in a highly coordinated fashion. For example, the objectives you should roughly intend to set are "Find" "Destroy" "Kill" "Clear" etc. 2. The execution/method of the mission should not necessarily be laid out in the briefing (Beyond where you start and how you can get to the objectives). This allows for people to join midway through rather than missing out by 10 minutes and being forced to miss it for the week. 3. Rescue, Stealth, and nitty-gritty complex missions are difficult to run within these constructs and should be avoided. This can be compromised, but should be considered as a rough guide to make sure that your mission isn't drastically altered. 4. Missions that fail if stealth is not achieved are difficult, if not impossible, to run. However, if being discovered makes it harder, then this can be worked with 5. Mission templates are recommended to be sent to Webbie or Orion to be added to the server prior this will greatly assist staff in the creation of the missions. However, ensure that the main bases you build aren't horrendously complex, because they're often only seen for 15-20 minutes maximum anyway and are often difficult to create/transfer. 6. Don't send the mission file with any objectives, respawns or other modules included, this should also be done on the fly. If anyone has any questions on how to alter their mission flow while still trying to remain tactical, please don't hesitate to message @Guardian on discord or the forums to discuss these and work through them so that your missions can get run. After all this is your community and your ideas are key to the continued success. webbie edit: Some things can be negotiated and I am happy to edit the mission to get it as close to what you want as we can as long as it falls into the guidelines for flexibility above.

Tonight, 23 March, at 5pm AEDT/7pm NZDT a Zeus Operation will be run on the Events Server under Noskire and assistance from myself. Poke @Guardian in Teamspeak or Message me in the forums for the password. Understanding this is late notice, but we will also put this notice into the game servers as well. Briefing will be conducted on the server around the start time! RHS USAF will be required if you want to be able to see the vehicles.

This is the first Community Zeus event for Straya I&A - with the idea being to reduce the workload on our tireless admins like @webbie ,@Noskire and @Fitz running some epic missions at the moment - and putting in a lot of time and effort to keep this community running and entertained. Server Start Time: 12.00pm AEDT Mission Start Time: 12.30pm AEDT Location: StrayaGaming I and A Event Server (search "straya" to find the server, which will be active 30 minutes before the operation commences). Password: straya Situation: CSAT have landed a significant quantity of combat supplies, troops and vehicles in the port of Tuvanaka. It is assessed that they are planning for a major offensive against Georgetown and the NATO Airbase. The main NATO Force is tied up in the remainder of the Horizon Islands, and as such Task Force Straya is tasked with neutralising the key assets in the area before they have a chance to strike. Mission: Task Force Straya is to land and achieve the following objectives: 1. Destroy the Supply Cache in Tuvanaka 2. Destroy enemy IFV’s under repair at the vehicle range 3. Destroy grounded fighter aircraft at the airfield 4. Clear the radar installation in the centre of the island 5. Kill the Logistics Commander (Colonel Mahadi) Execution This operation will be conducted in a free-reign manner. Personnel are free to attack the objectives individually if they wish. However, group management will be as per standard I&A, therefore grouping up and teamwork is highly encouraged. Intentionally interfering with other teams’ plans will not be tolerated. On completion of the mission, return to the FOB for further tasks around Tanoa Control Measures: Helicopter CAS will be available – and will operate in accordance with I&A ROE, in that they must be called in on a target. CAS is NOT permitted to engage objectives to complete them. Logistics: Dress: NATO Equipment only Equipment: Individual preference Weapons: Individual preference Medical: Standard Arma 3 revive system (It’s slow, so make sure you stay alive and look out for your mates) Transport: 1. Mk V SOCs will be available to land personnel 2. UH-60 Black Hawks will be available to land personnel 3. Helicopter CAS will be available in the form of an AH-64 Apache – available to the dedicated pilot slot. Mods: 1. RHS USAF is required 2. JSRS Soundmod and Blastcore are optional Command and Signals Individual preference. It is encouraged to group together and complete objectives that way – however there will be no set chain of command or overall commander Timing: Group on the I&A Events Server this Sunday 17 March at 12pm AEDT/2pm NZDT for a 1230pm AEDT/2:30pm NZDT start time. Late entries are acceptable - just tie in with a group or grab your two machine guns and rambo it in. Feel free to message me at any time on discord or in the forums for more info. May the Force be with you all.

Ladies and Gentlemen, For those of you who haven't seen this in the main forums! THE OBJECTIVE: Following the epic clash between the three pillars of Straya Gaming in Operation Velvet Thunder, a sequel has been planned to include more bloodshed, greater stakes and the most prized thing of all: REDEMPTION Each 15-man unit from Invade and Annex, Altis Life and Wasteland will begin the event with control of one town/zone. Your goal is to seize the other two zones without losing your own. If after an hour has passed no single team has secured all three zones, the team with the largest number of player-kills will take the title. TASKS: Secure all three zones Eliminate any opposing forces CONTROL MEASURES: Teams: To represent a server, you must play most frequently on that server (as in Velvet Thunder). Vehicles: You will be given a set arsenal of vehicles available for use. These vehicles will respawn after 60 seconds. Weapons: No limitations have been applied (may change). You may use whatever weapon/launcher/explosive you wish. Equipment: Thermal equipment has been restricted; including sights, thermal capable NVG and launcher sights. Respawns: No limitations have been applied. You have unlimited respawns. Game Mechanics: Stamina has been disabled. 3rd person is disabled. (May change) TEAM COMPOSITION: Team Commanders will be chosen by each server's staff team, who will select members for their team. If you are interested in being a Team Commander, please contact @Guardian ASAP. All players who wish to participate should send an expression of interest to @Guardian or @Asnee, who will direct you accordingly to a team. 15 members per team (may be increased to 20 if required) WHEN, WHERE & MISC: The event will take place on Sunday the 24th at 7PM AEDT. If you are participating, please ensure you are in TeamSpeak (ts.straya.life) by 6:30PM AEDT. Server Commanders and participating players are encouraged but not required to join our new events discord for easy communication and planning leading up to the event. A detailed mission brief of the zone locations and available vehicles will be made public closer to the event date. PRIZES: Prizes will be available for the winning team, top kills, and most strategic play. Prizes are as follows: Winning Team: Event Winner TeamSpeak tag Most Kills: $20 Steam Voucher Most Strategic Play: $20 Steam Voucher I'm the team leader for this, so if anyone is wanting to join our I&A Team and support the cause of earning our redemption through Wasteland and Altis Life's blood - message me through the forums or in discord (guardian#4314) Don't reply to this with Expressions of interest, MESSAGE ME. I'll add you to the channel so we can plan our winning strategy. Hope to see you there. Any questions - fire away!

I'm on the fence on this one... Changes could be made to improve it, but there may be behind the scenes reasons as to why not. I agree with some of the points, but not others. What I don't agree with: 1. Unlimited Spawns (Once you take a HEMTT Medical there, they very rarely run out after that - so all it takes is a Pilot/Land Logistics System to keep it effectively unlimited atm) 2. Having a helo spawn on the pad (I think that it's unnecessary given the main base's location and flight time - this is from the grunt perspective tho) I do however agree that: 1. A teleport to FOB option would be beneficial from base. Means that it would be used for, and could then cut pilots flight time if that was an issue. 2. A more diverse range of vehicles might not be the worst thing. So long as they still required resupply by HEMTT Box/Huron Crate to use. Indifferent: 1. AI around base, I don't really have an opinion - if it reduces any kind of performance then probably not. But meh 2. Praetorian, Meh. I'm not affected by this change enough to have an opinion

I imagine I'm about to be torn apart for this, but I also want people to keep in mind that it's very easy to look at things in hindsight - and to tear apart how everyone else has done it because you have the perfect solution. Some good work was done by several people, and in the end a few of us made mistakes (Myself most certainly included) which aligned to result in a critical mission failure. Our Zeus' did well given the circumstances and they've been hung enough and issues raised in this forum have already been raised and agreed upon in our after action reports within Teamspeak. As the overall commander - I would like to acknowledge my failings for a lot of the decisions I made based on information I had at the time. In hindsight I would change them, but there are decisions which at the time I firmly believed were the right call and I stand by their execution and at times, subsequent failure. The Recon Team: Admittedly, my field of expertise is not reconnaissance nor sniping nor overwatch - in reality or game. I admittedly made a token decision on where to place the recon team which ultimately resulted in their immediate demise and limited usefulness throughout. The plan for visibility on the south side of town was for Demon to observe the south side and report. There will never be a perfect OP that will not be scouted by the enemy. I should have taken this more into account. I would like to acknowledge the hard work of @BigRed and @decibel_spl in persisting with my failed recon plan. The Transport: I had made prior arrangements to transport each callsign into the AO - initially this was for a Blackfish to insert Demon to near their AO to prevent the long drive. However with a lack of qualified pilots for this on the day, the decision to drive was made to get the mission moving. In future, I need to peg down pilots with experience earlier and ensure they know they will have a pivotal role - and include them in the planning. The Loitering Helo: This decision was made based more on real-life scenarios rather than in-game ones. The overall plan involved Demon setting up a cordon and Angel then immediately deploying into the town to achieve surprise, violence of action, and simultaneity. However when one was delayed, the other was too. And when the latter was then delayed I had to further delay the former. While realistically, this may have been a feasible course of action (Not necessarily the best one), I didn't factor in the in-game effects of boring somewhat impatient (and rightly so) players. Zeus Co-ord: In future, I think it would be better for the commander to liaise with Zeus so that they can both war-game accordingly. In these scenarios the NATO Commander gives up their gameplay to coordinate squad leaders; and as such them knowing what Zeus is about to do isn't the worst thing in the world. It's how the squad leaders react which identifies where the magic happens. I should have made contact with Zeus in this instance. As stated I take the majority of the responsibility for the failure of this operation. @Farqman I did have several General Garrison moments, and several moments in the aftermath where I was kicking myself for my decisions. But as stated, I made them with the information available and as I stated above. The important thing is that we learn - and don't hang our Zeus, Squad Leaders and other teammates for some epic work that they put in, to the point where they're afraid to try and lead because of the backlash they've faced or seen others face. This doesn't mean don't give criticism - but make sure it's constructive. This is not in reference to any particular post or reply - but just something to keep in mind in the future. If I lead you again, I will make these improvements in the future. Kia Kaha, And May the Force be with you.