Info: Bot prefix is tataru, < > refers to a required argument, [ ] is optional,do not actually type these.
"--" denotes a flag for an argument eg. --flagname argument
(note: subcommands for the commands encounterlogs, logs of category FFlogs are omitted
as they're similar to the tierlogs command)
Help
Command and Aliases
Description
Example Usage
help
Shows help about a command, or category
tataru help <command name>, tataru help <category name>
No Category
Command and Aliases
Description
Example Usage
ping
Check the bot's websocket latency
tataru ping
prefix
Returns the bot current prefixes
tataru prefix
say
Echo a message
tataru say <sup, biches>
about
Get info about the bot
tataru about
source
Returns the bot's github url
tataru source
Mirapi
Command and Aliases
Description
Example Usage
mirapi, mi
The main command for mirapi by itself returns glamours on the main page
tataru mirapi
acceptable_flags, af
Returns acceptable arguments that can be passed as flags for equipment and filters commands
Create the database
You will need to create a postgres database owned by postgres and require PostgreSQL 9.5 or higher.
The bot will add the tables on startup.
Setting up configuration
example configuration can be found in the exampleconfig.py, create a config.py similar to this
and place it in the config directory
Upon starting the bot by running the main.py file you will finally need to run the add_zones command to
setup the fflogs cog, and run the add_images to setup the gamerscape cog then, setup_worlds_dc to have the bot save lodestone users.
Optionally your preferred method of serving images locally with http/https. Note if you choose not to gis glam random [sub command] will not function as intended, depending on how you structure your directories you'll need to modify some code you can opt to use the tree structure I have here