Recently, in an effort to better understand how the Biomorph program worked, I decided to implement it myself in JavaScript using the HTML5 canvas element. The result of this endeavour can be found here. Read more to learn how to use the Biomorph program.

How do I work it?

The user interface contains 9 biomorphs arranged in a 3×3 grid. This is a biomorph generation. The centre the grid (with the blue border) contains the parent biomorph. The parent is the biomorph that the remaining 8 children biomorphs are based on. The children biomorphs are created by slightly mutating each of the eight genes in a biomorph.

In order to evolve a biomorph towards a certain goal, look at the 8 child biomorphs and select the one that is closest to looking like the biomorph you are aiming for. For example, if you’re trying to make a bat biomorph, pick the biomorph that looks most like a bat. Once you have a chosen a biomorph, click it to generate a new generation of biomorphs based on it.

If you choose the parent biomorph, you will simple be regenerating the child generation. However, since each gene can move in two directions, you have 16 possible children for each parent. Thus, if you are unhappy with your choice of children, you can try clicking the parent biomorph again to get one of the 8 other child biomorphs you haven’t seen.

Since I’m toying around with the idea of sidescrollers, I did a search for “Flash sidescroller tutorial” and found this excellent 3-parter by devnote.org.  Unfortunately (for me), the tutorial expects that you’re using Adobe’s Flash IDE.  Thus, as a contribution to the web (and myself… mostly myself), I translated the tutorial to work with FlashDevelop.  Read on to see how I did it, or just grab the source here.

There are basically only 3 elements in the DevNote tutorial that require the Flash IDE.  They are the Boundaries, Player and StartMarker MovieClips.

As the StartMarker was just a point, I used the Point class to represent it (and called it _startPos instead). Since Boundaries and Player were basically sprites, I represented them using the Sprite class. Here is the pertinent code:

public class Main extends MovieClip 
{
    private var _startPos:Point;
    private var _player:Sprite;
    private var _boundaries:Sprite;    
    ...
    public function Main():void {
        // Assign defaults.
        _startPos = new Point(100, 10);
 
        _player = new Sprite();
        _player.graphics.beginFill(0xff0000);
        _player.graphics.drawRect(-10, -50, 20, 50);
        _player.graphics.endFill();
        _player.x = _startPos.x;
        _player.y = _startPos.y;
        addChild(_player);
 
        _boundaries = new Sprite();
        _boundaries.graphics.beginFill(0x0000ff);
        _boundaries.graphics.drawRect(40, 100, 110, 20);
        _boundaries.graphics.drawRect(100, 150, 110, 20);
        _boundaries.graphics.lineStyle(20, 0x0000ff);
        _boundaries.graphics.moveTo(200, 300);
        _boundaries.graphics.lineTo(500, 100);
        _boundaries.graphics.moveTo(500, 100);
        _boundaries.graphics.lineTo(600, 100);
        _boundaries.graphics.moveTo(800, 200);
        _boundaries.graphics.lineTo(500, 200);
        _boundaries.graphics.endFill();
        addChild(_boundaries);
        ...
    }    
    ...
}

I also change the code slightly in the case of the key handlers (I used constants for the key codes isntead of magic numbers) and used a do ... while loop for the collision detection.

As if there wasn’t already enough Wezzle awesomeness going around, we just reduced the price of the game to $4.99 (from $14.99). So, if you haven’t yet grabbed a copy of Wezzle, I highly recommend you do it now.

For those of you unfamiliar with Wezzle, it’s a casual puzzler that features four unique items, 3 difficulty modes, 10 original songs and eye-poppingly colourful graphics.

Recently, FF1 was released on the Wii Virtual Console and, even though I already owned it on my NES, I felt the urge to play the classic again without the fear of my NES crashing because I blinked too hard.

So I flipped on my Wii, downloaded the game, and played it for about 2-3 hours a night for a week (keep in mind I logged many, many hours playing this game as a child).  Here are my thoughts on the title.

Phil, what are you doing here?
You‘re partied out, man. Again.

