Home Creators Posts Import Register Favorites Logout

Videos

  • AGLS v2.0 - Reload Video.mp4
  • AGLS v2.0 - New Climbing Presentation.mp4

Downloads

Content

Adventure Game Locomotion System (AGLS) v2.0 is an extensive framework designed to provide a solid foundation for creating full-fledged single-player third-person games. The project's content was inspired by game series such as Uncharted and The Last of Us, while also introducing many unique mechanics of its own.

  • ⚙️The project is based on C++ (6 C++ plugins), but modifying the source code is not required — changes can be made entirely through Blueprints.

  • Not all animations are included in the project (list), but they are not required for the project to function.

  • AGLS was designed specifically for Windows🪟. Running the project directly on other operating systems has not been officially tested. However, this does not rule out the possibility of using it on systems such as Linux, although doing so may require additional and more advanced setup steps. The 𝐀𝐆𝐋𝐒 v2.0.1 UE5.8 version has been adjusted to improve compatibility with 𝙇𝙡𝙉𝙐𝙓-based systems 🖥️.

  • The entire system is NOT replicated.

  • 🏃‍♂️All animations (~ 2.7k files) rigged to UE4 Mannequin, but project include real-time retargeting to UE5 Manny (compatible with Metahuman skeleton structure)

  • Size to download ~2.6GB zipped

  • ⚠️ NOTE: AGLS is a highly complex and extensive framework. It includes many features that extend the default systems available in the engine. Working with it efficiently and making modifications requires substantial experience with Unreal Engine.

Due to the overall complexity and scale of the system, it is important to keep in mind that the number of potential bugs may increase. Nevertheless, I make every effort to identify and eliminate such issues, and whenever bugs are discovered, I provide updated files with the necessary fixes.

Packaged Project DEMO for Windows

Patch Notes from 1.2 to 1.7 (Patreon Posts)

The link to download the project files is at the end of the post content

Informations about animations:

Not all animations are included in the project. 

Animations such as Stealth Finishers or some other finishers come from the UE Marketplace. You don't need to own these animation packs to open the project in the editor. The main consequence of missing animations will simply be poorly looking sequences like attack or some interactions.

⚠️ Note: There have been significant changes regarding animations not included in the project. As of version v1.8, animations from the "Brutal Finishers - Hand and Knife" pack are no longer as essential, and MeleeCombat now uses only 6 animation assets during game from this pack. Despite this, the project still contains additional assets for these animation sequences, as they are planned to be used in future versions. For "Stealth Finishers - Knife and Hand" and "Ultimate Traversal Anims", the situation remains largely the same as in previous versions of the project.

Here’s a list of animation packs not included in the project (not all sequences from the packs are used in the project):

A full list of not included animations sequences used in the project

If you have the necessary additional components, the implementation into AGLS is very simple. You just need to export the required animation sequences to .FBX files. Then, assign the appropriate file names and reimport them into AGLS.

✅ Without these animations, the project will run normally.

After a long period of development, I have finally managed to complete the first release of AGLS v2.0. I put a great deal of time into this version, and the final number of changes turned out to be quite significant (A large part concerns technical issues). With v2.0, I wanted to focus as much as possible on making the project more "production ready." I tried to improve many mechanics, animations, and systems, while also creating a more organized environment so that working with AGLS would be clearer and easier.

More than two years have passed since version 1.0, which marked the transition from ALSv4 locomotion to Motion Matching. That is a very long time to spend on a single project. During this period, I have continuously developed my Game Dev skills, including my knowledge of Unreal Engine, C++, animation, and modeling.

Because of that, I would like to thanks everyone who has supported my work. Some of you have been doing so for years, and without your support, my journey with Unreal Engine would most likely have ended a long time ago.

I will try to explain the current state of AGLS v2.0, provide an overview of the update, describe my future plans for the project, and cover other important information.

First of all, the release of v2.0 does not mean the definitive end of my support for this project. I think that versions such as 2.0.1 or 2.0.2 should still appear later this year.

The main reason for this is that AGLS is a very complex project environment, which naturally makes it more susceptible to various bugs that I may not have managed to catch. Even though I have tested the project myself, I do not think I was able to cover every possible scenario that a player might encounter. Because of this, I will try to keep track of reported issues and fix them. If enough of them accumulate, I will most likely release smaller file updates. I also do not rule out adding some smaller improvements along the way, such as changes to HoldHostage, since I skipped that gameplay element in v2.0.0.

🔷Main changes and information regarding version 2.0.0:

🔴 Updated Guns systems 🔴

v2.0 includes major changes related to equipment and weapons. Most importantly, this applies to the new approach to pistols and rifles. Starting from this version, weapon models are declared as Data Assets, while the DataTable is now used only for cataloging and indexing them. The DataAsset contains more configuration parameters and appears to be much easier to read and manage.

The weapon models themselves—including their skeletal structures and geometry—have undergone numerous changes to better support the AnimInstances assigned to the props.

As for the firearm-related elements, I improved many animations, mainly those related to OverlayStates, and added a large library of completely new sequences, including Recoils, Reload with Drop Mags, Reload without Drop, Switching Weapon Models, Filling Magazines with Individual Bullets, and more. The weapon models themselves now include around 70 unique animations.

Putting it all together, I think I’ve managed to implement an interesting weapon system that, with the right configuration, can realistically reflect reality and add an engaging layer of survival immersion.

Of course, it is important to keep in mind that I used certain simplifications in some areas, and the entire system was created by a single person without extensive professional animation experience. I also did not focus heavily on visual effects such as particle effects or CameraShake. I do not have much experience with Niagara, so I decided to leave that part to the user of the project.

The system now mainly supports two different approaches related to ammunition, magazines, and item drops. By default, the ALS_GameMode_SP class contains parameters that affect the gameplay mode:

The most important values are GunsMagazinesArStoredInPlayerChar and CanUseSurvivalModeGuns. By default, both are set to true, which causes reloading and looting behavior to work somewhat differently than in previous versions of the project.

Most importantly, with this configuration, the player does not drop the magazine during reloading. Instead, it is stored in the inventory. By default, the player can carry up to 3 magazines per rifle or pistol instanice (excluding shotguns and revolvers).

During reloading, the game selects the magazine with the highest amount of ammunition. Individual magazines can also be picked up. If there is no free inventory space available, the picked-up magazine replaces one already stored in the player’s inventory. The system selects the magazine with the lowest amount of ammunition for replacement.

To perform a standard reload, press the (R) key. Holding the key instead will attempt to use the 'Fill Mag With Ammo' ability.

