Liberty Bull

That's exaclty what I mean. It could be due to my beginner level of scripting knowledge, I tried looking through the various functions to figure out how to just call it on the on AI group without having to have the player command it.

I am trying to figure out a way to simply have one designate AI unit to follow the path. I can get the whole team to follow my custom plan in the example mission, but cant seem to figure out how to modify it to simply have an AI enemy guard continuously cycle through the points. Any help would be appreciated as this would make AI work with custom building interior compositions I am using in my open world style mission.

As title, after loading up today, any trigger already placed in any mission, even ones I didn't make, have their conditions replaced with "call {this}" or "call {variable}". Any new trigger I place and then save/load is normal with simply "this" in the condition.

I suspected this being that CBA updated today and that this behavior started today. It also caused some issues with another mod "Improved melee system" where it throws a script error on missions start begining today. I thought my mission was about to kill itself, but I suppose it is fine.

One issue I notice is the dog will attack enemies hidden with the show/hide modules.

**** Figured out the solution through trial and error, if anyone is curious, here is the working code. nametagALayer = "nametagA" call BIS_fnc_rscLayer; _textnametaga = parseText format ["<t font ='RobotoCondensedBold' align = 'left' size='0.6' color='#ffb742' shadow='2'>%1</t>", name cursorObject]; [_textnametaga, 1.0,0.0,/*durata*/ 30,/* fade in?*/ 0,0,nametagALayer] spawn BIS_fnc_dynamicText; I am trying to get text to pop up with the name of the AI you are looking at. This following code is executed from an SQF file and works to deliver text I fill in, but instead of making a custom sqf for each AI name, I'd rather make it work so it grabs the characters name from the game. nametagALayer = "nametagA" call BIS_fnc_rscLayer; _textnametaga = "<t font ='RobotoCondensedBold' align = 'left' size='0.6' color='#ffb742' shadow='2'>" + "Easy Pete"+"</t>"; [_textnametaga, 1.0,0.0,/*durata*/ 30,/* fade in?*/ 0,0,nametagALayer] spawn BIS_fnc_dynamicText; Now, when I put this into a hint, the hint does what I want. hint format ["%1", name cursorObject] But I am having trouble figuring out how to mesh the two concepts. I am pretty new to scripting so I am sure I am making obvious mistakes that I don't realize. So trying to put it this way below only results in the "format ["%1", name cursorObject]" literally being the text that appears. nametagALayer = "nametagA" call BIS_fnc_rscLayer; _textnametaga = "<t font ='RobotoCondensedBold' align = 'left' size='0.6' color='#ffb742' shadow='2'>" + "format ["%1", name cursorObject]"+"</t>"; [_textnametaga, 1.0,0.0,/*durata*/ 30,/* fade in?*/ 0,0,nametagALayer] spawn BIS_fnc_dynamicText; Any messing around I'm doing isn't resulting in what I'm going for, could someone help me with this? ***Edit*** After more research I tried this which seems like it is the proper way, but it is still giving me an error. nametagALayer = "nametagA" call BIS_fnc_rscLayer; _textnametaga = parsetText format ["<t font ='RobotoCondensedBold' align = 'left' size='0.6' color='#ffb742' shadow='2'>%1</t>", name cursorObject]; [_textnametaga, 1.0,0.0,/*durata*/ 30,/* fade in?*/ 0,0,nametagALayer] spawn BIS_fnc_dynamicText;

oh jesus, *facepalm* and I thought I figured something out different with the solution I put up top in an edit, not even realizing I had gotten it right in the end but made a typo. Thanks a million!

Whether its [0,"BLACK",3,1] call BIS_fnc_fadeEffect; sleep 5; [1,"BLACK",3,1] call BIS_fnc_fadeEffect; in initsqf [1, "WHITE", 5, 1] spawn BIS_fnc_fadeEffect; in a trigger, or any sort, the blur effects of the function work, but the black or white part of it seems to be broken, only appearing for a nano second in a "blip". Am I doing something wrong or is the function bugged? I discovered this from trying to simply have the mission fade in from a white screen. *** Edit *** Update, after trying for 30 minutes with the various iterations of the fade functions before I posted this, then doing more searching afterwards, I discovered that titleText ["","WHITE IN",7]; works.

