Jump to content


  • Content Count

  • Joined

  • Last visited

  • Medals

Community Reputation

777 Excellent

About nkenny

  • Rank
    Master Gunnery Sergeant


  • Interests
    I live here, Really.

Profile Information

  • Gender
  • Location
    Oslo, Norway

Recent Profile Visitors

2188 profile views
  1. Cool stuff! Literally. -k
  2. @mickeymen Have you checked the gitHub wiki? https://github.com/nk3nny/LambsDanger/wiki/Variables-and-functions ---- Here is the first of a three part series that covers the design philosophy of LAMBS Danger and how the module system works. Next video will consider Zeus and a more in depth look at the various modules. -k
  3. LAMBS Danger.fsm affects no weapon settings. With that said, the shared information may have other emergent properties. If anything the tendency of infantry to move and shoot in cqb may cause decreased accuracy. -k
  4. @LSValmont <unit> setVariable ["lambs_danger_disableAI", true]; -k
  5. LAMBS Danger fsm New release: Current version 2.4.4 *HOTFIX* Changelog Added context_menu actions support to the Zeus Enhanced mod Added configurable setting for ‘combat mode’ sharing distance Added patrol option to taskGarrison and taskCamp (default is disabled) Improved taskAssault (more reliable) Improved taskRush with dynamic cycle times Fixed random suppressive fire in taskCQB and improved house selection routines Fixed vehicles suppressing through terrain and high flying aircraft Fixed units will more reliable man static weapons in taskGarrison and taskCamp Fixed units will more reliably deploy static weapons from modded content Fixed units with LAMBS AI disabled will no longer be forced into combat mode by information sharing Fixed artillery registration issue Fixed in Zeus, moduleCQB and moduleAssault would always delete the logic even when asked not to. Fixed various issues in Eden and Zeus modules This version fixes and improves many small aspects of the mod related to task modules and group level behaviour. For players using the Zeus Enhanced (ZEN) mod, we’ve also connected the modules to the contextual menu for ease of use. The next move from the team will be an restructure of the naming scheme of many of the functions. As LAMBS Danger has proceeded the complexity of the project has increased. We are experimenting with future features. among these are: enhancements to artillery, a much requested reinforcement system, adding a post-combat AI, a dynamic close air support engine, and various other pieces. As always we are committed to keeping the mod from overriding mission makers intentions and hence creating a seamless improvement to the game. From the team diwako / joko / nkenny
  6. @mickeymen TaskGarrison is meant to be a long term garrison, not simply checking a building, or temporarily holding it. Because the waypoint is actually a handler for a scripted function and not a "way point" in the BIS sense, it should be treated as end state when activated through waypoints. There are technical and game design reasons for this. It is, however, possible to skip out of the garrisoned state. You can do that by using the taskReset module, or simply by running the taskReset function directly on the unit you wish to have abandon the garrison. That could be achieved within the trigger or statement you are using to have the garrisoned unit move again. The function to taskReset is [<group>] call lambs_wp_fnc_taskReset; Doing so comes with the limitation that this group will be fullly _reset_. Essentially the members of the group will join a freshly created group. -k
  7. @mickeymen 1. We allow the waypoint modules to be a little more invasive in terms of changing behaviours and combat modes. Best way to see which do what is to experiment a little. That said: When AI enter buildings, they are often limited to walking pace. This is a limitation of pathfinding. 2. In the same spirit as (1), the waypoint modules are not designed from the ground up to be easily linked into a chain of actions. These are better realised as "end states" or "fire and forget" modules. Easy ways in which to deploy the AI to a specific task. That doesn't mean it is impossible to string together different behaviours. The way to realise it is by using the taskReset module. Of course, if you are constructing a more advanced mission like that, I would advice creating your own scripted handler and calling the functions directly. @M1stb0rn As Joko says, only artillery units will be added to the artillery pool. Future versions will add CAS support 🙂 @Jimi Markkanen Not familiar with IFA3. By default it will only consider underbarrel grenade launchers. I suspect these weren't really around in WW2. hehe. Perhaps future version. -k
  8. LAMBS Danger fsm HOTFIX New release: Current version 2.4.2 Changelog (2.4.1 & 2.4.2) Added None to Task Garrison Exit Triggers (option prevents units from breaking garrison) Added Increased Flare/Illumination usage on Contact State Fixed Key Signature issues on Dedicated Server Fixed AI getting stuck in Garrison State* Fixed AI getting stuck in Fleeing mode Fixed vehicle AI would sometimes spam share Information Removed Investigation path from vehicle FSM (was unused) *Thanks to @Coulfor finding and fixing the issue. From the team diwako / joko / nkenny
  9. @coul That's a real bug! Must have been removed in one of the revisions. It isn't critical as I believe FSMs will time out automatically, but I will look into it further. -k
  10. @madrussian Next version will feature an internal restructure. Which is exactly where I would want to expand on the features you are interested in! -k
  11. LAMBS Danger.fsm New Release: Current version 2.4.0 Requires CBA_A3 3.15.0 or later Changelog Added Port all Strings over to Stringtables so that they can get Localized Added Vanilla EventHandler wrapper for all current Events Added Nearby friendly fire check for Suppression with configurable setting Added Nearby friendly fire check for vehicle suppression and assault functions Added Maximum Reveal value setting Added CBA Version dependency Added Player only setting for Task Creep/Hunt/Rush (these modules can now hunt enemy AI) Added SortByHeight, Teleport and Exit Condition setting to TaskGarrison Added Teleport setting to TaskCamp Added Remote compatibility to Task Assault/CQB/Camp/Creep/Garrison/Hunt/Patrol/Reset/Rush Zeus and Editor Modules Added Rewrite of Task Artillery to make it multiplayer compatible Added Various performance optimizations to danger FSM Added Immediate Action state Added fnc_immediateAction with smarter movement routines to avoiding fire Added fnc_indoor to only recognize buildings Added Units with ACE3 medical AI enabled will exit FSM Added Tweaks to fine-adjust suppression position Added Improvements to re-manning static weapons Added fnc_leaderAssault, fnc_leaderFlank, fnc_leaderSuppress, and fnc_leaderGarrison* Added fnc_leaderStaticDeploy, fnc_leaderStaticPack and fnc_leaderStaticFind (units will now dynamically deploy static weapons and more reliably man nearby ones) Added fnc_doSmoke, fnc_doUGL (functions to throw smoke and shoot flares respectively) Added FSM fix to prevent units from reacting to allied weapon fire Added FSM reaction state will now only trigger on dangerous events** Added FSM better support for ACE3 medical AI by delaying healing when unit is threatened by nearby gunfire or forced movement Added FSM faster and more aggressive movement when 'forceMove' variable is enabled Added units which call artillery will now attempt to use binoculars and stay in position to direct fire Added settings to disable dynamic weapon deployment and remanning Changed All number edit boxes in ZEUS Modules to sliders Changed Module Artillery Dropdown to Side Selector Changed Make use of CBA_fnc_getPos from CBA 3.15.0 update Changed Moved various settings such as speed and search range from FSM to function for easier editing Changed Increased threshold for doing suppression while suppressed from 0.5 to 0.75 Changed FSM priorities for bulletClose increased from 3 to 6 Changed fnc_fsmExitVariables to use fnc_isAlive Changed Default settings for CQB range from 50 to 60 Changed Radio minimum range settings from 200 to 20 based on user input Changed Gestures used to indicate initial reaction (from 'cease fire' to 'freeze') Changed fnc_hideInside, reduced range units without cover would retreat from 45-110m to 10-55m Changed Debug information variables are now global if `Debug Functions` setting is enabled Fixed An issue with ShareInformation Fixed That Task Creep/Rush didn't use user set Cycle Times Fixed Error in fnc_vehicleSuppress (vehicles would fail to engage) Fixed Assaulting units from occasionally looking into the ceiling Fixed Global variable in suppression part of FSM (timeout) Fixed Increased APC dismount range from 180 to 250 meters Fixed Tightened range which units check for CQB buildings in CQB mode (No need to check out to 250 meters) Fixed fnc_react - reaction state stances were reversed Fixed fnc_suppress - override setting would also override intelligent target adjustment based on visibility Fixed fnc_zoneMarker - marker is now created local only Fixed FSM issues with doWatch and doLook Fixed FSM leader state Contact! Now uses distinct gesture and collects troops better Fixed FSM improved performance, moved more code to functions, and clarified priorities Fixed move command in fnc_leaderFlank would override the current waypoint Fixed Flying Waypoint in TaskGarrison Fixed A possible issue with group counts overflowing max group limit with some taskX Modules/Waypoints Removed fnc_leaderManoevure replaced by fnc_leaderFlank Group Tactics A big addition in this release is the introduction of a more extensive set of group level actions. These are called when the AI assesses that enemies are holding in garrisoned buildings or in otherwise weak tactical positions. The unit can respond in four ways: Flanking, suppressing, assaulting, or attempting to garrison its own or enemy building. The exact tactic being employed depends on the unit's own combat mode, available cover and distance to target. These new states replace the more limited fnc_leaderManoevure. Reaction state The second major overhaul is how the AI will enter the reaction state: Units that expect enemy contact are less likely to flinch. By default they will now only enter a reaction state when the unit is hit, unit spots a new enemy, nearby explosion or bullet impact, seeing unit from their own group killed, hearing another unit being hit, or bullet whizzing by. Units set to FULL speed mode or STEALTH behaviour will not trigger reaction and hiding responses. Special thanks The team would like to extend thanks to @BadGuy for help with adding User Interface elements, @R3vo for the German translations and @madrussian for spotting an error with waypoints being deleted. Discord Got questions, suggestions or other feedback? Come hang with the cool kids on our Discord. From the team: diwako / joko / nkenny --- STEAM Workshop --- GitHub --- Discord
  12. @Carlos Leung No configuration necessary. Mod runs automatically on all units. Even modded ones, provided they inherit from vanilla units. -k
  13. @Disgusting_Man I'll look into it. We have a version we use in nopryl.no that I could make public. @tyreyalv I keep my skill settings at the default. As I have investigated elsewhere, I find the biggest difference being the weapon carried-- particularly when mods are compared to each other. On our server we run custom settings, but closely linked to 'veteran' or 'expert' settings. In the end it is a matter of preference. A cross-section of the deadliness of gameplay that you or your community want to have. Arma3 settings are unfrotuantely rather opaque in this regard, so there is little other option than experimenting youself or trying one of the mods that specialise just in that regard. 🙂 -k
  14. Realised half-way through this video that I didn't have my headset on. Which in turn messed with the sound quite a bit. Initially I had intended to remake it, but didn't really have the time for it. Take it for what it is. An early development video showcasing the new group manoeuvre system being introduced in version 2.4 Oh, and errors in suppression (i.e., friendly fire have since been fixed) -k
  15. @LSValmont Nothing fancy. In our case the move just gave the squad extra impetus to keep on target. Based on our new tactical manoeuvres , substituting with doMove, as suggested, was sufficient. -k