I should also mention the HUD interface and other Widgets. I did not focus heavily on these aspects, so the overall presentation may not always be very clear. In addition, when displaying information about a particular item, the system has to take a large amount of data into account. By default, the Widgets display information using Rich Text, which allows for more advanced text formatting as well as the ability to insert images.

When overlay menu opened:

Another important change related to rifles is the ability to carry more than one instance. AGLS currently allows up to 3 rifles, although I would personally recommend limiting this to a maximum of 2 instances.

From a technical perspective, the new weapon system is based on a completely new class. Previously, elements such as shooting using gun were implemented directly inside ALS_Character_BP. From now on, however, this functionality is handled through the AGLS_PlayerGunsFunctionalityExtend instance.

AGLS_PlayerGunsFunctionalityExtend is also responsible for elements such as:

  • Correctly attaching weapon instances

  • Updating Recoil and Aiming Instability

  • Generating hit trajectories for sniper rifles

There is also a function library available that allows you to control and read important parameters related to the Guns System:

Another important new asset worth mentioning is 'AGLS_BulletsTypes'. It is responsible for declaring the ammunition types that weapon models can use.

A major new addition is also an entirely new firearm type: the revolver. By default, only one revolver declaration is available, named RSH-12. It is one of the more recognizable conceptual revolver designs and can also be seen, for example, in Resident Evil Requiem.

By default, like most models in AGLS, the revolver was created as a low-poly model. However, a much higher-resolution model is also available as an example.

