UPDATING.md

TRAINER UPDATE PROCESS

Upgrade cycle when balance changes are released by NGE. Note that doing the change will require you to know how to operate a webserver to test, and doing some minor changes in the source code. While not complicated, you still need to know these basics.

Doing a balance update

There are shorter ways to do so, but this way you can update a new trainer dataset beta after beta, until the final release, making 0-day releases of the live version without spending a lot of time on the said release day.

Create a new version

As soon as the first beta/rc is released, remove the data/beta directory and copy the newest version folder to data/beta (called "beta folder" later).

Change the trainer data

Modify the new trainerdata.json in the beta folder with the new balance changes in #experimental.

Until the final release is live, you can checkout beta.html to test things out, beta after beta.

Change the icons

Icons size is 47px width x 48px height. The ratio hasn't been kept to deal with some artifacts as there are different icon styles used by the game (square, rounded, with or without black border).

It's not recommended to re-edit the images from the older version, due to the quality loss it implies. Lossless icons for all skills are available in the CoRT Icons pack.

That pack also includes a python script to automatically refresh skills icons from your edited trainerdata.json. Its usage is explained in the pack's README, and is the heavily recommended method.

Making the new version available on the website once the new version is live

Copy the beta folder to data/trainer/1.x.x according to the new version number.

Update the array containing all available versions in js/trainertools/constants.js with the newest version last.

That's it.