The Enemies are pretty buggy, shooting for 2-3-4 second when there is no longer a target. Sometimes some of the agents is just freezes on one place. Also, I was never answered a question from the support form.

I'm writing about a compatibility issue I encountered with the Enemy AI asset's setup script. In February we discussed how the SetupProject.cs script applies the TagManager preset, which completely overwrites existing layer configurations. This is causing significant conflicts with other assets, particularly VR systems like AutoHand. The Problem: When users run "Enemy AI/Set Project Settings", the preset overwrites ALL layers in the TagManager. This breaks carefully configured layer setups from other assets, especially VR systems that require specific layers like "Hand", "Grabbing", "NotGrabbable", etc. Current Behavior: The preset applies globally, removing any layers not defined in the Enemy AI preset VR systems lose their critical layer configurations Physics collisions break because layer assignments are lost The VR player character behaves erratically (flying around, collision issues)

Bad code, architecture and design practices, package uses so much layers. Whole package looks like written by junior. Better write enemy system by yourself.

I downloaded this package to use in a very simple rts system, and was a bit disappointed that the targeting of enemies can only be set to one specific target: the player. That was decently clear in the description, so that's on me. Other than that, it is a very high quality package, and is very simple to set up with custom characters and guns. I am currently reworking the scripts from the ground up to incorporate multiple targets, and the understandable code structure luckily makes that very easy.

Usually I stay away from AI packs as they are very incompatible if you already have a system in place. I used this to add a variant enemy to my current AI and the layer / tag set up did not mess up my project at all (plus was easy to edit). Very easy to integrate and set up on new models. Thanks!

you need to do all setup yourself, so you can do the same by watching any tutorial on youtube

ive downloaded the addon, imported it, and im watching the tutorial and im up to 5:22 and they say right click the robot kyle model and there should be an enemyai tab but there just isnt one Edit: i changed it from 1 star to 5 stars, idk why but for some reason my project just wouldnt work with the addon even tho it was brand new and barely had anything done on it.. i opened up an empty project to make sure it works and it works pretty well once you get past the config that *could* be a little easier for beginners but at least its super configurable!

The AI is very confusing to configure and does´t work anymore because it´s outdated

So in general it works fine, the logic is solid enough. It's a well thought state machine. Don't expect incredible things but it's good enough for sure. What dropped a star is that the asset is so very self-contained. You have to work only within its extreme constraints where if you don't follow it's exact rules, you have no chance to implement it to a custom system you might have. I'm talking large, AA size projects that spread through companies etc. Sometimes you have many complex things that need to go together and often you have to touch the asset you buy yourself to make it go with what you have. Well, this asset is not very easily adaptable that's for sure. Took a lot of digging to understand what's behind the code. Update: The dev contacted me and ensured that the next update is getting rid of the element that I originally complained about below. Hence the updated review. The second star was dropped because of just one simple line of code: aimTarget.root I am genuinely surprised that the actually intelligent and good coding developer of this asset, chose to use this extremely, very extremely limiting type of access where your targets always have to be on the root of the hierarchy. You can't do anything related to parenting, hierarchical stuff, addressable based multi-faceted scene/prefab relations etc. It's as blunt as it sounds. Your targets have to be on root. I'm very open to edit this, if the developer can provide under this very comment, a very, undeniable reason to use this type of access rather than simply using properties, variables etc. Heck I would even be ok with something as drastic as using Reflection before going for transform.root.

This asset is very basic, no idea why the ratings are so high. They make you do so much work on your own setting it up that you might as well just build it yourself based on tutorials and then have more control too. For me it is also broken, doesn't follow the player smoothly. You should not have to put this much work into getting an asset to work.