Model creator: "RSH-12 revolver" (https://skfb.ly/oHI9v) by MCTav1sh. Rig by JakubW

To use it, simply open the 'PistolDefinition_RSH_12' asset and set SkeletalMesh to Revolver_RSH_12_HighPoly.

🟠 Heavy update for props like Bow, Knife, Axe 🟠

AGLS v2.0 also significantly alters elements such as holding a bow, knife, or axe. All animations associated with these items have been refreshed, and the models themselves have undergone major changes for certain variants.

🟡 Significant changes related to the 'BP_DynamicClimbingComponent_v2' component 🟡

The Climbing System has undergone many changes. Whether some of these changes are improvements or drawbacks may be highly subjective, so the option to return to the default configuration originating from the IWALS project has been preserved. The most significant changes are the ability to choose the algorithm used to detect so-called ledges, as well as the transition sequence into the ledge-hanging state, which is now based on Motion Matching.

This is what the current default Climbing System configuration looks like:

The main change related to the new LedgeDetection algorithm is that the Climbing Component now includes a parameter that determines which algorithm should be used. There are three available types: Default, ComplexTraces, and Astra. Descriptions of each type can be found in the variable tooltip.

Choosing the appropriate algorithm, along with its configuration parameters, can be important for performance. The default ComplexTracesMode expands the area in which a ledge can be detected. In addition, it accepts collision cases where the available space for the capsule is limited, which allows it to handle Complex Collision more effectively, including on Nanite geometry.

By default, a new function is also used that performs significantly better when searching for an edge that can be used to transition into Climbing Ledge. Its use is optional as well.

Some smaller climbing-related changes include:

  • Improved Beam Swinging, including transition animations into the hanging state, as well as the use of BlendStack for better animation blending. Importantly, by default, the DetermineWallPosition function does not analyze instances of BP_BeamForSwinging actors. To change this behavior, place a BP_ModifyClimbingParamsVolume in the level using the recommended configuration:

  • The approach used to determine HandsIK positions has also been changed. Previously, the FindingLedge algorithm was additionally executed for this purpose, which unnecessarily affected system performance

  • Improved behavior on moving geometry, including additional conditions that check ledge inclination, the velocity of the object the player is holding onto, and other related parameters

  • Improved pistol aiming control while climbing. The player can now lean over an edge if the system detects that there is enough space to do so

  • Added active physics simulation for the legs during FreeHanging (experimental feature)

  • Changed the Root bone position for all climbing-related animations. Previously, all of these animations had an incorrect Pelvis position relative to the Root bone. Because of this, ModifyBone had to be used to correct the offset

🟢 Ability to load presets associated with the player's default inventory and equipment. 🟢

A new class named BP_PlayerCharacterConfigurator now allows you to create presets for the player character’s default configuration. By placing an instance of this class in the level and selecting a preset, you can control whether the player starts with full equipment, has no weapons, carries a backpack, how many weapon instances can be carried, how many magazines are available in the inventory, and other related settings.

Actor instances can be retrieved from the current scene, or the system can create new ones and assign them to the player.

List of smaller changes introduced in the project:

  • Improved blending between OverlayState layers and BasePoses, as well and transitions between different OverlayLayer instances, for example ALS_OverlayState_Pistol_2H -> ALS_OverlayState_Default, using InertialBlending.

  • Improved OverlayPoses blending when changing Stance, such as Standing, Crouching, or Crawling.

  • Converted many functions in classes located in the States folder to ThreadSafe.

  • Improved animation blending when activating ThrowableObjectHold layer. This mainly concerns cases where the character was unequip item such as a rifle. Previously, the ArmR layering was not passing through correctly.

  • Improved blending between different overlays while the flashlight-holding overlay is active. This is a fairly complex case, but I think the final result is significantly better than in previous versions of the project.

  • Added additional Equip and UnEquip animations for KnifeOverlay.

  • Improved the actual grenade flight trajectory so that it matches the generated prediction more accurately.

  • Reworked TorchOverlay. This system has been significantly simplified while still preserving the ability to light the torch.

  • Made a small change to HumanAI Dying Sequences. Fixed incorrect animation selection when the AI was in the Crouching state.

  • Slightly changed the item drop system when HumanAI dies. This logic is connected to the new Weapons System.

  • Added Namespaces to some systems.

  • Added and standardized thumbnails for many assets available in the project.

  • Added an ⚠️ experimental optimization approach for the Camera System. When this functionality is enabled, the AnimGraph responsible for controlling the camera position can dynamically adjust its TickRate depending on whether any state has changed.

  • Optimized active SkeletalMesh instances available in the level. From now on, elements such as BP_I_OpenableCabinet, BP_I_OpenableDoors, BP_I_OpenableDrawers, and BP_PickablePropItem process their skeletons only when it is actually necessary. These instances can also switch from rendering as SkeletalMesh to rendering as StaticMesh.

AGLS ᵥ2.0.1 UE5.7/5.8 Main changes log:

🔶If you are already using v2.0.0 and have been working with the project for some time, you can find a file in the attachments section that contains a list of all assets modified in v2.0.1 compared to v2.0.0. In that case, you can choose to overwrite only the necessary assets, or even just individual Blueprint functions.

  • 🔸Improved the behavior of props held in the character’s hands during actions such as Mantle, Ragdoll, and Fall Damage. Previously, some items could become invisible or have an incorrect position relative to the active OverlayState. [Discord Bug Thread 1] [Discord Bug Thread 2]

  • Improved the behavior of ALS_Ability_PickAmmoForGun when the action is triggered while crouching. New animation sequences were added for this purpose. [Discord Bug Thread]

  • Slightly adjusted the impulse value applied to Physics Bodies during ragdoll. Despite this, situations where the character suddenly bounces away or becomes stuck in collision may still occur. [Discord Bug Thread]

  • Improved OverlayLayer behavior while a Predictable Jump Montage is active. [DiscordBugThread]

  • Generated correct FootsSpeed curves for several animations, including CoveringWalk, Landing, and RunStops. Previously, incorrect values could cause improper FootIK behavior.

  • Corrected the display of information related to owned weapons while the Overlay Menu is open. Before these changes, weapon data shown during reloading could refer to a different weapon model instead of the currently active instance. [DiscordBugThread]

  • Made a small correction related to the 'RestartLevelOnDeath?' variable available in ALS_AnimManBP.

  • Fixed an issue with incorrect MovementMode values during actions such as TraversalAction and Mantle. Previously, if Mantle was still active and the player triggered a Traversal Action, it could result in an incorrect MovementMode being set in CharacterMovementComponent. [DiscordBugThread]

  • Fixed the ability to activate the ladder climbing system. Previously, the issue was caused by ClimbingLedge detecting the ladder as a regular ledge instead of ignoring instances of the BP_Ladder_generator_V2 class. These changes apply to C++. [DiscordBugThread]

  • Improved transitions into LedgeHold during rapid switching between Climbing and Falling. Traversal actions are now blocked in certain cases when the ledge position is very close to the player. [DiscordBugThread]

  • 🔸Significantly reworked the SwingingOnBeam element related to the Climbing System. The overall behavior should now feel much more dynamic.

  • Improved the transition between Swimming and HoldingLedge.

  • Added support for more player behavior scenarios during ALS_Abilty_SwitchPistolInstance. Previously, MontagePlayer did not react to the Interrupt output, which could cause the action to never be recognized as completed.

  • Improved OverlayStates behavior while swimming, including the handling of active overlays and the items displayed in WheeledOverlayMenu. Previously, in some cases, the player could still hold a rifle while swimming.

  • ALS_Ability_NarrowLedgeWalk now supports interruption of the ability instance, for example due to Ragdoll or Mantle.

  • Improved some animations related to the Mossberg-590 model, mainly fixing issues with the player character’s position during firing. The problem was especially noticeable in CoveringMode.

  • Slightly adjusted the behavior of ALS_CLF_GetUp_Front and ALS_CLF_GetUp_Back.

  • ❗Fixed a critical bug in AGLS_HumanAI_StatesCore. The issue caused serious errors when selecting the correct State while HumanAI transitioned from LookingEnemy to AgressiveMode. [DiscordBugThread01] [DiscordBugThread02]

  • Added an additional animation for the Bow Overlay, ALS_Props_RecurveBow_Sheath_Crouch, to improve the behavior when putting away an arrow. [DiscordBugThread]

  • 🔸Reworked the animation system related to the HoldingHostageSystem. The overall result should now look significantly more consistent thanks to new animations and additional IK elements.

  • ⚠️ Added two new Anim Curves to ALS_Mannequin_Skeleton for better control of the Control Rig used by CrawlingLocomotion.

These changes should improve OverlayLayer behavior while crawling, especially when equipping or holstering items. However, it is important to keep in mind that many poorly looking animations during crawling are mainly the result of missing dedicated animation sequences, which may need to be implemented separately. It is also worth noting that these changes modified curve values in individual animation assets and in several AnimInstance assets.
  • ⚠️ Made very important changes to the C++ code. I introduced key fixes related to compatibility issues with other operating systems. This may significantly simplify running the project in environments such as Linux. These fixes mainly apply to AGLS under Unreal Engine 5.8.

  • ❌ Deleted some old animations from:
    /Game/AdvancedLocomotionV4/CharacterAssets/Animations/Interaction/Picking_Item

  • Made changes to Shoot Trace that allow the shot trace to pass through the water surface up to a certain distance.
    ⚠️ NOTE: This required changes to the collision settings in Project Settings.

⎹ 𝔻𝕆𝕎ℕ𝕃𝕆𝔸𝔻 𝕃𝕀ℕ𝕂𝕊 ⎸

▶ DOWNLOAD PROJECT FILES (v2.0.1, UE5.7) ◀

▶ DOWNLOAD PROJECT FILES (v2.0.1, UE5.8) ◀

✅ 05.10.2026 - A huge update related to Retargeting UE5 Manny system . Now it should now work much better. I also introduced several additional changes related to retargeting. By default, the AnimInstance uses only a single IK Retargeter asset. However, I added an additional mode that can use multiple retargeting assets, selected depending on values from the Player Character. This new approach is more precise because each IK Retargeter can be configured for specific situations, but it may also have a higher performance cost. For that reason, it is not enabled by default. You can test it by executing the following command:AGLS.Retargeting.UseExperimentalRigAssets 1Alternatively, you can open Manny_BetterRetarget_AnimInst and set ForceUseExperimentalRetargeting to true. These changes should already be available for download.

⚠️ OUTDATED FILES ⚠️

▶ DOWNLOAD PROJECT FILES (v2.0.0, UE5.7) ◀

I would also like to mention an important point to keep in mind when extracting the project files. Normally, little attention is paid to the folder in which a project is stored. However, asset paths are subject to length limitations. AGLS contains a large number of subfolders and assets with relatively long names. As a result, storing the project in a directory with a very long path may cause issues during packaging. For example, in my case, the project files are stored in the ':\Unreal Projects\UE5.7' directory. If it were something like ':\Epic Games\Unreal Engine 5.7\Projects\AdventureGameLocomotion System\', you might get an error message about the asset path exceeding the maximum number of characters.✳️ Minor Zombies-related changes published on 02.10.2026. Fixed/Adjusted: ① Physics Asset adjustments | ② FootsIK correction during crawling | ③ The LOD state determination function now also takes FOV into account

⚠️ OUTDATED FILES ⚠️

▶ DOWNLOAD PROJECT FILES (v2.0.0, UE5.8) ◀

▶️ AGLS Tutorials Playlist ◀️

This tutorial playlist might be outdated. I will try to prepare a brand-new, up-to-date playlist for version 2.0.

Can it be used for commercial purposes?
Yes, but there are certain limitations. Most importantly, distributing project files (in the same way I provide them) is strictly prohibited. For commercial purposes, distribution should only be in the form of a packaged project (preferably in shipping configuration). This means that publication should be done in a format that does not allow easy extraction of AGLS project content. In short, the permitted format would be a compiled program, such as a .exe file for Windows.

It is worth reading the full license of use. You can find it at the link (PDF) or in the attachments under the post.

📄 it is worth taking a look at the documents in the attachments 📄

Information about project packaging.
In this version of the project, I left a few folders related to the packaging process I performed on my own computer — these include the 'Binaries' and 'Intermediate' directories for project and plugins folders. If any errors occur during packaging, it’s worth considering completely deleting these directories from the project files. Additionally, in such cases, it’s recommended to use the 'Full Rebuild' option.

Some important Discord threads:

I would also like to mention a small request. Namely, it is about private messages sent on Patreon. I would ask that this method of communication be limited, due to its large constraints. If your question is about the project, please send it on the Discord server, or in the comments under the Patreon post. In other cases, I would suggest an email or possibly via a Patreon mailbox. Please note that due to the large number of messages, I am unable to reply to all of them. Most often I answer questions asked on the Discord server, followed by emails, comments under the Patreon post, and Patreon private messages. Thank you for your understanding.

Files

Comments

Jakub W

Hi. Regarding the files for Unreal Engine 5.8, I mentioned this in the body of the post. It is worth checking out that announcement if anyone is expecting files for that version of the engine.

Andy Pang

Hi Jakub, I know this might have been answered in the past already, but I am wondering how to set up the doors so that keys are required to open them. I saw a few exposed variables called RequireKey and KeyTag on the BP_I_OpenableDoor already, but when I dug a bit deeper it seems like none of the variables are checked against during the interaction. I also didn't find an accompanying BP_Key or anything that is required to interact with the door. Is that up to us to implement or am I missing something in the project files entirely?

StormrsZone 2.0

look up resident techworks on youtube, he just recently did a tutorial on doors and using keys to open them

geim an

live laugh love jakub W work

Martin Hanuš

Hello! how to safely upgrade project 1.9.2 to new version 2 of AGLS? thanks!

geim an

hey jakub after playing the new version i dont know if it only happened on my end but enemy ai would spawn with no weapons and couldnt be killed and it would give me this error Blueprint Runtime Error: "Accessed None trying to read (real) property StatusMesh in AGLS_HumanAI_CharacterBP_C". Node: Set World Rotation Graph: UpdateStatusMeshRotation Function: Update Status Mesh Rotation Blueprint: AGLS_HumanAI_CharacterBP

Martin Hanuš

yes.. I also get error :( enemies are also immortal now, only zombies works

Martin Hanuš

also companion cannot climb now..it works well in previous version and also in demo version :(

Nikkoid

I just went through the extensive post about AGLS 2.0.0. Data Assets are definitely the way to go, and a lot of things are getting much better. I’d like to share my thoughts on the future of the project: - Consolidate and debug as much as possible. At some point, it might be worth setting up a proper bug-reporting system so the community can report issues and help you track them efficiently. - Improve modularity. Make sure we can modify or extend AGLS without touching the original code. Otherwise, upgrading to future versions can become a nightmare. - Keep health and damage systems clearly separated. This is a critical part of almost every game and is very often customized or completely reworked. It should therefore be easy to replace or modify without having to dig through the rest of the framework. - The same applies to impacts, footsteps, muzzle flashes, etc. These are almost always customized from project to project. They should be easy to modify or replace without having to reprogram everything after every AGLS update. - Avoid declaring Blueprints in C++ unless there is a real reason to do so. It adds an unnecessary layer of complexity. The issues with 5.8 are a good example: Voyager, TPS Kit, AAMS v2, Ultimate Adventure, etc. were compatible out of the box, while AGLS required additional work. And in most cases, declaring something in C++ doesn't actually make the Blueprint code execute faster. C++ should primarily be used where it provides a real performance advantage or for functionality that cannot reasonably be done in Blueprints. - Try to get replication fully implemented. This would open up a lot of possibilities for multiplayer projects. - Move the whole project toward a clean, self-contained structure. Ideally, everything should eventually live in a single AGLS folder, completely separated from the old ALS structure. This would make the framework much easier to maintain, customize, and update. Good luck, and please don't give up on this project. You have already achieved an excellent result, and that's something that doesn't happen many times in a lifetime!

Sam Yazdi

love the project, i saw the video of you showing how to change the movement speed, but i cant find the datatable, is it gone, is it changed? could you please tell me how to do change it?

zeroDay

I guess i have to pause development 5 days

Jakub W

Hi. It depends on several factors. The main one is what kind of changes you've made to the current version of AGLS you're using. If you've modified any of the default Blueprint assets, things become a bit more complicated if you want to preserve those changes after updating. However, if you've added external assets such as models, textures, or materials, and you keep them outside the default AGLS project folders, then the update should not be particularly problematic. In general, the simplest approach is to delete the folders inside Content and Plugins directly through Windows File Explorer, and then copy the corresponding folders from v2.0 into the project. The Config folder is also important, although in this case the only file that has changed compared to v1.9.2 is DefaultGameplayTags.

Jakub W

Hi. Unfortunately, AGLS does not include the functionality you mentioned, so this kind of logic would need to be implemented by yourself. As the user StormrsZone 2.0 mentioned on YouTube, Resident Techworks has shown what changes can be made in order to add support for using keys.

Jakub W

Thanks for letting me know, and sorry about the issues. When I removed the old parameters from the Rifles structure, I was convinced that there were no references to them left anywhere in the project. However, for some reason Unreal Engine did not show any compilation errors. Interestingly, it even managed to package the project despite errors being present in the AGLS_HumanAI_CharacterLogicBase class, so I really had no way of noticing that something was wrong. Only after compressing and then extracting the project files did the engine perform a Blueprint validation, and that was when the errors were finally generated. A very strange issue. I've updated the files, so this should now be fixed.

Jakub W

Hi. When I removed the old parameters from the Rifles structure, I was convinced that there were no references to them left anywhere in the project. However, for some reason Unreal Engine did not show any compilation errors. Interestingly, it even managed to package the project despite errors being present in the AGLS_HumanAI_CharacterLogicBase class, so I really had no way of noticing that something was wrong. Only after compressing and then extracting the project files did the engine perform a Blueprint validation, and that was when the errors were finally generated. A very strange issue. I've updated the files, so this should now be fixed.

Thisisme Mario1

Hello Jakub, I'm super sad to see that 2.0 is your latest update as I would have love to see this project evolved even further. Each update was a blast and the highlight of my day :) THANK YOU so much for your hard work and for this fantastic base to build upon. But I'm also eager to see what you're gonna build next ;) Regarding UE 5.8, I read the post but I'm still not sure I got it. AI enemies and state tree are working now ? Is AGLS entierly compatible with UE 5.8 ? If not can I use the same files on 5.7 ? I'm mostly interested in 5.8 for the meta human mocap with iPhone. Thank you Jakub for this project. Cheers

Andy Pang

Thanks for sharing the resource!

geim an

no worries man its still aa good update just need some small bugs to fix

Martin Hanuš

understand! btw new version finally works! thanks!

TryHarder

Hi, what is the issue with 5.8? Aside the usual few issues and a ray tracing buffer issue in JakubCablePhysic.cpp it built fine (5.8.3 source) all seems to work ok aside the AI doesnt attack. So is that it? Do I just need to spend another hour fixing the AI State Tree again? Or is there something else.

Martin Hanuš

I dont know if its just me? but in this last version I cannot pickup backpack? looks like it doesnt work in demo also. ? maybe blueprint was replaced but in the map is older model without functional blueprint? I guess?

Shaune Greenidge

Hi, I also have the same issue. The issue also happened when i downloaded v1.92. @JakubW any ideas for a fix? Thanks in advance.

Brandon Elder

I see you fixed the AI gun issues with an updated project file. But one thing still stands, you can’t attack enemies still. You can kill them with a gun, but you can’t attack them with a melee weapon

Martin Hanuš

at least at v1.92 you can select your ALS_AnimMan_CharacterBP find parameter backpackActor and select BP_backpack and you can start with backpack already.. but in v2 this doesnt work

Abdullah Razeen

same, and the xray part also doesn't work, yet slow-mo works perfectly.

Jakub W

Hi. Generally, yes. The way CharacterMovement parameters are controlled was redesigned some time ago. Since a certain version, movement is handled by the MovementParamsControl_Player component, so the steps shown in the video tutorial are no longer up to date. That said, the changes are still easy to make. In the following directory: /Game/AdvancedLocomotionV4/Blueprints/MovementControl/PlayerPresets you'll find Data Assets containing the movement configuration. By default, the player uses MovementPreset_Relaxed. After opening this asset, you'll see a structure similar to the one previously used in the Data Tables, so I think the rest should be fairly straightforward to understand. I'm aware that the current tutorial playlist is outdated, so I'll be working on creating a new one that is up to date for v2.0. Best regards.

Sam Yazdi

Hi. Ty for replying, yesterday i was just scrolling thru my character and saw the button for it lol. Appreciate the reply and helpfullness!

Galen

Scan works. Select BP_ScanArea in the Outliner. In the Details panel, find Input > Auto Receive Input. Set to Player 0.

Jakub W

Hi. I checked the issue related to the Backpack, and it seems to work the same way as in previous versions of the project. The ability to pick up the backpack should work correctly both in the project itself and in the demo. The problem may be caused by the fact that BP_Backpack has slightly different interaction conditions compared to other elements. The camera needs to be facing toward the backpack in order for the interaction to work. In this video, I showed how it works by default: https://drive.google.com/file/d/1eS4xSbQFFn4tIbYQmc4Kw5kNYJEqiEd3/view?usp=sharing

Jakub W

Hi. Unfortunately, I don't know exactly when you downloaded the project files, but I believe the mechanics you mentioned should be working correctly in the current version. Initially, there were some compilation errors in several Blueprint files, mainly related to HumanAI and the Shooting System. I would recommend downloading the latest project files to make sure you're working with the most up-to-date version.

Jakub W

Hi. Thank you for supporting my work. The release of v2.0 does not mean the definitive end of AGLS. There should still be smaller updates in the future, mainly focused on bug fixes and possibly some minor improvements. As for a future project, nothing has been decided yet. I need to take many factors into account and consider what direction I want to take next, especially since Unreal Engine itself is also evolving quite rapidly. Regarding your questions: 1) Yes, they are already working. The issue was actually quite difficult to predict because, for some reason, the engine did not perform Blueprint Validation when I removed several parameters from the structure declaration, and it turned out that HumanAI still had references to them. 2) Yes, it will. In this case, I don't intend to provide only the plugin files, but the complete project files for UE5.8. Best regards.

Brandon Elder

Sadly, I did a fresh install and still does not work. Only killing that works is with a weapon. No melee animation works

Martin Hanuš (edited)

Comment edits

2026-09-29 16:00 strange thing is that no indication will appear as on every other object, for example "presse E to pickup backpack" someone who dont know template also dont know its pickable.. it works when i point camera down.. but as i said..there is no indication... like doors etc. no changable radius where we can pick it. Like other objects.
2026-09-28 20:27 strange thing is that no indication will appear as on every other object, for example "press E to pickup backpack" someone who dont know template also dont know its pickable.. it works when i point camera down.. but as i said..there is no indication... like doors etc. no changable radius where we can pick it. Like other objects.

strange thing is that no indication will appear as on every other object, for example "press E to pickup backpack" someone who dont know template also dont know its pickable.. it works when i point camera down.. but as i said..there is no indication... like doors etc. no changable radius where we can pick it. Like other objects.

Jakub W

Hmm, that is really strange. To be sure, I ran a test by downloading the files from Google Drive and then checking for any issues with Melee Combat. Its works fine for me. Is there any reaction when you press 'V'? Does the component at least attempt to async load the animation data into memory? I’m also attaching a video demonstrating some simple diagnostics for the Melee Combat Component. It would be worth doing this so I can better understand at which stage of the code the problem might lie: https://drive.google.com/file/d/1ey7_ZRQVPDF7Kzd3AkLqqUm7mB5XMJQB/view?usp=sharing

Brandon Elder

Got it working! Sorry, I did not know you changed the melee input to "V". Before, it was always left mouse button

Re-top-o Monkey

Hey Jakob, I opened the default level and go into play mode the character has really bad lag. I opened the zombie level and it also has really bad lag. I have a powerful work station so I'm pretty sure its not the computer.. what do you think is causing this..?

Martin Hanuš

what helps me to not play in selected viewport but standalone game. For generating zombies.. there is shortcut.. note is somewhere in level on the wall ...its "L"... also problem is that project need some preloader thats the reason why its lagging I guess.. its loading all assets on the fly

Jakub W

I understand 😂. Since version 1.8, the keys are 'V' and 'C'. To avoid any confusion regarding other default key assignments, it is worth consulting the 'AGLS v2.0 Keyboard Inputs Binding' file.

Jakub W

Hi. These "bad lags" are most likely related to the Async Loading operations. In larger projects, proper memory management becomes much more important. AGLS launches relatively quickly in the editor because many assets are not loaded into memory at startup. Instead, they are loaded asynchronously when a specific part of the code actually requires them. This does not apply only to the Zombie-related systems, but to the overall project architecture. AGLS also loads the following elements asynchronously: • HumanAI structure - Character and AI Controller • Assets used by Zombie Characters • Ability classes for the Player Character, such as opening props • Overlay State Animation Layers • Motion Matching Databases - this solution is experimental. I discussed it in more detail in the description of version 1.9 • Several other classes and object instances This approach allows the engine to avoid creating unnecessary Hard References to classes that may never actually be used. For example, if SpawnActorFromClass had a Zombie class assigned directly as a HardRef, or if any Player Character asset contained something like CastToZombie, then the engine could end up loading all related assets into memory when the project starts. That is generally not the best approach. It is also worth noting that the AsyncLoad operation is significantly slower compared to packaged projects in the Shipping configuration. Loading times may also depend on hardware - for example, whether the project files are stored on an external drive or on an HDD, which usually has lower read speeds than an SSD. However, these factors are generally less important than the difference between loading assets from the editor and from a packaged build. If you want to avoid this behavior and force the engine to load the required assets when the project starts, you can simply create Hard References somewhere in the default level to one of the key classes, such as AGLS_ZombieCharacter_Base or AGLS_ZombieAI_Controller.

Martin Hanuš

Hello! I have another problem in this version 2. When I want to jump on ledge Unreal crash and it worked in previous version nicely. In your example level there is generated path..so now is it nescessary to build path on every ledge? this is crashlog from UE LoginId:cc7c1f814caa668a20b9be82cd51d43f EpicAccountId:0973e37edba14b15a55a8ff4a1ebeec8 Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000010 UnrealEditor_HelpfulFunctions!UCpp_DynamicClimbingComponent::FindSingleLedgePointUsingComplexTraces() [D:\Unreal Projects\UE5.7\AGLS_ProgramingCpp\Plugins\HelpfulFunctions\Source\HelpfulFunctions\Private\Cpp_DynamicClimbingComponent.cpp:1353] UnrealEditor_HelpfulFunctions!UCpp_DynamicClimbingComponent::TryCreateLedgeUsingComplexTracesMethod() [D:\Unreal Projects\UE5.7\AGLS_ProgramingCpp\Plugins\HelpfulFunctions\Source\HelpfulFunctions\Private\Cpp_DynamicClimbingComponent.cpp:2221] UnrealEditor_HelpfulFunctions!UCpp_DynamicClimbingComponent::TryCreateLedgeStructureC_Implementation() [D:\Unreal Projects\UE5.7\AGLS_ProgramingCpp\Plugins\HelpfulFunctions\Source\HelpfulFunctions\Private\Cpp_DynamicClimbingComponent.cpp:144] UnrealEditor_HelpfulFunctions!UCpp_DynamicClimbingComponent::DetermineWallPositionAndFindLedgeDuringTheFall_Implementation() [D:\Unreal Projects\UE5.7\AGLS_ProgramingCpp\Plugins\HelpfulFunctions\Source\HelpfulFunctions\Private\Cpp_DynamicClimbingComponent.cpp:2665] UnrealEditor_HelpfulFunctions!UCpp_DynamicClimbingComponent::execDetermineWallPositionAndFindLedgeDuringTheFall() [D:\Unreal Projects\UE5.7\AGLS_ProgramingCpp\Plugins\HelpfulFunctions\Intermediate\Build\Win64\UnrealEditor\Inc\HelpfulFunctions\UHT\Cpp_DynamicClimbingComponent.gen.cpp:2078] UnrealEditor_CoreUObject

Jakub W

Hi. I think I know what's going on. Is the problem caused by the fact that you're using 'Brush' geometry, and the crash only happens with those objects? This usually happens because that type of geometry can't return the correct class (StaticClass() == NULL). I should be able to fix this soon. This issue shouldn't occur if you set the LedgeSolver to 'Default' and disable the DetectWall function.

Jakub W

I believe I’ve fixed the errors in the C++ code. Running traces on BSP geometry should no longer cause the engine to crash. However, it is important to note that if you want the Climbing System to detect ledges on brush geometry, you must switch the LedgeSolver to 'Default'. I mentioned this in the post, so it is worth checking out that information.

Martin Hanuš

yes .. it was 'Brush' geometry..as you said, I missed this information O.o here is a lot of information everywhere

SKD007

I would be really cool if someone can create a full project using the new AnimGen asset with Replication.

Jakub W

Hi. Thanks for sharing your thoughts. I’ll try to respond to a few of the points you mentioned: 1) That sounds like a reasonable solution. There are probably some interesting services available for this kind of purpose. It would be worth looking into them and checking whether any of them would be suitable for an Unreal Engine project. 2) This is difficult to maintain in such a large and complex project. The fact is that, especially at the beginning, I didn’t pay much attention to things like ease of integration or modularity. The reason is fairly simple: AGLS has been the platform on which I learned Unreal Engine and programming. Because of that, many systems had to be modified or rebuilt once I gained more knowledge in a particular area. Today, I would approach many of those systems in a completely different way. That said, I think the separation of the different mechanics and the overall modularity are not in a particularly bad state. Also, AGLS v2.0 will most likely be the final update that significantly expands the project’s mechanics and systems. Future releases will probably be limited mostly to smaller updates focused on bug fixes. 3) The answer to this is partly covered by point 2. The health and damage system can be fairly difficult to understand for people who are not already familiar with the project. I hope that if I manage to record tutorials covering this topic, many of those elements will become much easier to understand. 4) In this area, I believe I’ve preserved the ability to modify these elements relatively easily. Adjusting weapon-related systems should now be significantly simpler compared to v1.9. 5) Declaring functions in C++ is generally not intended to provide a significant performance improvement. In most cases, the difference in performance will be negligible. The main reason is somewhat different: it is about avoiding unnecessary Hard References. When the core of a class is implemented in C++, external classes that reference it do not create Hard References to Blueprint-derived versions of that class. For me, implementing the core in C++ also provides an easier path for later rewriting Blueprint logic in C++ when needed. 6) Full replication support is something that AGLS will most likely never include.

