Getting to know the Tiled map editor

I came across this tutorial on parsing .tmx maps into AS3. While I find it useful enough to get me started there are still other parts I had to figure out myself.

Using multiple tilesets

When using multiple tilesets additional <tileset> nodes are added to the .tmx file. This means we need to register listeners to each of the images and track when all of them have finished loading. In my case, I implemented a flag on my “onLoaded” function that triggers only when all the images are fully loaded.

Only when the images are fully loaded can you start the actual render process. Else you might end up with a null bitmapdata.

Using the firstgid attribute.

Each <tileset> has an attribute called firstgid. It simply tells the gid of the first element of the tileset. So if you have two tilesets one has firstgid = “1” and the other has firstgid=”301”, the tiles with gids from 1 – 300 are located on the first tileset and >=301 on the second tileset.

two tilesheets

CSV layer parsing

It is possible to specify other encryption methods but I have only tried XML and CSV. Parsing XML layers can freeze the flash player especially on large maps. The CSV layer can be treated as a String so parsing it is only a matter of using split() operations.

A Tree by the Sea

Oops, I rhymed.

This here is the draft screenie for the first scene of LoveHateGame. Everything inside the non-gray area is the player’s viewport (it’s a little photoshop trick I learned from my former artist officemates).

The gameplay is now slightly different than the last post. I’ll explain it later after I make the 2nd scene.

Still I’m a little bit worried about the number of sprites this scene might animate considering most of the things here are alive — the trees, the grass, the sea breeze, the sea, the sky and most specially the people. I want this scene to feel alive because this might be one of the few scenes the player will interact with. Everything in this scene must be enough for the player to feel the whole game.

1st Sketch, A lot of wasted space below the horizon

I was trying to get a grip of the grass overlooking the sea concept. I would have taken the easy way and silhouetted the art style but this would make the world dull and sad. I also wanted to make the player feel like a distance observer for the player hence the long road leading to the tree, but with this I’ll have to draw the avatar and other people smaller and that might be a problem.

The tree will be an integral part of the game and would reflect the player’s progress. As time goes the tree will shed until it withers.

Jollibug now with parallax

My friend is making a game called Jollibug. He made it during the Global Game Jam. It isn’t about a certain fastfood mascot — although I personally believe otherwise. He forced me at gunpoint to upload some updates of his game in my blog.

Any resemblance is coincidental

He said he put some parallaxing on the layered backgrounds now. He also made  a totally original menu screen because his game didn’t have any!!! WTF!

Things that are on the works:

  • Animate menuscreen
  • Add warnings or signals on where the enemies come from
  • Sound (sounds halfass right now)
  • Add more corporate advertising
  • Game over screen looks like it was made by a jologs
  • Audience animation states

I think making parody games is for those who don’t have creativity but have an immature sense of humor.

Biomodd Game Post Mortem

Original design sketch.

I was trying to stay away from writing a post mortem for this game because I don’t want to accept that it’s over. Multiplatform support, multiplayer networking, a 3 (occasionally 2, but usually 1) man development team and a very short project deadline; this was clearly one of the most challenging projects I ever did. It was also the most fun. From the all nighter brain storming session with Jeryll, Angelo‘s wonderful design inputs, game design arguments with Lomel (ex. Should Maria Makiling have a “Wrath” meter that allows her to nuke the whole place?); the whole creative process justified the reason why I chose to make games: it’s way more fun than just playing them.

However, coming from a software engineer’s perspective the project piled up with mistake after mistake that the game would have come out mediocre at best. And it did, actually. The game wasn’t there during the first opening night and it was barely enjoyable when it came out in the second.

What Went Wrong?

Choosing the wrong guns

During the initial planning, I was the only game programmer present, and a very inexperienced one at that. Multiplatform? That leaves GameMaker out. Multiplayer? Hmm, Java has nice networking features. Graphics requirements.. ok there’s no way we can render something that intensive in Flash. I chose Flash and Java anyway for the main reason that Flash is actually more multiplatform than Java, and Java will handle Flash’s networking. I was in the middle of creating my game engine in Flash when I posted this..

That’s right, I can’t make the animations smooth enough for an enjoyable game experience. So I went back to Java. I chose an old Java game framework called JGame and Sun’s Project Darkstar Server. Both frameworks looked easy enough. I put aside JGame since it was the least challenging and began working on the Server Side.

Bad choice number 1. It was too late when I realize that JGame wasn’t a good choice programming wise because it hardly implements any OOP, and there were already two programmers sharing and modifying the same java code file. Plus it became a headache just trying to locate java functions inside a 1000 plus line single file source code.

