Amount of views here is criminal. Even already understanding the mechanics coming from Unity, you explain how to speak Unreal language, and that's extremely helpful!
Can't wait for another episode, it's so clear. Other youtube tutorials kinda explains inventory, but not really, also most of them are using some weird overcomplicated code to make simple things work.
You are a relatively hidden GEM! my god, one of the few people that gives both a follow along tutorial AND and explanation for every little move, pretty much. For someone new to game dev and scripting in general, some of these things need to be explained to me like I'm five years old, and you manage to do that without being patronizing. It's such a relief, gonna be watching your other videos as well!
Every other video I have been looking through does not get to the point quite like this. Thank you. This also solved an issue I had with getting the camera trace without actually casting. Clean. I am new to Unreal and coding and this made so much sense. Can't wait for more.
Just wanted to say that I appreciate the way you annunciate and "teach!" A lot of tutorials out there by technical / intelligent people that unfortunately don't always translate to teaching well, or explaining things in a verbally understandable way
What I like todo, is I make items actor components, so there is: Item (Actor Component) Holdable (Something the player can hold, child of item, has stuff like animations soft references (to save memory)) Melee item (child of holdable, has stats like damage, and overrides events from holdable like primary action to do an attack) Sword (inherits from melee item, has specific item stats) Then there is an inventory which works as an interface to interact with it's items array and holdable array
First of all, I'm extremely grateful for the way you explain what you're doing as you go. I find your approach to teaching very helpful. Unfortunately, I've come unstuck. Everything goes well until I test the line trace hitting the item. You mention that this won't work unless the item has collision but, in your video, it clearly does, because it works right away. I have done nothing different (except I use a different static mesh) but I'm not seeing the debug message. There are collision settings within the static mesh but I'm not sure what, if anything, needs setting here. Any tips would be greatly appreciated. Thanks again for making these vids.
Inevitably, right after posting, I found the fix (which was to add a simple collision capsule to the static mesh). D'oh! But also... Woohoo! Episode 2 here I come.
At 24:10 when trying to connect Sphere Trace Reach Length to Break Hit Result I get "Only exactly matching structures are considered compatible. Derived structures are disallowed" Anyone know what I've messed up?
The thing about inventorys that I have yet to find a good solution to, is managing items with different types of data associated - without just making a massive overbloated struct. IE. Say you want to store a gun - you need to store the amount of ammo currently in the weapon, and maybe durability. Whereas, if your storing a key, it's going to have to have some sort of ID to identify what door it opens. The way everyone does it is by making a struct with allll of that data in it, but i don't like that. Not to mention if you want to add new items with new data later on...well structs don't like to be edited when they're in use. Basically, the day I can create an inventory like rusts inventory in a modular way, ill be happy lol. Looking forward to seeing how you manage your items
You need to consider parent to child relationships if you want to take this further. For example, if the parent contains all the data needed for your inventory then the children can further become unique. The inventory will only need to look for the parent level information. Another route is having a structure of structures. A master structure that references and holds the other structures.
@@DarkslayerTV Well yea so, say you have a gun that inherits from pickup, or something along the lines. The gun will obviously have the base data that the inventory manages, but the problem still is if you wield a gun (spawn it in) shoot a couple shots, then put the gun away (despawn it) all of its data (such as the current amo in the gun) will be destroyed, and thus has to get passed into the inventory system, or somewhere to keep track of that data. Same thing with any class that's getting destroyed from the world when being put away really. Using the child struct of struct methods, I still can't really wrap my head around how the inventory manager itself would deal with that. All of those structs are going to be different data types
@@TylerSerino You could store an actor reference with the inventory item. When you equip the item set it HiddenInGame = False and attach to socket. When you unequip the item set it HiddenInGame = True and attach to root or something.
I think this is the clearest and best explained inventory system in Bp Video i come Across, insane content quality dude. I wish you the best!!!
Finally someone who actually explains why we do and use things. Thanks man subbed!
Great tutorial. Keep them coming! you're a great teacher
Amount of views here is criminal. Even already understanding the mechanics coming from Unity, you explain how to speak Unreal language, and that's extremely helpful!
I like your style of teaching. The WHY and HOW and BECAUSE anecdotes are very important.
Can't wait for another episode, it's so clear. Other youtube tutorials kinda explains inventory, but not really, also most of them are using some weird overcomplicated code to make simple things work.
You are a relatively hidden GEM! my god, one of the few people that gives both a follow along tutorial AND and explanation for every little move, pretty much. For someone new to game dev and scripting in general, some of these things need to be explained to me like I'm five years old, and you manage to do that without being patronizing. It's such a relief, gonna be watching your other videos as well!
Love this! I actually get it and can apply this other places!
Dude, thank u so much. You actually explain what is happening and why
hands down the best tutorial I've ever seen, in terms of depth
been going through inventory tutorials and thank goodness I found this because you clearly know whats going on
Hands Down Best Tutorial I have ever watched! and I have seen A lot.. Lol Good stuff man keep the info coming!
BRO i can't tell you how much i needed this video. As an artist designer who struggles with programming, this helped me so much!!!
Wow dude ! Love your format !! The community needs you !
Every other video I have been looking through does not get to the point quite like this. Thank you. This also solved an issue I had with getting the camera trace without actually casting. Clean. I am new to Unreal and coding and this made so much sense. Can't wait for more.
You are so interesting ! i'll watch this video multiple times for sure. Thanks for sharing with such depth.
Best regards,
Just wanted to say that I appreciate the way you annunciate and "teach!" A lot of tutorials out there by technical / intelligent people that unfortunately don't always translate to teaching well, or explaining things in a verbally understandable way
What I like todo, is I make items actor components, so there is:
Item (Actor Component)
Holdable (Something the player can hold, child of item, has stuff like animations soft references (to save memory))
Melee item (child of holdable, has stats like damage, and overrides events from holdable like primary action to do an attack)
Sword (inherits from melee item, has specific item stats)
Then there is an inventory which works as an interface to interact with it's items array and holdable array
Great video man, bravo
Can someone explain why you would use string, text, or name? The internet is all over the place about it
First of all, I'm extremely grateful for the way you explain what you're doing as you go. I find your approach to teaching very helpful. Unfortunately, I've come unstuck. Everything goes well until I test the line trace hitting the item. You mention that this won't work unless the item has collision but, in your video, it clearly does, because it works right away. I have done nothing different (except I use a different static mesh) but I'm not seeing the debug message. There are collision settings within the static mesh but I'm not sure what, if anything, needs setting here. Any tips would be greatly appreciated. Thanks again for making these vids.
Inevitably, right after posting, I found the fix (which was to add a simple collision capsule to the static mesh). D'oh! But also... Woohoo! Episode 2 here I come.
This is a topic that im trying to learn. It was explained like im 4 and i appreciate that. And i laughed like 7 times. Girth. 🤣
Legend!
legend
At 24:10 when trying to connect Sphere Trace Reach Length to Break Hit Result I get "Only exactly matching structures are considered compatible. Derived structures are disallowed" Anyone know what I've messed up?
I solved it! I'm a dummy and used a "multi sphere trace by channel" instead of "sphere trace by channel"
The thing about inventorys that I have yet to find a good solution to, is managing items with different types of data associated - without just making a massive overbloated struct. IE. Say you want to store a gun - you need to store the amount of ammo currently in the weapon, and maybe durability. Whereas, if your storing a key, it's going to have to have some sort of ID to identify what door it opens. The way everyone does it is by making a struct with allll of that data in it, but i don't like that. Not to mention if you want to add new items with new data later on...well structs don't like to be edited when they're in use. Basically, the day I can create an inventory like rusts inventory in a modular way, ill be happy lol. Looking forward to seeing how you manage your items
You need to consider parent to child relationships if you want to take this further. For example, if the parent contains all the data needed for your inventory then the children can further become unique. The inventory will only need to look for the parent level information.
Another route is having a structure of structures. A master structure that references and holds the other structures.
@@DarkslayerTV Well yea so, say you have a gun that inherits from pickup, or something along the lines. The gun will obviously have the base data that the inventory manages, but the problem still is if you wield a gun (spawn it in) shoot a couple shots, then put the gun away (despawn it) all of its data (such as the current amo in the gun) will be destroyed, and thus has to get passed into the inventory system, or somewhere to keep track of that data. Same thing with any class that's getting destroyed from the world when being put away really. Using the child struct of struct methods, I still can't really wrap my head around how the inventory manager itself would deal with that. All of those structs are going to be different data types
@@TylerSerino You could store an actor reference with the inventory item. When you equip the item set it HiddenInGame = False and attach to socket. When you unequip the item set it HiddenInGame = True and attach to root or something.
u r the best 🫂