Do you think it makes sense to use sql for inventory? Because I need to separate all the rows one by one and check if they are full or empty and add them to the inventory. I personally think that these processes will tire the computer and it will be very tiring in the blueprint. What should I use?
i am using this now
I would vote no.
I think all inventory systems runs in engine, you don’t need SQL.
The only possible reason for using SQL would be a massive multiplayer game where people had A LOT of account and inventory information ( read: hundreds of MB each ).
What’s the problem you’re having?
A good and memory saving approach is, not to use SQL…
Use a Simple DataTable, that holds your Item Structure.
And your Inventory AND Inventories… should only contain an Array of a Name+Int Struct. This Struct simply contains the Item RowName and Quantity…
And via the RowName, you get the Row from the DataTable.
So… you only save this really small Inventory Array… and keep one DataTable of all Items and Stuff to get Data from.
I think there will be a huge data glut.The game I’m making is a game that works with a dedicated server and allows people to log in and create items.That’s why I need to register the inventory somewhere. As I said, assuming that there are a lot of items and considering that many people will enter the game, it’s a very big data.bunun için endişeleniyorum ve bu nedenle farklı çözümlerin olup olmadığını öğrenmek istiyorum
it makes sense that you say for an offline game, but I’m making an online game.Somehow I need to store data out of the reach of users