Wednesday, 26 November 2014

Nuzlocke

Earlier this week I was talked into my first run of Pokémon Omega Ruby being a Nuzlocke run. I don't do Nuzlockes on my games for the main reason that once I have started a game, I don't start again. I am too attached to the Pokémon I have caught and start a new game means saying goodbye to them. I was fine with this when I was younger but I am more emotionally invested now than I was back then. By doing a Nuzlocke as my first run, it means I get to start over and do it properly my way once I'm finished.

Me being me, I decided I wanted a way to track stuff. So I made a small website containing information, including silhouetted gym leaders (and Elite Four) at the bottom of each page and a map/trainer card combination that updates dynamically.

The website can be found here.



The Leader / Elites on each page
Once a leader is beaten, their full coloured picture will be revealed, indicated that they have been beaten. This is controlled through a script that displays 13 images - 8 on top and 5 on bottom - wherever the relevant section is set to on the page.

The map and Trainer Card are a little different. I decided to delve into a HTML 5 canvas. Originally I was going to display static images and manually edit the text on the page itself. However I wanted a challenge, and a set up that meant I wouldn't have to edit the code for each update. So the data highlighted on the image below is obtained from a text file.

The town, money, Pokédex, Play Time and badges are set through a separate text file
For editing this text file easily, I revisited the Smash Editor and made a simplified version of it that allows me to access the same file the canvas uses. I did want to make a portable version for my phone or tablet as Pokémon is a portable game and I'm more likely to be around one of those while playing but decided the PC editor was good enough.
The data can be manipulated via an editor