Linuxer sysdevil

Amazing Project!! After a bit(a lot) of grinding, I managed to run it on Arch Linux using UE 5.8. Let me know if I can help someone.

Linuxer sysdevil

UE 5.8 no longer accepts the FRayTracingDynamicGeometryUpdateParams{ ... } initializer list.

TryHarder

Yep, fixed that, I've just not done the enemies not attacking as im waiting to see if Jakob is on that, but he's been a few days now. I'm not chasing at all btw. I can do it myself if I have to.

Nikkoid

5.8 is released! Congratulation on the fast release! I was struggling with Claude to compile all the plugins for 5.8. Even with the help of AI it is not an easy task.

Nikkoid

Thanks for taking the time to answer. I think you actually have three different projects, each targeting a different audience, so they could make sense as separate subscriptions: 1 — WALS: For people like me who already have games built with WALS and don't want AGLS. We mainly need ongoing maintenance and plugin updates so we can keep up with new Unreal versions. 2 — AGLS: The more advanced evolution of WALS, for people who want the additional features. 3 — RALS: A replicated/multiplayer version for developers who need networking. I think replication may look more overwhelming than it actually is. Once you have a simple local setup with a server and a client, it becomes a really interesting technical challenge. There are also plenty of ways to optimize things and "fake" replication where full replication isn't necessary. Considering how far you've already taken AGLS, I'm pretty sure you could master replication too. It's probably just a matter of jumping into it. As for Patreon, I don't know how much it currently generates, but I know people working at some of the biggest game companies, and many of them aren't making that much money. They have lots of constraints, stress and competition. It is not fun. Having your own business, being independent and having no boss is, in my experience, far more rewarding. Anyway, I'm following your work. The future will tell!

