Accommodating for Multiple Stacks of Items in an Inventory System

Help and Feedback Scripting Support
#21

…

#22

Ohhhhh yeah I remember some of this stuff from when I used to program in Java. This sounds like it’ll work, like a module script for every player?

#23

Yep, if you want I can provide some code which will get you going in the right track

#24

i don’t get why you’d want to use OOP with an inventory system? you can’t save metatables?

#25

Yes please! This is all very new to me and that would be extremely helpful

#26

Well, who said we were gunna save metatables

#27

well i don’t see the point, you’d make it unnecessarily complex with OOP.

#28

Basically you will have an Inventory class which will handle all your items and related functions like adding items, removing items, and so on. The base inventory class would look smth like this:

local Inventory = {}
Inventory.__index = Inventory

function Inventory.new(player)
    local self = {}

    self.Player = player
    self.Data = {}
    
    return setmetatable(self, Inventory)
end

Whenever our player joins, we would do:

local StackLimits = require(workspace.StackLimits)
local Inventory = require(script.Inventory)
local InventoryTables = {}

game.Players.PlayerAdded:Connect(function(Player)
	local inventory = Inventory.new(player)
    InventoryTables[player] = inventory
end)

And yes, OOP might be a lil bit too complex but the outcome is really neat, because you can just incorporate functions in each inventory and it becomes really easy to do a certain task like adding an item.

local inventory = InventoryTables[player]
inventory:AddItem(item)
inventory:RemoveItem(item)
inventory:GetItems()
inventory:Clear()
inventory:Destroy()
#29

Correct me if I’m wrong, but the first script is supposed to be a module script inside the main script?

#30

A child of the main script but yes, it’s a module script

1 Like
#31

Thank you for all your help. The work now starts!

#32

Alright feel free to hum anytime if you want assistance

1 Like
#33

What’s the __ part for? Or is that a just an example value

#34

It’s how OOP works (metatable stuff). If you wan know more, check out the topic I linked, it explains it better.

#35

Alright thank you. Could this also be stored in Datastores in some way so that the player can come back later and still have all their stuff?

#36

Yep, for that you would just listen for the PlayerRemoved event and then call preferably a method called SaveData inside the Inventory, which saves the Inventory.Data

1 Like
#37

I’ve gotten the error: Module code did not return exactly one value. I don’t think I set it up wrong, unless it needs to be put inside one of those premade module tables.

local Inventory = {}
Inventory.__index = Inventory

function Inventory.new(player)
	local self = {}
	
	self.Player = player
	self.Data = {}
	return setmetatable(self, Inventory)
end
#38

return the module at the bottom

local Inventory = {}
Inventory.__index = Inventory

function Inventory.new(player)
	local self = {}
	
	self.Player = player
	self.Data = {}
	return setmetatable(self, Inventory)
end

return Inventory
#39

Should all the executable code be put inside of the PlayerAdded function? Sorry if all these questions sound stupid

#40

Wdym by executable code?