I liked having a customizable party.  There are 6 classes to choose from: 3 melee classes and 3 caster classes.  Since your party only consists of 4 characters, this means there’s no way you can try them all out in one play through.  That increases re-playability, and it also allows you to tailor the party to your play style.  You also become more attached to your party because they’re using the same 4 guys from start to finish.  They grow on you.

(Aside: I recently played FF2: The After Years and found it very annoying how often the characters changed.  Who cares if you level a character up if they’re only there for two scenes of the game).

Unfortunately, and this may be due to size limitations of the platform, there’s not a whole lot of in-game information to help you choose your party members.  What’s the difference between a Thief and Black Belt?  Red Mage or Black Mage?  There’s really no way to tell unless you go online and read up on the differences between the classes.  Not a huge deal considering it’s an old game, but definitely something you’d have to take care of in a modern game.

What do you want me to do?  Kill him again?

With respect to combat, I also liked how there was no rollover attack if your target died.  Allow me to explain.  In FF1 combat, you have 4 party members, and 1 or more enemies.  Combat works in rounds, where each party member and enemy gets 1 attack in an randomly chosen order.  Now, if I get in a fight with two baddies, and make all my party members attack the first guy, and he dies on the first hit, everyone else who was supposed to attack that guy wastes their attack for that round (they just hit air).  That means that in dungeons, you really have to know how much your guys hit for on average, how often they hit, and roughly how many hit points the bad guys have.  As you get familiar with your party and the baddies, you start to get a feel of how you should distribute your attacks.  This makes the combat more interesting.

That being said, that particular combat feature is a little unintuitive.  I think most players would expect their attacks to rollover.  Indeed, in later FF games, this is how combat works.  However, I’m not so sure that the feature needs to be abandoned completely.  I feel that a hybrid system strike a nice balance.  Instead of making the regular attacks miss if the target is dead, I suggest having two types of attacks: regular attacks and focused attacks.  When using regular attacks, you would have a lower hit rate but your attack would rollover if the target dies before your turn comes.  When using a focused attack, you attack would be more likely to hit, but would not rollover if the target died.  The idea being that if a warrior positioned himself on the battlefield to attack multiple enemies, he would be in a suboptimal position for hitting each them individually.

Ships, canoes and airships.  Oh my.

I liked the pacing of FF1.  I enjoyed slowly upgrading my transport and having that dictate what I could access.  For example, you start FF1 on foot.  Then, at the second village, you kill a pirate captain and take his ship.  A little later on you get a canoe, which in turn allows you to get an airship, which in turn allows you to get a class upgrade, which in turn brings us to the next point.

Rise, my champion.

I liked class changes.  In FF1, once you obtain the airship and complete a particular dungeon, you get a class change.  This changes the appearance of your character and allows them access to more weapons, armour and magic.  It’s a nice thing to look forward to (akin to getting your level 40/50/60 talents in World of WarCraft) and gives you that second wind to keep playing until the end.

Another cool thing about class changes is that they’re optional.  If you want to be hardcore, you can skip them and still beat the game.

What the hells the difference between RUB and XXXX or QAKE and ZAP!?

FF1 suffers from a problem that I feel is fairly common in many Square games.  There’s just too many spells that do the same thing.  For example, RUB, XXXX, ZAP! and QAKE are all spells that will instantly kill an enemy or enemies.  Why would you have 4 spells that do that?  I feel like the game designers just gave up with the Level 7 and 8 spells.

What’s better?  An Ice Sword or a Flame Sword?  Who can even use them?

My biggest issue with FF1 is that total lack of  in-game information.  The vendors do not tell you what the weapons, armour and spells do, or even who can use them.  I know the game came with a fold-out page that contained it, but come on, who keeps that stuff around?

Conclusion

FF1 is a wonderful game that has a surprisingly amount of depth and re-playability, especially for a game made over 20 years ago.  In fact, I feel like games like FF1 are a lost art, and have been unnecessarily abandoned for games that focus too much on CG cutscenes and not enough on gameplay.