zeroDay

My brain loves this. Thanks Jak

Jakub W

Haha thanks. Since when can you post images in Patreon comments? I honestly don't know how you managed that 😅.

Jakub W

Hi. It’s great to hear that you managed to run the project on a system other than Windows. I know that Linux distributions have been gaining popularity for quite some time now. I’m curious, though, what the main issue was in your case that had to be resolved in order to open the project. If you also converted the project files from UE5.7 to UE5.8, then I know that quite a few code changes were required. However, I’m wondering whether most of those changes were actually the same as on Windows. Warnings related to things like ambiguity between float and double, or RHI issues in CableComponent, should be independent of the operating system and more related to the UHT/compiler process itself. Could you describe the steps you had to take in order to get AGLS running?

zeroDay

lool, Patreon mobile can let you attach media

Linuxer sysdevil

Hi Jakub, thanks a lot for the reply, and for AGLS! Short answer to your question: there was no single big blocker. Most of the work was the UE 5.7 to 5.8 conversion, which would be the same on Windows. Only three changes were really Linux-specific, and they come from the compiler (clang) and the build setup, not from AGLS logic. Here is the whole process, with the cause of each change. SETUP - Arch Linux, UE 5.8.2 (the Linux installed build), AGLS v2.0.0 (the UE 5.7 project, unpacked unchanged). - In AGLS.uproject I changed "EngineAssociation" from "5.7" to "5.8". - The plugins ship with Windows binaries only, so on Linux all C++ is compiled from source. I build the editor target from the command line: Engine/Build/BatchFiles/Linux/Build.sh AGLSEditor Linux Development -Project=".../AGLS.uproject" Building through the editor with -TargetType=Editor worked only the first time. After that it failed with "Unable to merge actions ... PrerequisiteItems are different", so I always build the AGLSEditor target directly. A. CHANGES NEEDED BECAUSE OF UE 5.8 (SAME ON WINDOWS) JakubCableComponent, JakubCablePhysic.cpp (around line 618). This is the RHI/cable issue you mentioned. UE 5.8 no longer accepts the FRayTracingDynamicGeometryUpdateParams{ ... } initializer list. I fill the struct field by field, the way the engine's own 5.8 CableComponent does: FRayTracingDynamicGeometryUpdateParams UpdateParams; UpdateParams.MeshBatchesView = CachedRayTracingMaterials; UpdateParams.NumVertices = (uint32)VertexCount; UpdateParams.VertexBufferSize = uint32((SIZE_T)VertexCount * sizeof(FVector3f)); UpdateParams.NumTriangles = Geometry.GetInitializer().TotalPrimitiveCount; UpdateParams.Geometry = &Geometry; UpdateParams.Buffer = VertexBuffer; Collector.AddRayTracingGeometryUpdate(FirstActiveViewIndex, MoveTemp(UpdateParams)); The zombie AnimBP (AGLS_Zombie_AnimCPP) did not compile. Its Generate Trajectory override still pointed at the 7-parameter version in AGLS_AI_AnimInstanceBase, but the parent chain is ZombieAnimInstCore > AnimInstanceSimpleCore, which has the 3-parameter version. The 4 extra pins were not connected anyway, so I pointed the override at the SimpleCore function. No behaviour change. The human AI StateTree (AGLS_HumanAI_StatesCore) did not compile. In 5.8 a StateTree parameter that uses a Blueprint enum is stored as a byte property, and an enum property reference won't bind to it, so the SearchingMode and OtherActionMode bindings failed. I replaced the three Blueprint enums used there (E_AI_TraversalActionMode, E_HumanAI_OtherActionState, E_HumanAI_SearchingState) with C++ enum classes with the same values. I added CoreRedirects (EnumRedirects with ValueChanges and OverrideClassName) in DefaultEngine.ini so the existing assets map onto them, and resaved the 19 assets that use them. After that the tree compiles. B. CHANGES NEEDED BECAUSE OF LINUX / CLANG Cpp_DynamicClimbingComponent.cpp (around line 1437): a for loop over ValidUpTraces that always returns in its first pass. Clang reports this as -Wunreachable-code-loop-increment, and the Linux build treats it as an error. I replaced it with if (ValidUpTraces.Num() > 0) using element 0. Same behaviour. HelpfulFunctionsBPLibrary.cpp (around lines 1773-1791): seven "break;" lines directly after "return;" in the input switch (-Wunreachable-code-break, also an error). I removed them. Note: this file is Windows-1250 encoded with CRLF line endings, so it has to be edited without converting it to UTF-8. Unity build macro leak: AGLS_HumanAI_CharacterBase.cpp and AGLS_ZombieCharacterCore.cpp define "#define AnimInst GetMesh()->GetAnimInstance" (and similar local macros such as CapHeight elsewhere) without #undef. In a unity build the macro leaks into the next files of the same batch and breaks every declaration named AnimInst (for example in AsyncFunctionsPlayer.cpp and Cpp_MatchedMontageComponent.h). My first build only passed because of the batch order. This one is not really Linux-only: it can happen on Windows too whenever the build groups the files differently. Adding #undef at the end of those files fixes it. MSVC doesn't treat the Cpp_DynamicClimbingComponent and HelpfulFunctionsBPLibrary topics as errors, which is why they never show up on Windows. I also did not hit any float/double ambiguity problems that blocked the build. RESULT - CompileAllBlueprints: 953 of 953, 0 errors (952 before the two asset repairs). - Tested in play on Linux: locomotion, crawl, vault, dynamic ledge climbing, rifle and pistol, cover under fire, human AI and zombie AI. - Not tested yet: ledge-to-ledge jump, pickaxe wall, grenades, packaging, and a side-by-side comparison with the Windows demo. Changes on Cpp_DynamicClimbingComponent, HelpfulFunctionsBPLibrary and AGLS_HumanAI_CharacterBase are harmless on Windows, so they could go into the main version if you like. I'm happy to send you the exact diff privately.

