Sure, the Dialogue Index variable (just the single int) is used at runtime and it increased each time it gets to an 'Add Dialogue' node. This is so it knows how many steps into the dialogue it has gotten. The 'Dialogue Progress' variable (The map with the int key and int value) is used to store what options the player has gotten selected. If auto progressing, it'll populate with 0. The key value used when adding progress is the 'Dialogue Index', so where it has gotten to, and the value is the actual option picked by the player. When progressing dialogue, when it gets to an 'Add Dialogue' node, it checks if there is any progress in the map for the current Dialogue index. If there is, it passes through, if not, it updates the text/dialogue. I hope this helps. :)

@@mpattymtremendous! Thank you!🙏🏻

Just to clarify, whilst this inventory system is the main inspiration for the inventory system tutorial, the goal of that series is to teach you how to make any type of inventory system. In terms of the general concepts they are however very similar and yes, I do at some point plan to cover saving the inventory and world item data. This will probably be after I've done an episode on setting up something like a chest, where you have two separate inventories shown on screen and you can transfer items between them.

I won't be showing how to create this UI specifically but I'll certainly be going over some of the concepts. Whilst I have plenty more to still go over, was there anything in particular you want to know how to achieve?

Okay upon writing this, i've realized that the issue occurs when I use SetDialogueBranch but not when I use RemoveDialogueProgress. Makes me think I'm not updating my progress correctly?

@@tendowav Its hard to say specifically without seeing it. All I can suggest is double checking how you've setup the 'Set Dialogue Branch' node. If you're still having issues, feel free to jump on my discord where you share some screenshots. :)

I solved using only InputAction, thanks!!

That last time I checked that was the case for game related projects. However it would be best to check out the UE website regarding royalties. :)

I've not done facial animation myself but from my understanding, if the skeleton has facial bones, you would play a montage/animations the same way. Some games choose to have two character models though, one with and without these bones. If this is the case, you would need to switch the skeletal mesh to the relevant one before playing the montage.

@@arturmincberger9236 one option would be to add a camera switcher delay threshold. So if the player has just switched the camera, there's a few seconds delay before the camera can switch again.

I'm not entirely sure what you mean but I would imagine what I mentioned in my reply to one of your other comments would probably resolve this as it will only switch the cam when you first overlap the switcher. :)

@@mpattymI think what he meant by this is that, he wants to retain the direction control from the previous camera until the player press another direction which switches the control on the new camera to avoid the run looping between the two collisions. You can recreate this issue by setting up the two cameras facing each other with collision right next to each other then try to run on the next collision.

@@ramiru3264 Ah okay. For something like this, I'd probably store the movement direction vector before switching the camera and use that temporarily before switching to using the movement direction vectors that calculated using the current camera view. You can always include an vinterp to smooth this out if needed.

When I designed the system it was with the intention of having a main track to switch back too. If you don't need this, you can ignore the on end overlap event on the track switcher. This will mean they cam will remain at the last track it was switched too until the player overlaps another one. You can probably omit most of the logic that was added to the player character as the only thing you would need is just the camera track variable.. You will need to make sum adjustments the track switcher where when its first overlapped, you set the cam owner on the camera track stored in the character to null and then set the ref to the link track in the newly overlapped switcher. This allows the track switcher to know what current track you're using and set it's cam owner to null so it no longer ticks when overlapping with other switchers. Hope this helps. :)

Thank you. :) Regarding your statement, I'm not sure what you mean. I assume you're referring to the casting in the camera track switcher but this is just checking that the overlapped actor is the relevant player character. Unless you have multiple player characters that don't share a base character parent, using an interface just adds unnecessary extra steps.

@@mysticprophecyroblox yes, with what I've currently shown, they get pooled into a single item base (assuming they're the same item) when picked up. If you only ever want items in the world to be 1 item. (No stacking) You'll just need to update the drop function to create a new item object of the same type of the relevant type and remove 1 from the pooled total. Then assign to the spawned world item.

@@mpattym Ah thanks

Thank you. :)

Thanks. :)

OMG, literally JUST after posting this, I saw that I did connect the State pin to the Selection input 🤣 Ah well. At least this will remind anyone who gets into this bind in the future.

Yes, it's set up to use mouse clicks so it should make a difference if you're using 1st or 3rd person.

@@mpattym Awesome

This just makes it easier to get a specific actor references for scripted events. When you're spawning things dynamically, it's not always easy to get a reference to the actor in the level. You could use the get actors of class but when you want a specific actor this can be wasteful as you'll have to loop through the actors to find the one you want. Personally, this is one method of many I utilize to get the reference I need depending on the situation.

Glad you like them!

I'm sorry you're having some issues. Debugging is fairly straightforward so if you need some assistance, feel free to jump on my discord.

Ok I got it, I was following since the first lesson, you need to press compile after you add these interfaces at the beginning, every single one separately

Thank you for the feedback. I can certainly agree with your statement but my goal is to teach you how you can make 'any' type of inventory. What I'm currently showing would be applicable to most types. Once you know some of the core concepts of how to make an inventory system it becomes a lot easier to build it how you want. For example, what I'm showing here is the start of two different inventory systems I've made. One that could be compared to Minecraft and another that is similar to Fallout/Skyrim, of which are very different. If there are any specific aspects you'd like me to cover, feel free to let me know. :)

You would create a class variable of the dialogue component. You'll then be able to select any child BP of the dialogue component. You can then use this to add component by class to create the component on begin play.

@@mpattym Thanks