Bad choice number 2. Choosing to work on the network servers before even creating a working game. I thought that if I finish the hardest part, then everything would be smooth sailing from there. What I didn’t saw, was the possibility that I just might not pull off that hardest part. Blinded by my inexperience and my pride to do something only few developers even attempt to do, I marched on; with the rest of the Biomodd guys not seeing the semblance of a game coming out from my computer screen.

This was a case when a rapid prototype would have benefited the project greatly. More people could have played the game even if it was still on beta. Playtesting and balancing would have been done based on their inputs. And more buzz would have been generated about the game.

Lacking the right tools

Remember Java’s “write once, run anywhere” credo, well, I never realized how much of a fantasy that was until I tried running the server and the client on Ubuntu. I never anticipated the screensize not automatically adjusting plus the sound not working on Linux. Add the extra work of uploading the necessary .jars and you have yourself a big problem that would’ve been easily solved if I used multiple Virtual Machines on my laptop.

I was also using Vista x64 which much to my disappointment, being the fanboy that I am, crashed every time my development processes took 100% of the memory.

Jeryl in the lab

What Went Right?

Changing Horses in Midstream

And having the courage to do so. I have been ignoring Slick2D up until 3 weeks before the Manila exhibit. I realized I can’t go on with JGame and if I continue trying to make it work the code is going to be worse and worse. Slick was actually pretty easy to jump into and I recoded the whole game in just 2 days. The transition was painless I even added some extra holes in it for the networking layer.

The code base itself became more stable and extensible that it just took me a little more than an hour to add the 2-player and Twitter features.


A lot of the features originally stated in the game design didn’t make it to the final game (or at least the game that was played in the exhibit). My inadequacies in programming skills prevented me from creating a stable networking layer. Hardware issues made receiving data streams from environment sensors a difficult task. The way we intended to represent Maria Makiling seemed impractical considering our lack of artistic skills. We also have to let go of the much debated Wrath issue of Maria Makiling. It looked as if the features that made the game fun on paper weren’t going to be part of the actual software.

Then, 2 weeks before the end of the exhibit, I made some of the few good decisions I made in this project.

  1. Put the game source on code sharing.
  2. Dropped the networking layer altogether.
  3. Made a single machine 2 player game.
  4. Connected the game to twitter.

First, I shared the game in Google Code. This way the game can finally declare itself open-source. (Well, not really that open, outsiders only have read privileges). It didn’t actually contribute anything development-wise, but putting it up there made the project “immortal”. The installation may be dismantled, its parts distributed or recycled, but the software and the source will always remain in the clouds free for anyone to check out – and/or laugh at. (Which reminds me, I might need to clean up the code a bit for those who are allergic to duct-tape coding).

Second, I made the painful decision to let go of the highly unstable networking code. It was becoming a monster and working on it ate a lot of valuable dev time that should have been spent on improving the gameplay. Throughout the project, the multiplayer feature took the highest priority; the game cannot be the game if it wasn’t multiplayer, the game design hinges on that. Also, call it programmer’s ego, but the thought of giving up on the coolest thing you have ever coded simply didn’t enter my thoughts during that time.

It was after taking a few days off that it finally hit me. There simply isn’t enough time to pull off what I’ve been trying to do. And it wasn’t that I was giving up on my code, I simply saw a different way to write it. The networking layer needs to be taken down, but that doesn’t mean the game had to change. In fact, releasing it on single player for the exhibit was already shameful in my part.

The game should only be played with other people. So I settled with the easiest option: make it 2 player. With only a few days left on the exhibit, I thought it was too late.

Lastly, there’s “the game tweets” decision. Originally, Tina, the electronics ninja, setup some sensors to connect to the internet and visualize the state of the installation. The game was supposed to hook to that as well, creating a unique interaction that fuses everything in Biomodd together. Sadly, because I was too focused on unimportant stuff (curse you, networking and parallel programming!) I didn’t give much attention on this until it was too late. I was trying my hardest to get pachube feeds to the game when I thought, “It’s going to take a lot of time to set this up. And I still don’t have any idea how to interpret the data into the game aside from changing the background. Maybe if the sensors just tweet me stuff they want to happen to the game…”

So I connected the game to twitter and the possibilities of the tweeting interaction began pouring as I code it. The game tweets, players tweet the game. And since I know that the game was only going to be played within the PCs of Biomodd, I can get away with this easily. It won’t flood Twitter’s bandwidth, players feel Makiling in the context of the game and the installation and there’s certainly the “Whoah, this has never been done before” factor.