Jonathan P

Hey this is an amazing project! I am interested in the enemy combat arena and creating different ones and spawning enemies via trigger boxes , how do you link the trigger box behind the gate opening to the spawning of the enemies, I can't seem to replicate it in level without duplicating the trigger box and i cant find where the box and enemy spawn link to eachother.

Jakub W

I was aware of the code issues involved in compiling the previous version of the project for UE5.8. That’s why I knew right away what needed changing - and sometimes, simply swapping out the files was enough 😅.

tygra78

Hi Jakub, thanks for amazing work on 2.0, currently I have 1 critical issue with ammo count and reloading on both 5.7 and 5.8, works different on every weapon, on AK-47 it's always 2 magazines left with zero bullets also with infinite reloading. The other thing is retargeting to ue5 manny in 5.8, is not same good as in 5.7, is there a way to improuve it? And by the way, thanks for bringing back a torch system)

Ramazan Arıkan

Hello, are you thinking about making the weapon pickup animation that uses the left hand for the right hand? the current animation looks a bit awkward when the character is wearing a backpack and picks up the weapon with their right hand

Jakub W

Hi. Based on the information you provided about the weapon system, it’s possible that what you’re seeing is not actually a bug, but rather intentional behavior on my side. I would consider it an infinite reload issue only if the player could keep reloading while still being able to shoot every time, meaning that ammunition could effectively be duplicated endlessly. However, reloading itself is intentionally still possible even when the magazines are empty. I recommend checking the detailed description of this mechanic that I described in the post. Magazines can be refilled manually with individual bullets, which is why reloading is still available even when the current ammunition count is 0. As for retargeting to UE5 Manny, you’re right that it looks noticeably worse in UE5.8. In this engine version, the Retarget Asset system was reworked, so some adjustments were required. I’ve made an attempt to improve this, and it should now work much better. I also introduced several additional changes related to retargeting. By default, the AnimInstance uses only a single IK Retargeter asset. However, I added an additional mode that can use multiple retargeting assets, selected depending on values from the Player Character. This new approach is more precise because each IK Retargeter can be configured for specific situations, but it may also have a higher performance cost. For that reason, it is not enabled by default. You can test it by executing the following command: AGLS.Retargeting.UseExperimentalRigAssets 1 Alternatively, you can open 'Manny_BetterRetarget_AnimInst' and set 'ForceUseExperimentalRetargeting' to true. These changes should already be available for download.

