- main: Deployed version of the bot (Autodeploy)
- develop: Most up-to-date branch used for development
- feature/{name}: New WIP features
All planned features and ideas can be found here.
This section will go over the usage of the bot and is mostly meant for those managing users with it.
Points info command:
/help points
Ranks info command:
/help ranks
Currently, we give points out like so.
- Splits
- Low value: 10
- Medium value: 20
- High value: 30
- Events
- Participation: 5
- Hosting: 10
- Learners
- Half: 5
- Full: 10
- Forum
- Bumping: 5
Help on different commands and topics relating to the clan.
/help (command/topic)
Use the discord slash command autocomplete to browse through options.
Points is a command that returns the points of a specified user, takes in an optional username which will default to the user calling the command if left blank.
Get own points:
/points
Get someone elses points:
/points @User
Used for gaining rank points after splitting with clan members. You must accompany using this command with a screenshot of a drop that you split with your clan members.
/split (value range)
Select the correct value range corresponding to the item value at the time.
For new users we will use /activate (username). This will automatically assign them with the Jade rank and add them to the database. This allows activated users to start recieving rank points.
/activate @User
For users that are no longer a part of the community we have /deactivate (username) which will delete all points values associated with them from the database.
/deactivate @User
Used for checking if a user is activated or not, just a simple and useful utility mod command.
/checkstatus @User
Event is used for rewarding points for either participating or hosting an event.
Rewarding a user for hosting an event:
/event hosting @User
Rewarding a user for participating in an event:
/event participation @User
Used for rewarding players that teach other clan members. Depending on the activity, players can be awarder either half or full points.
Half points:
/learner half @User
Full points:
/learner full @User
For new users we will use /activate (username). This will automatically assign them with the Jade rank and add them to the database. This allows activated users to start recieving rank points.
For users that are no longer a part of the community we have /deactivate (username) which will delete all points values associated with them from the database.
Checking if a particular user is activated or not can be done with /checkstatus (username).
Git clone the project or manually download and extract.
git clone https://github.com/Miconen/tectonic-bot
For this step you will need your bots token, if you haven't yet made a bot or got a token you can do so from Discords developer website. Once you have your bot token, create a file in the projects root folder, name it .env and paste your bot token inside as shown below.
BOT_TOKEN=BOT_TOKEN_HERE
Install your npm packages, specified in package.json
npm install
Edit passwords and usernames to your liking in docker-compose.yml
Build and start your docker instance, open a terminal window and make sure you're in your project folder.
cd (Project path)
docker-compose build
docker-compose up
Now you can open localhost:8080 in your browser, you should be able to login using the credentials you chose under phpmyadmin in docker-compose.yml. To find your ip for the "Server" field, open your terminal once again and run the following commands. These are probably root, root by default.
Boilerplate and template for the bot from https://github.com/oceanroleplay/discordx-templates/
I had this issue on a Mac. The solution to fix it was to create a new user with a host of % in the database. First user docker ps to list your containers.
docker ps
Copy your databases id and run:
docker exec -it (database_id) bash
Log in to your databse through the command line by running the following command and inserting your password. The default password is most likely either root or just blank.
mysql -u root -p
After logging in run these commands and the database connection should be fixed.
CREATE USER 'root'@'%' IDENTIFIED BY 'root';
grant all on *.* to 'root'@'%';