The project is definitely my most challenging yet. I don’t want to conclude.


Biomodd[LBA2] website:
Google Code Project Repository:
Maria Makiling’s Twitter account:

It is what is. 🙂

Remember that AI game you were working on?

Back when I was still in school, a professor advised us to createa code repository. Sure you might find your old programs stupid and badly written but within those old crappy code you might find something of value. Come to think of it, this is one of the reasons why I made this blog.

While working on the Biomodd game, I stumbled upon an old project of mine. It was a java based simulation platform for implementing bot behavior. I started coding it a few weeks after graduation fresh from my immune algorithms thesis. The algorithm bit of the thesis was interesting but I was more curious at how I can extend the system so that I can easily swap algorithms without changing much of the code. I didn’t know it then but I was actually trying to design a framework. Like most of my “ventures”, I eventually had to freeze the project after I dug into “flocking algorithms” and totally messed up the physics part. I was at my hometown with no internet and no physics or math book so I had to rely on stock knowledge for pretty much everything.

My OOP and design pattern skills were limited but the code came in handy when I was studying for an IT-certificate course (don’t ask J). We were required to present a game that utilizes OOP concepts. I revived the project, added a few sprites, simplified the movement algorithms (to a simple linear Point A to Point B movement), added a few if-else conditions then presented the “game” to our class the next day.

It was almost a year since I last touched the code and had to download JCreator in order to open the project file. Going back to JCreator after my experience with NetBeans and Eclipse made me wonder at how simple my programming needs were back in college. No code-complete, no SVNs, no build or debug tools, no refactoring.

Everything was so simple. I looked over my code and saw stupid OOP mistakes. Bad use of inheritance here, bloated classes there. I searched for the movement logic and, thanks to the code comments of my old self, easily found it and toyed with it once more.

I guess maybe I need to create a google code account or something, just to have something to put all the past codes/garbage in. Ok I’ll do that, as soon as I have broadband access.

Designing the Biomodd Multiplayer

We are still currently at the development phase of the project. The team is made up of 3 volunteers: 2 programmers and 1 game artist.

I am responsible for both the server side architecture and the client-server messaging protocols. Lemuel is in charge of the client side engine. And Jeryl is responsible for the art assets. It would be great if we have another programmer take care of the messaging protocols so I can focus on the server.

As you can see from the game design, the uniqueness of the game calls for 3 technically challenging features. First, it has to be multiplayer, which means it has to be built on a server-client framework. Second, it has to simulate a growing organic being. Third, the game must have no “beginning” and “end”.

Standalone games are usually executed on a game loop (movePlayer->moveEnemies->checkAgainstGameRules->renderGraphics-> repeat until game ends). But in the case of a multiplayer game, the game loop is partly in the server and partly in the client. The server stores the game state and broadcasts it to the clients for rendering, while the clients get user inputs and sends it to the server to update the game state. In a turn based multiplayer game this change in structure wouldn’t really matter much, since the players are contained in a simple little queue and at any given time only one client is accessing the game state. This changes drastically on an arcade style multiplayer, since the game runs on real time and at one point multiple clients might be trying to access a single resource. This would eventually lead to deadlocks, memory leaks, and all kinds of nasty behavior. To resolve this issue, we implemented Sun Microsystem’s Project Darkstar Server. (Though still on its beta phase, this framework worked like a charm).

Traditional multiplayer game designs limit the amount of data transfers between client and server. Send packets too much too soon and you’ll clog the network. This leads the team to its current roadblock. The entire game state (plants, enemies, players and all) must be stored in the server. Everything, including the movement calculations, plant growth, collision detection, spell cool-downs, etc. must be calculated in the server. Why not put some of them in the client? Because the game has neither a definite beginning nor end. The game exists even without a client. Once a client enters the world the server has to send him the entire game state.

Putting all the stress in the server would be impractical. We are currently trying to resolve this issue by using timestamps. By storing a timestamp value corresponding to the time a game object was last updated, hopefully, any fresh client can calculate the game state based on the time elapsed without having the need to physically store the game objects. That way we are transferring the computational burden to the clients.

We are using Project Darkstar for server side and jGame for the client (the latter is actually pretty old/dead, but it’s easier for non-game programmers to understand than “real” java game frameworks like jMonkeyEngine).

With the deadline creeping in, the team would be more than happy if we can at least make the game playable. I for one, still think it’s the kewlest game ever.