tygra78

Yeah, great retargeting works better now, thanks) As for my current project based on AGLS, after moving to 2.0 on 5.8 my custom enemies stopped receiving ReceiveDamageShooting event when Player shoots, but when Ai shoots ReceiveDamageShooting still works, looks like something is changed in player's trace system. One more thing, I've added 2 wheel vehicle but I don't see a right way to play custom driving animation for the player, at this moment I see only replacement of base driving animation solution.

Jakub W

Hi. Regarding your issue with 'ReceiveDamageShooting', I tested it by creating a new ACharacter class, and in my case it worked correctly. It’s possible that the problem is caused by your characters not being based on that class, which would cause the CastToCharacter call to fail. However, changing how 'ReceiveDamageShooting' is called is quite simple, and you can easily adapt it to your own setup. Just go to: AGLS_PlayerGunsFunctionalityExtend -> GunShotHitResult https://snipboard.io/8hjfpg.jpg https://snipboard.io/INJKtn.jpg

Jakub W

Hi. I agree that some sequences might not be fully polished. Nevertheless, I don't really intend to make any further adjustments to elements like that.

Wilko

Hello Jakub, would you consider making an "uncharted add-on" for Narrative Pro? The developer reubs is allowing devs to sell add-ons on itch.io and may allow for patreon aswell. Perhaps you could setup a new patreon subscription for development of this add-on. This would be a good opportunity to rebuild the system within a framework that is using the new mover/gasp system aswell as has many other useful features.

Jakub W

Hi. At the moment, I’m not really planning to work on anything similar to what you described. Right now, I’m focused on AGLS v2.0.1, which is intended to fix several important bugs (I expect to release it within the next few days). My plans for further development of AGLS, or for starting a completely new project, have not been decided yet.

Duccio Carnicelli

Hi! Quick question: is there a way to trigger aiming from low cover, like in most cover shooters? If not, what things should I look into to try to implement it?

Jakub W

Hi. When it comes to aiming while the Covering system is active, this action is already supported. To do it, hold [A] or [D] together with the aiming button. This works in both Standing and Crouching. However, if you meant leaning up into a standing position while crouched (not aiming to left or right behind wall), that action is also implemented. In that case, you only need to hold RMB (rifle or pistol overlay require). The issue with this mode is that the conditions for allowing the lean are quite restrictive. The main limitation is the height of the cover, which cannot be too low or too high. The valid range is fairly narrow, which makes this behavior somewhat impractical. If you want to improve this, you should look in BP_CoverSystemV2, more specifically in the CheckCanStartAiming function. The current approach to the Traces in this function is not entirely ideal and would need to be redesigned somewhat to make the system more flexible.