You're very welcome 🙏 glad you enjoyed it and thank you for watching!

@@AliElZoheiry no problem ! really love your tutorials, and would be cool to see some on parkour systems ^^

Is that a plugin?

@@AliElZoheiry it is motion matching, the 500+ animation project they just released, it's a very performant way to do complex animations. It is deprecating the anim state tree.

@@HiddenWorldsLLC ahh that's what you mean. Yeah I tried it out! Very cool technology. Though I wouldn't say it's deprecating the animation state machine, as motion matching is a different way of doing animations and requires a huge database of different animations and poses. I would say it's better for realism and complex movement, but state machines will still be used widely

@@AliElZoheiry You have links disabled so I cant even post a name of a video but the GDC they did recently and the video they did all the way back in 2016 about motion matching, they are saying they want to replace the state tree with motion matching like the Enhanced Input System, Niagara, and other things. From what I have seen, when they say they want to deprecate something they make it happen. It may not be tomorrow, this year, or next year but eventually I think it will happen. This doesn't mean you can't still use these systems, but they are deprecating things for a reason. Niagara was a HUGE update to particle systems, Enhanced Input gives you so much more control over your players Inputs. Motion Matching is also so much better than a state tree. This does not mean you cant use it but there is a reason they put so much emphasis on Motion Matching.

I get that question a lot, and it seems like the most intuitive thing to do. But is actually the same exact thing I am trying to avoid here. Which is create a dependency between the widget and the other actors (e.g the enemy and the door) Because imagine this scenario. You decide one day to remove the widget from your level, and replace it with something else. Suddenly the door stops working 😅 and you have to rebuild the mechanism for opening the door somewhere else. Pretty strange for a UI element to control a gameplay mechanic, that's why creating unwanted dependencies can cause a lot of problems when making changes in your game down the line. and trust me, you will always be making changes

@@AliElZoheiry the Get Widget class is the lazy way to trigger the widget event. you can do it via Interface. use User Widget Object. send it to actor and let the actor do the bpi thing. so no reference on each other. but this case im talking about is the one you demos in the video, other scenario is different. i have done similar thing in my ongoing framework project. in my Actor Component which haves the HUD init. i have the User Widget Object saved there as variable ( not the hard reference of the Widget) and i trigger every Widget events store in that Main HUD UI by having other widget as a child via UI Interface. this method has no Reference to actor and to the widget vice versa. im still learning things, so i followed you , hoped you share more good ideas. dont get annoyed if comments like this appear. its just a dev convo , so i can learned more. ty

@@Jabolaso hey, I think you missed the 2nd part of this series. The next video on dependencies is the one that tackles this problem. Check it out and let me know if it answers your questions

Hey there! Thanks for the heads-up! I'll make sure to test it out in 5.4

​​@@AliElZoheiry just to be clear in not talking about collapsing to functions or macros it is specific to nodes in event graph at 4:00 i just create new event graphs if i want to clean up like that like having a debug graph stats graph quests graph, it's a good alternative

Indeed, it all comes down to the specific requirements and architecture of the system being developed. Nothing is black and white in software development, and there are always trade offs. Thank you for sharing your insights!

Hey there! Thank you for your comment and sharing that tip with us. It's really helpful for anyone encountering the same issue. Keep up the good work!

Hey there! Through my patreon you can download the entire project, and migrate any assets you want to your own project, just like I do in the next part of this series (Where I migrate the bow to my other Enemy AI project)

@@AliElZoheiry thankyou!

For multiplayer, you have to think about a whole array of different things. So it's not that a design pattern that works for single player can work for multiplayer as well. It highly depends on how you want the projectiles to be replicated. I try not to go into multiplayer in my tutorials, because it really multiplies the scope x10, and is highly highly dependent on the type of game you're making

At 19:34 I explain that this could happen if the mesh itself isn't pointing to the X axis, check out that part and make sure your arrow is transformed the same as mine

@@AliElZoheiry hey the mesh was pointing z axis . I changed it and now it's working properly thanks bro.

Glad to hear you've found the tutorials helpful! Thank you for the recommendation. 🙏

@@AliElZoheiry i already know the things you teach but i like to see other people's implementation of mechanics and you and i build almost identical systems and i have people ask about things all the time and a lot of tutorials on yt are very basic and they just try to get the job done as quick as possible which is good if you are a beginner just looking to learn things but it is not good for a full game.

Glad to hear you were able to resolve the issue! Setting the item and context offset can make a big difference in how the AI interprets the query. Sounds like you found a good compromise for now. Keep up the great work!