Forgive my poor collage making skills. As title, I wanted to look at the differences between commanding a squad with fireteams using either the "Odds & Evens" style where 2, 4, 6, 8 and 3, 5, 7, 9 are the two fireteams vs having 2 - 5 being one fireteam and 6 - 9 being the other. As you see in the photo, the two organization styles result in the formations being structured differently, especially when giving one (or both) fireteams a move order. Odds & Evens on left, Left & Right on the right. On the interface, Left & Right looks "better" with the colors being together so you can more easily see the status of the fireteams. Starting with the wedge, Odds & Evens results in the fireteams being evenly on the left and right of the squad leader, with the FTL closest, AR next, etc. Left & Right instead has the fireteams both in the same order, but when together as an entire squad one fireteam surrounds the SL, and the second fireteam surrounds the first fireateam. Odds & Eves in this case looks better when using well balanced fireteams like shown here, however if you instead like having seperate fire and manuever teams, "Left & Right" may be better because your "fire" team with the MGs stay close to the SL and your meanuever team is on the fringes ready to move out. When giving a fireteam a move order away from the squad, however, you will notice that the wedge then gets cut in half in Odds & Evens, with each fireteam having a diagonal echelon formation, effectively ruining your wedge when not operating as a single unit. This is "fixed" in the Left & Right structure, as you see when you send out a fireteam, both fireteams adopt a smaller wedge. Next is the line. Just like the wedge, in O&E the fireteams are on either side of the squad leader, and in L&R the one fireteam surrounds the SL, the other fireteam surrounds the first fireteam. Giving a move order functions similarly in both styles, however here is where you can really start to notice that in the odds & evens style, the fireteam with a move order lines up with the fireteam leader standing on the "Move" waypoint with his team to his side. On the Left & Right style, however, the fireteam as a whole stands in the waypoint with the formation center on the waypoint. Staggered column is where we notice big differences again. In Odds & Evens, the two fireteams form two straight columns with the fireteams on either side. When you give one a move order, you essentially are now in two regular column formations. In the Left & Right style, the fireteams line up one in front of the other and keep their relative formations when being ordered to move about. Lastly we have the diamond. In Odds & Evens the fireteams kind of jumble together when in formation. In the Left & Right style, the fireteams again line up one in front of the other. Interestingly, unlike the other formations, when giving a move order the fireteams manage to adopt a sort of mini wedge in both styles. All in all, it appears that "Left & Right" style works out better if you plan on having multiple fireteams because when being ordered to move about the fireteams each keep the formation.

You are right about me limiting what I did in the mission to stay true to the original. Did you play it after I updated for some weapon variety? I did still keep most of them with Mac 10s however I added a few AKs, an RPK by the barn, a CZ sniper at the foreman house etc. Adding a note to the bunker with the sniper in it is agood idea, I will add that. Vehicles may be a good idea, I'll look into it. Moving them from the AO could be an improvement, I do have to consider how it works in Arma as you are pointing out. You know I am normally one to try and make places look good with props, I'm not quite sure why I didn't do that (pathing aside, since the AI doesnt even really go into the building with you). I had given it a thought and then got distracted adding the bunkers. The "charges set" trigger was intentional because I havent tried messing with eventhandlers yet and it seemed like alot of work to get it to detect when the player placed an explosive at the crate, so the next best thing was to have it trigger the radio dialogue after a few seconds as an ad hoc way of doing it. If you know a better way to have it trigger on the placing of the charges I'd love to try it.

Alright, so I took it a step further and I added an intro cinematic that recreates the original, I added getting into the heli and flying off, the heli will come in guns blazing if there are any enemy left alive because once you blow the weapons caches all enemies will run to the explosions. I also did some general polishing thanks to someone who posted a video of his playthrough. Oh and I also added music from SOCOM, only 3 tracks, two for each objective completion and one on mission completion.

You know I should do that for the evac. I didn't because originally I was trying to stick to the original mission as closely as possible and in the original mission a cutscene shows the "insertion" via helo and the actual mission starts out on the ground, and the mission ends when youre in the zone. However, this is Arma and I don't think it would destroy the "recreation" by improving it. A helo escape would be more exciting especially now that I have the enemys rush the area when you detonate the explosive. Will add that in!

Let me know what you think!

Thanks kju

Can't wait for the new update.

I am hot and bothered by this.

Love the new update. Really allows you to make different nations.

I made a mission like this. Its a basic SP/COOP 1 - 15 mission where you defend a HESCO fob against enemies. Currently they attack along folds in the enviornment to try to hide from the FOB as they approach the flanks, so its not in "waves" per se, but in whenever they make it to their respective flank spots. Uses the new respawn system. No revive since you respawn in the middle of the FOB 20 seconds after death. http://steamcommunity.com/sharedfiles/filedetails/?id=768542888