Nested Inventory Architecture (in short NIA) will allow you to create your desired inventory and equipment system easily and intuitively!

By Using Approaches: Nested Archicture, Object Based, Section Based, Customizable, Async Mesh Loading, All Parts Replicated.

Video Inventory Showcase: Here

First Tutorial: Here

Equipment Module Showcase: (soon)

Explore the Documentation/Tutorial: Here

Access the Test Build: Here

NIA -as the name suggests- is an architecture, it allows you to build your inventory. Based on a well designed structre and it doesn't restrict the way you edit them.

Altough there are already defined some basic functions such as: Add, TransformSlots, Discard, SetSlot" etc. , you are free to override them, or create new editing methods from scratch!

This System Gives You:​

• Nested Inventory System will allow items to hold other inventories! Backpacks within packpacks, weapon attachments inside weapons... Everything is possible!
• Object Based Architecture makes possible to make use of inheritance for primitive item types and hold runtime variables for items. Everything an object can do.
• Built in Attachment And Merging System is an option while your creating your equipment system. With a additional data asset (Attachment Settings) on Item's Payload, you can decide which items attaches or merges where. You could even attach weapons on weapons!
• Data Asset Use For Base Info allows items to hold customized variables types per class with the help of inheritance and many other advantages of using data assets.
• Sections as GameplayTags used for Inventories that hold sections with different types. Allowing item transform in a much more intuitive manner. Allowing logics like: If item tag and section tag matches etc.
• Customizable Inventory Editing is always available by overriding the related methods or create new ones for your project, Blueprints or C++!
• Replication for Networking is out of the box with NIA! Making it easier to make Multiplayer Games.

And many more!

This inventory system has a default UI, but it mainly for debugging and testing out the system. UI is not a main part of this plugin. But you could easily make your own UI based on the provided widgets and Helper Blueprint Function Libraries.

For more information please check the documentation. Cheers!