![\"\"](\"https:\/\/georgebaker.nuacomputerscience.co.uk\/blog\/wp-content\/uploads\/2025\/05\/image-63.png\")
<\/figure>\n\n\n\nFirstly these are the settings for the navigation invoker which only really relevant changes are the generation radius of 1000 and removal radius of 3000 which represents how far around the enemy tiles are generated and how far away the enemy has to move out of radius to start removing tiles.<\/p>\n\n\n\n This is the project settings for the navigation system where because I’m now using navigation invokers I have enabled generate navigation only around navigation invokers and set the active tiles update interval to 0.4 seconds.<\/p>\n\n\n\n https:\/\/blueprintue.com\/blueprint\/nb18xqce<\/a><\/p>\n\n\n\n This shows the changes to the free roam logic of the enemy first change being checking if movement is enabled which is related to the activate and deactivate of the nav invoker events (more on them later). <\/p>\n\n\n\n The next changes is when movement is disabled at which point it calls activate nav invoker (calling it evoker is a typo it does get updated later just a minor detail) with a delay then calling free roam. <\/p>\n\n\n\n The next change is after the ai move to node where now both on the success and failure calls top deactivate the nav invoker then calling back to free roam. <\/p>\n\n\n\n https:\/\/blueprintue.com\/blueprint\/it1hln7d<\/a><\/p>\n\n\n\n This is the logic for both the activation and deactivation of the navigation invoker.<\/p>\n\n\n\n For deactivating it first checks if the distance between the player and enemy location is <= 2000 which if it’s not then it deactivates the navigation invoker sets movement enabled to false print strings movement disabled (testing purposes to see when the enemies movement is getting disabled) then calls free roam.<\/p>\n\n\n\n For activating it does the same check as deactivating just does it if the condition is true instead it then continues to checking if movement is enabled which if it’s false activates the navigation invoker sets movement to enabled print strings movement enabled then has a 0.4 second delay (to give time for the nav mesh to update around it) before calling free roam.<\/p>\n\n\n\n Next I added 2 box colliders to every room to act as spawning validators and have changed how the room validation works as shown below.<\/p>\n\n\n\n https:\/\/blueprintue.com\/blueprint\/as_-zenc<\/a><\/p>\n\n\n\n The start of the blueprint is still the same as it was before changes don’t start to come until the for each loop after the set actor location node. This loops through all the overlapping actors of 1 of the spawning validator with checking if each is equal to the spawned actor (itself) or the owner of the spawn arrow (the room that spawned it) which if both conditions are false sets invalid room to true.<\/p>\n\n\n\n Once that first loop is complete it goes in to the next for loop which does the exact same thing as the previous one for the after spawning validator.<\/p>\n\n\n\n On the completion of that loop it then checks the value of invalid room which to start simple if is false sets all of the room failed to false and the value of rooms failed to 0 before calling the spawn enemies node that works the same as previously.<\/p>\n\n\n\n On invalid room being true it does a for each loop of the all rooms array to check each of the rooms for which one was the room that failed which when found sets that room to failed if it’s not already print strings the room failed and increments rooms failed by 1 which then calls for the break of the loop. On complete of the loop it destroys the room that failed then checks if rooms failed is equal to 6 which if false calls back to setting target room to try again. <\/p>\n\n\n\n However if it’s true print strings no valid room resets all the failed rooms set failed rooms to 0, invalid room to false and print strings the rooms failed which was for testing but is pointless at this point.<\/p>\n\n\n\n I spent the day playing around with enemy AI fixing the animations so it now can use the Manny animations and playing the attack animation. The fix for the animations was just a simple enabling the use of acceleration for paths in the character movement component. <\/p>\n\n\n\n This is the first and simplest change to the enemy starting with using the same logic the player class uses to attach an enemy sword to the enemy on the begin play of the enemy.<\/p>\n\n\n\n https:\/\/blueprintue.com\/blueprint\/_urtdcxd<\/a><\/p>\n\n\n\n This is the only other place with changes in the enemy actor with it now having on success of the AI move to the player character acceptance radius it does once a call to an attack function which plays the enemy swing sword animation montage on complete of that it delays a second and then resets the do once.<\/p>\n\n\n\n Link to the project on Github: GeorgeBGames\/FinalProject<\/a><\/p>\n\n\n\n![\"\"](\"https:\/\/georgebaker.nuacomputerscience.co.uk\/blog\/wp-content\/uploads\/2025\/05\/image-64.png\")
<\/figure>\n\n\n\nDay 1- Afternoon<\/h4>\n\n\n\n
Day 2\/last day<\/h4>\n\n\n\n
![\"\"](\"https:\/\/georgebaker.nuacomputerscience.co.uk\/blog\/wp-content\/uploads\/2025\/05\/image-66-1024x290.png\")
<\/figure>\n\n\n\n