Right now, I’m loading all the tools into the player’s starter gear, and when the player dies, I delete all the tools that are supposed to be lost on death. I have a table that saves all the tool information from the starter gear, but I’m worried there will be some issues with duping. Are there better ways to handle this?
I’m not sure what you mean by this, but if you have tools with properties that can change for each player, then you can store default tools in a folder and when a player joins, just duplicate it and change the properties to what the player has for that tool. If that was your method already, then it’s fine.
That’s what I’m already doing; I think I should rephrase what I’m worried about.
When I duplicate the tools, I add them all to the player’s starter gear. This is so that I don’t have to constantly keep adding them to the player’s backpacks with code. I don’t think it has any performance changes, but it makes my life easier and gives me more clarity about my code. I’m wondering if there are any issues with doing this or if there are better ways to accomplish it.
There’s nothing wrong with that and it’s the most efficient method. Although, if you give the player tools and they’re intended to be lost after the player dies, then you can just parent them to the player’s backpack.