This article lists some tools that you’ll probably want to get if you’re doing Ares coding.
Table of Contents
Do yourself a favor and get a decent code editor for managing code on your local PC. Editors offer syntax highlighting, project browsing/searching, source control integration, and more. Here are some good ones:
GitHub Desktop is a nice tool that makes it easy to work with GitHub. It’s available for Mac or Windows.
For help using GitHub, including GitHub desktop, see the Git tutorial.
You can use GitHub to move code between your test environment and your real game.
It’s helpful to have a place to test your code that isn’t your main game. That way you can make sure everything works right before unleashing it on your players.
Most games will not need a test environment until after they open to the public. While you’re in development, you can generally tolerate a few hiccups on your real server. Once you have a little more experience with Ares or are ready to open, you can explore these other options for setting up a game for development purposes.
The quickest way to set up a test game is to just get a second droplet and install a new copy of the game using the standard installation instructions. Essentially you will have two games running the same code.
You don’t need a separate host name for the test game; you can just use the droplet’s IP address as the host name.
There are a few different options for getting Ares running on your local PC.
Ares cannot run natively on a Windows PC due to a limitation of the database libraries.
Some games have tried to have a test instance installed on the same droplet as their regular game. You are strongly advised NOT to do this. The droplets aren’t built for running two games at once, and it’s very easy to accidentally mess up the configuration and/or database on your real game. If you wish to try this, you’re on your own.