-
It would not be ideal to have stacking right out of the box according to my designs bc I can’t predict what type of structure each dev decides to have for their inventory. I could force a certain type of schema, but I want my module to be flexible and work with different types of data. For example, you’d usually want to be able to equip your items, have it be in your character’s hand and what not. Say you equip a stacked item, how would the welding of the item’s model look like and where would the model be stored? Should one model represent the entire stack or should all the models be stored in the stack? So yeah, it’s ready on the client side, but it requires the dev to handle their server side code so that it can integrate with InventoryMaker.
-
I only designed the module with PC in mind. I don’t think I’ll be working on support for other devices since I am not at all familiar with console and don’t play enough Roblox on mobile to get a feel of how I’d like the interactions to be. Who knows…
-
I could make this a feature that can be toggled if it’s actually annoying
-
You can set the inventory capacity to the desired max limit, so that when you call AddItem(), nothing will happen. I’m not sure if this is what you mean, tho
-
im not sure what you’re aksing
-
That sounds really cool. I’ll consider adding it after I finish up documentation.
-
Yeah, the hover prompt for toolbar is disabled in the demo. It can toggled for the hotbar container though if you go into studio and set the
HOTBAR_UNTOGGLED_HOVERflag -
The server side stuff is in the demo. It’s really a bare bones server tho. In the demo, I use one tool to represent all items in a stack and only clone when necessary.
-
anti-exploit should be handled by the server, which is up to the developer to do. The server should be the main authority for checking the player’s inventory. This module works on the client, so a client-side anti-exploit is pretty much useless
3 Likes