Inventory/Weapon Items Set up. Best practice/idea?

[Rev0verDrive]

@CryptiKau

So Im having another shot at it. But cant seem to see how I can fix it.

Basically because I am casting ItemBP as a WeaponBP to access the Weapon Details which are a part of the ItemBP Child Class WeaponBP. If I can find a way to access WeaponDetails(its a structure) from the ItemBP level without having to cast the object then I can easily go on with my inventory system.

The reason I want to do this is because each inventory slot needs to be able to hold any of the children of the ItemBP class(Weapon, Consumables and Key Items) not specific slots for weapons etc. Because Inventory juggling is a keypart of the design exactly like RE.

Using my example above you’d cast to WepSK_M416.

ItemBP (parent item class): Contains data structure/vars that all items will have.
e.g. Item ID, Item Type, umg icon etc.

Weapon_SK_BP (child Item class): Contains data structure/vars and components that ONLY & ALL weapons will have.
e.g. Max ammo, recoil struct, sway, attachment system, reloading, montages, fx, sounds, camera component etc.

WepSK_M416 (child child item class): Contains data structure/vars and components that ONLY the M416 will have if any.

The structures inherited from Weapon_SK_BP are fill ins so you don’t have to build each weapon from scratch or C&P an existing and modify. By simply using “Create child BP class” from Weapon_SK_BP gives you all the format, structures and vars needed to have a new weapon. Fill in the vars/struct fields … done.

Look at as templating. Weapon SK BP is a template for weapons.