License • Code of Conduct • Contributing • Changelog
There are two ways to build and run BotANF. One being an automated script and the other being a manual process.
The first way; running the automated script is really simple.
You first launch run the script and it'll install all dependencies, open up your default file explorer and launch VS Code (if it is found). However, there is one thing to beware of, if you do not have npm, it will ask you if you want to install it - this process uses some functions that are not available in PowerShell 5, that's the default installation on Windows which means it won't run. That's why there's an if check that verifies if the version if at least 6. You can modify that as long as you are assured that you have npm installed and accessible on the command line.
The second method is to run npm install or npm run restore to install the packages. Make sure you have the required .env file which should look like this sample env file.
BotANF uses SemVer.
Given a version number MAJOR.MINOR.PATCH, increment the
MAJORversion when you make incompatible API changes,
MINORversion when you add functionality in a backwards compatible manner, and
PATCHversion when you make backwards compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
You can create an issue or just join the support server.
