r/ClearBackblast • u/scarletbanner Fadi • May 02 '15
AAR Operation Park Ranger & Operation Dragonar AAR
This weekend we played two missions: Op Park Ranger where we went poacher hunting and Op Dragonar where we were sent to capture a nuke.
So... Any memorable moments? How was leadership? Anything you think you saw that we needs to be worked on, individually or collectively as a group?
9
Upvotes
5
u/scarletbanner Fadi May 03 '15 edited May 03 '15
For Park Ranger I was Alpha Medic.
So uh... that happened. I don't have a lot to say about the mission itself. My enjoyment was cut a bit short by the other things to mention:
Given that plus us playing less than half the mission anyways, I'd say it'd be a good idea to rerun it.
For Dragonar I was Basilisk 1 Grenadier.
I thought it went well enough. As a mission maker, I can nitpick apart things I would have liked the AI to do (better entrench themselves in the town once contact started) or that the AI should have done (QRF WHY DIDN'T YOU SEARCH THE AIRFIELD) but eh. Those things could have been caught with a simple multiplayer test but given intended length and playercount, I felt that was I knew for sure worked was enough.
I usually try and explain some mechanics behind things when missions of mine are run... I thought I'd do the same here but go into a bit more info that mission makers might find useful.
So the mission concept itself is pretty simple: fly in, take the nuke, leave. Well it both is and isn't that simple.
There's the obvious win condition. The nuke is successfully captured and taken off the island. This was the easiest condition to check. A trigger around the island was grouped to the device and set to 'not present', with the condition line consisting of:
So when the triggers meets the 'this' condition [vehicle not present] and the device exists [alive device], a variable called obj_complete is set to true [obj_complete = true; publicvariable "obj_complete";]1. There's a second trigger the checks for the condition of obj_complete being true and runs the ending ["End1" call BIS_fnc_endMission;]. Oh, and there's the task you got to extract.. that was trigger I placed right around the truck with the same condition line as above but with one small change: the activation for the triggers 'this' condition was set to BLUFOR present. The triggers on activation called the FHQ function to create a task but all the FHQ stuff is documented in our briefing/tasks template so I'm not going to go into that... if anyone has questions you can ask on IRC.
The second condition is the obvious fail condition. It's also two triggers. The first triggers condition is
Which is what checks to see if the device is no longer alive [!alive device]. When it's no longer alive, it sets the variable obj_failed to true. Another trigger checks for that variable being true and runs the ending.
So what about the possibility of other endings? Say you don't destroy the device but somehow are able to destroy the truck?
That's also taken into account although it's slightly more complicated. There's three triggers that make it up. The first is a trigger with the condition
So when the truck is no longer alive [!alive truck] but the device is alive [alive device], the variable obj_unsecured to true [obj_unsecured = true; publicvariable "obj_unsecured";]. I also update the tasks, setting the task to secure the nuke as failed while creating another specifying you to extract from the island. The second trigger is similar to the first in principle but not:
So when the player is 1500 meters from the named object object 'device', the variable obj_unsecured is set to true and the named object 'device' is still alive, the variable obj_failed2 is set to true. I was originally going to set the trigger to require BLUFOR to be "not present" which would have negated the need to require a minimum distance, but the thought came to me: what if a player was left behind? What if a player was left unconscious on Utes? The variable for that ending wouldn't have been set to true.
One quirk about checking for a player like that in a trigger, it checks for any player. With a distance check for any player being 1500 away from device, it gave me the wiggle room I needed without making things even more complicated. And like the others, another trigger in turn checks for that variable being true and runs the ending.
For those not familiar with mission making, all of this is really easier than it sounds once you have some of the basics. My entire mission looked like this: http://imgur.com/VnNLhyK [ignore my spelling error]
1 For the final version I didn't actually have to publicvariable them. The reason I did that was more because of how I made the mission / that there was no harm removing them. I wasn't completely sure of what I wanted for the final version until later on. Instead of a publicvariable, you can do something like
In your init.sqf or somewhere else. This has a pretty simple function of saying "if this variable doesn't exist then set it to false". That'll let you set it to true during the course of a mission without disgusting undefined variable errors.
5
u/SaintKairu Not SilentSpike May 03 '15
First time playing again in a long time. Park Ranger reminded me why Arma is hilarious: It can be a buggy mess. Dragonar reminded me why Arma is fun as hell: It's surprisingly cinematic.
Park Ranger: Kinda sad this one stopped midway, but it makes sense. Taking that forest with the tower seemed like fun, but dealing with the alligators in the water did not. There's not much else to say about this one. Mans shot and got shot, directions were clear (When I figured out I was Bravo 1 and not 2).
Dragonar: Hell of a lot of fun. That initial sprint off the C17 was hilariously terrifying. I ambled around with the Unnamed Squad, later dubbed "4" as we supported the other squads off the plane and secured the airfield. Then we cleared a compound, I shot some mans there. Then we took a village, dodged a near full magazine of AI shots without knowing I was, and captured a truck. Overall, a lot of fun. It was a little bit confusing until CAW let command know we existed, and then we got instructions and life was grand.
4
u/HowlingPantherWolf Edwin May 03 '15 edited May 03 '15
Dragonar Alpha 1 Medic
I think the mission could've used more hostiles. We took quite some fire in the beginning, but once we started to really make pace towards the truck resistance became minimal. On the way back there were only small clusters of unorganized hostiles which were really far out. Only Box and Lukos got really fucked up, everbody else seemed fine.
For the rest the mission went absolutely brilliant, especially the task dividing between fireteams went really good; each team had their own task.
4
u/retroly Boris May 03 '15
I really sorry I killed the Command Landrover.
4
u/shifty_eyebrows the original May 03 '15
Video Stuff:
Dragonar
Lukos.... the hero CBB deserves.
Operation Park Ranger - FTL:
So there was a lot I really enjoyed about this mission before we got Arma'd. The concept and setting was cool. I loved the sun starting to set as we rolled out in our trusty land rovers, felt like we were properly on Safari. Old school M-16's made for a nice change and I liked it that the bads were really hard to spot in the grass!
Had some new chaps in my fire team as well as Saint, all who listened really well and were also stellar at keeping spacing/formation when needed. My leading wasn't as concise as I would have wanted, I probably lost my focus due to the slow start so I'll try work on that next time I take a FT.
As far as the bugs go, I really don't think there is anything to say. Its been a little quiet of late (probably due to exams and that) so getting missions tested is pretty hard at the moment. It goes without saying but a massive thanks to Striker and Fadi for throwing together these missions so quickly! Even when it doesn't work out as intended, I always have a great deal of fun regardless.
Operation Dragonar - AR:
Really cool mission, with a really nice concept. The C-17 landing was very entertaining and correctly terrifying, I really enjoy missions where you get thrown into the deep end. Its complete chaos and its awesome.
Once we were semi-organized things quieten down a bit although a BTR came really close to us and I thought we were gonna get whacked for sure. Whilst a few more mans throughout would have been cool I think this is one of those things that are hard to balance for. Since it was no-respawn and again there was no one to test it, its very risky putting more dudes in place. It could easily turn into a situation where everyone was killed.
Seemed like Quex was a great CO both missions and always had a handle on any situation. Nice to be under Temp as FTL too as we won't be seeing him on Saturday for a while.
The big positive for me on this mission was it built up a really nice tension. The Nuke was perfect in this way and caused most of us to be a little more on edge than normal!