TFS storage table

[Itutorial]

I think we should work on setting up different tables for different storage values. For example: Exhaust storage could be its own table. Quest storage in its own table, ect. This would allow multiple of the same storage values to be used in different context and keep tables smaller increasing the efficiency of the database when handling storage values. What do you guys think?

 

[Perun]

pointless, just use 1 lib .lua put every storage number to table like:


STORAGES_QUESTS = {
QUEST_NAME = 1234,
}
etc, so you know which storages u used and which not. Don't need any other system. + storages are saved in memory, it save to database when you save player, so its not a problem.

+ you have some reserved storages for outfits etc and you can reserve some for any of your custom system

 

[Evil Puncker]

pointless, just use 1 lib .lua put every storage number to table like:


STORAGES_QUESTS = {
QUEST_NAME = 1234,
}
etc, so you know which storages u used and which not. Don't need any other system. + storages are saved in memory, it save to database when you save player, so its not a problem.

+ you have some reserved storages for outfits etc and you can reserve some for any of your custom system

yeah that is exactly how it is already, we currently only have 17 storages and I don't see new ones coming anytime soon