Open AbbyCottontail opened 7 years ago
execute
(runs when user obtain the item, either bought or obtained via an in discord game action or given by another user), executeUse
(runs when user use the item), type
(what kind of item), isUsable
(does item have usable function, if not, don't executeUse
)
example use case: an item that is used display a emoji on profile, or to show a certain stat would not be usable, while an item for a game or an item that be used to cause a reaction from bot would be usable,
*isBuyable
(can items be brought, if not, do-not display in the store)
use case: special titles that is given via other commands or a game item that is only given from a game.
description
(Item description), name
(Item name), invID
(called invID to hopefully help me avoid confusion between the unique itemID used for each items in user_inv database and InvID for the ID of the object item)title
(for item that is a title a user could have), invItem
(to refer to items that is mostly for show on profile or something), gameItems
(refer to items that get used for games)
example phoenix down for a RPG,
extental
(that give something for an item that is not for the bot)
e.g. maybe a code for a hat for use in guns of icarus or a code for a steam game, website, etc
upon bot start-up, the inv database will be refreshed to make sure each item is updated with type, description, invID, name, icon and store(isbuyable), this is so that I can mantain a the item list in one place only. Instead of having to worry about keeping items updated in more than one location. The big factor is making sure that I don't mess with an invID and if an item is removed, it's removed across the board (from user_inv as well)
A Store front where discord users can buy items with the currency gained from chatting. Effects of the items could vary from applying fluff to profile to exp gains, to titles, and more.