We’ve built Rucksack with the goal of being the most flexible and extensible inventory solution with UNet support that enables you to easily setup player inventories, NPC inventories, banks, premium shops and much more! So, what does this mean?
>> View on the Asset Store <<
Signup for the mailing list
>> Join Discord (thread not maintained) <<
It means that Rucksack is a super extensible system with full source code, a modular event based UI system, multiplayer built-in with UNet integration, a network permission model with server-based authorization, and much more!
We’re on a mission to build the best modular multiplayer-ready inventory system on the market, using all the knowledge we’ve gained over the years on the Asset Store - and we’re very hyped about releasing what we believe to be the best tool we’ve ever built!
Main Features
Multiplayer-compatible with UNet integration:
With a built-in integration for UNet that allows you to integrate into any server/networking setup, Rucksack is perfect for both online multiplayer and singleplayer games. Rucksack is secure and uses a server-authoritative permission model; So, no cheaters!
Modular event based UI system:
You’re in full control of your UI with our modular and event-based UI system. The system is very fast and extensible, yet simple to use, which means you’ll be setting up your inventory / collections UI in no time! It doesn’t matter if you’re making a fantasy RPG or a casual mobile game with IAP - Rucksack’s UI system can handle it all.
Items with behaviours:
In Rucksack, items can have behaviors, and you can very easily make your own item types and add custom behavior. We won’t limit your options!
Restrict collections:
Need a quest items-only inventory? Or a consumables-only inventory? Not a problem for Rucksack; Use any metric to restrict the objects that can be stored in a collection.
Insanely extensible:
Rucksack has been built from the ground-up to be extensible in every possible way, ensuring that you’ll never be limited in what you can achieve with the system if you want to extend it.
Visual item equipment / NPC’s with equipment:
Any character in your game can have their own inventories and equipment, which means you can make them equip different weapons and gear by simply binding it onto the NPC (static, skinned, and dynamic cloth meshes, or write your own equipment handler).
Permission Model with server-based authorization:
Our server-based authorization model makes your game cheat-proof, while remaining flexible and extensible to fit every kind of server / network setup. Example use with UNet: UNetPermissionRegistry.collections.SetPermission(collection, player, Permission.Read).
Vendors can sell anything for anything:
Need to be able to sell houses for cats, or skill for skillpoints? With Rucksack, any item can be sold, and anything can be a currency. Go nuts!
Shared and non-shared (instanced) banks and chests:
With Rucksack, you can easily differentiate between and setup both shared and non-shared (instanced) banks and chests in-game. The system is so flexible that the shared banks and chests could theoretically be shared between every player in a game, everyone in your party - and everything in-between.
Modular input and UI system:
Rucksack’s modular input system is extensible and changeable, and allows you to create input modules to handle your input. The beauty is that you can very easily replace or swap out certain input modules for maximum control (example).
Item inheritance:
Want to reduce the data transfers in your online game? With item inheritance, you can create variations of items (e.g. a Sword that can also be a Fire Sword). With Rucksack’s inheritance system, the Fire Sword can inherit its base stats from the Sword, while only overriding or adding those properties that have changed or have been added. In a large game, this saves a lot of duplicate data of unused props from being transferred.
Different prices at vendors for different users:
You can easily achieve and setup different prices at vendors / shops based on whatever properties you want, such as different in-app purchase prices based on country (requires custom IVendor implementation).
Thanks to everyone who helped beta test, and we hope you’re as excited as we are about Rucksack! Got any suggestions or feedback? Let us know below 
>> Join Discord (thread not maintained) <<
- Your friends at Devdog (Joris and Sune)
