This post enhances the previous post by the ability of actually placing obstacles which somewhen may become towers.
Continue reading
I know this may look like a call to clone. But the intention of this post is more like look and learn. Once you can do the same, make it better. We’ll have a look at Desktop Tower Defence and try to understand the basic methods of that game.
This post will cover the creation of the square grid in different colors and a method to obtain the actual position to build a tower.
Continue reading
I played a bit with the settlers-like map of that post to give it a more like terrain look. Therefore the triangle faces are colored now depending on their orientation.
Continue reading
This is kind of an experiment with a hexagonal map. I just had a look at “The Settlers”. Great game. Alright, the hexmap (map made of hexagonal tiles) can be described by nodes arranged in a triangular fashion.
Continue reading
In this part the adjacent cells of the acual node are called. This can get handy if we want to implement some kind of pathfinding algorithm. The base for this code is part 2.2. See part 1 for the creation of the basic grid.
Continue reading
This part deals with similar interaction as part 2.1 without the masses of EventListeners. See part 1 for the creation of the basic grid.
Continue reading
Now it’s time to add some interaction to the grid made in part 1. For that purpose simple MouseEvents for movement and click will be sufficient. As indication we will change the color of the relevant tile.
Continue reading
There are a lot of games based on different kinds of grids: Real Time Strategy (RTS) or round based Role Play Games (RPG) and Tower Defence (TD) games as well as Top-Down-Shooters and vertical scrolling Jump&Runs. One could use grids for tactical board games as well.
In the grid we are going to create, each tile consists of two parts, an Object() for the node and a MovieClip() for the graphic. The presented code is timeline and can thus be copied into the actions panel. This way it can be used for practicing purposes fast. For a game I would rather create and sort the code in classes.
Continue reading
This is now a less frustrating sequel. Less frustrating because I did not implement instant losing in the easy mode. Well, some players already commented on the game being too hard or too easy. Seems like mission completed! I did reuse a lot of code and stuff from the first game, thus development should have been fast. It wasn’t.
Continue reading
The fastest game I’ve ever made (including the time of despair about lack of talent) for mochimedia’s January contest. Uhh, graphics are a horrible thing. It would be easier it every object had a clearly defined function. Anyway, that game definitly holds some opportunities and a sequel should definitely follow. Maybe I should get an artist on board of the team.
Continue reading
TripleDrop
TriPop
PaperWolf: Training