Storm Alligator

Hello !

We’re Isabelle (Volute) and Thomas (Ygwee), we’re two independant game developers. We’ve made Mission in Space and right now we’re working on a new game.




Latest blog posts


A new Tinysasters is on the way !

Posted on by Volute

I’ve received a lot of positive comments about my Ludum Dare 23 entry Tinysasters on the Ludum Dare website, Kongregate and Newgrounds.

Tinysasters also got a few reviews on websites like Indiegames.com, Jayisgames and even Rock, Paper, Shotgun ! I couldn’t believe it ! It makes me very happy :)

People seem to think the game has potential, so I’ve decided to start coding a new version a few days after the end of the Ludum Dare.

The new version is about solving issues of the current game, the more problematic ones being :
- A simple technique to win is to spam workplaces
- Terraforming is not very useful

I’ve asked Ygwee to re-think all the gamedesign because he’s much more gifted with it than I am.

The new game will have :
- more buildings
- upgrades !
- spells (sort of)
- a tutorial
- several game modes, not just difficulty settings

The new version still looks like a WIP, but it is already well advanced. We hope to finish it soon ! If you’re interested, we should have a test version to show in a few days.

Posted in Tinysasters | 2 Comments


My Ludum Dare #23 entry post-mortem

Posted on by Volute

Hello everyone !

Not much activity on the website lately… Sorry about that, that’s because we’re very busy working on our new game ! We’ll tell you more about it very soon.

This week-end I made a break from our new game’s development and participated in the Ludum Dare 23 48h. For those who don’t know about it, it’s a game development event where participants have to build solo a game from scratch (no preexisting code or assets) in 48 hours. The game must be based on a specific theme chosen by the community. This time it was “Tiny World”.

There’s also the jam which is in 72 hours and has different rules.

If you want to know more about the Ludum Dare, there’s more info on the website of the event.

This was my very first participation in a game development event. I hadn’t planned to enter the event until about one week ago, and I didn’t prepare. But I work on flash game development every day, so this must count as some kind of preparation :)

I was a little anxious, because I had never developped a game in such a short amount of time, and I didn’t know if I could do it. But everything went very smoothly and I’m very happy with the game.

Now, let me tell you a little more about it…

First, its name is Tinysasters. It’s a contraction of “Tiny” and “Disasters”.
Tinysasters is a puzzle/simulation/strategy game. You play on a 8*8 randomly generated tile map and have to build workplaces, shrines and cities in order to collect ressources. The goal is to build a level 4 shrine. Natural disasters happen every now and then. They reconfigure the ground and make your life harder !


Build the level 4 shrine to heal the ground and spare the world from disasters like earthquake !

If you participated in the Ludum Dare, you can play and rate the game there :
Play and rate Tinysasters

Else you can also play on Kongregate. That version has a few bug fixes and will probably be improved :
Play Tinysasters on Kongregate

If you like the game, don’t hesitate to give the rating a little push ;)

The idea behind Tinysasters was to make something between the boardgames Settlers of Catan and Labyrinth ; basically a Settlers of Catan where the tiles move and change of nature.

At first, I was absolutely not happy with the theme. I rated it -1. I liked “Artificial Life” and “Castles in the Sky” a lot better, but I don’t know if I could have made something good out of them. The theme doesn’t matter a lot actually.

As for the nature of the game, to be honest, when it comes to play, my heart usually goes to platformers and adventure games with a good story. But programming is my strongest point, so I thought I should rely on it a lot for my entry.

 

What went right

- (almost) no time wasted on debugging ! That was a good surprise. I’m used to spending a lot of my time fixing problems that seem to come out from nowhere and make absolutely no sense although they usually end up being all my fault after all. That’s one tremendous benefit of working on a very small project : I just had to see a bug to know where it came from because the entire code of the game was so fresh in my mind.

- I was a little scared at first when I started programming the tile animating sequence that happens when there’s an earthquake or the player generates a land. But it went smoothly and the TweenLite library was very handy.

- I hate building / coding menus and interfaces with so many buttons, and so many textfields, and tabs, and they all have to update, show the right information, show a red color when there aren’t enough ressources, etc., and it’s so overwhelming… It was very tedious but it went ok. There are a lot of ugly duplicates in my code but I guess I can live with that.

One of the many possible states of this interface box…

- About 40 minutes before the deadline, there still were no sounds, and the tiles were still rough colored cubes. I rushed on as3sfxr to generate some sound effects (very useful tool), made a quick music arrangement, added an underground effect to the tiles, some texture and some decorations.

Despite the fatigue (it was about 2 AM and I had worked all day), I found myself inspired so everything went quickly and I finished on time.

- I’m very happy with the result. I enjoy just watching the game playing disasters and reconfigure the map into wild deserts, forests and lakes. The mountains always prevail, eventually.

Invasion of the mountains !

 

What went wrong

- The firsts hours of coding were the hard part. Sometimes I’d finish coding a new fonctionnality, like the map generation, and had some kind of a mental blockage : I just couldn’t figure out what to do next. What I had in front of me was so far from being a game… it was a little overwhelming.

a depressing early stage of the game

- Like I said, I only had 40 minutes to polish the sounds and graphics. I had great expectations for the animations, I wanted to use beautiful particles effects… I wanted the tiles to explode in a thousand of pixels when they reach the borders of the map instead of those mere alpha fade outs… I wanted the volcanic eruptions to set the map on fire… I wanted the flooded tiles covered with shiny swinging blue water drops… I wanted a little flying god inpersonating the player’s actions react to the disasters and constructions…

Nothing of that was done. I am so sad. Maybe in the enhanced version :)

Also, more types of disasters were initially planned. Disasters that only affect the constructions : plague, civil war, etc.

- 7 hours before the end I was like “Great, 7 hours left, I have PLENTY of time to do everything I want !”. But 7 hours in the end are not like 7 hours in the beginning, especially with the timezone I’m in. I was so tired I was like a zombie and sometimes found myself spending half my time just starring at the disasters do their thing. It’s a good thing the game was already well-advanced at this point.

 

What went terribly wrong

- But the biggest problem I encountered came from the nature of the game itself.

“Do the game mechanics even work ?”

I couldn’t answer this somewhat significant question before the game was ready to be tested. The disasters had to be coded, same goes for the ressources, the buildings, the upgrades and all the time-consuming interfaces that come with it.

The game was ready to be tested 2 hours before the end.

I had Ygwee test the game. He told me he was troubled by the game even though he knew what he had to do.

At first, I didn’t listen to what he said and continued to blindly code what I could. Coding more interfaces wouldn’t have bothered me that much at this point.

Then, I had to face the reality : the game mechanics didn’t work as they were.

I had to balance the costs and gains of ressources, add difficulty settings to avoid overwhelming the new player or boring the experienced one, write a “how to play”… For that, I had to test the game a lot which takes some time… And the game navigation (title screen, restart…) wasn’t done yet, nor the graphics and sounds, not to mention the fancy particle effects I still hadn’t given up on !

The last minute how to play screen

Damage control was done, but the game ended up being less challenging than I would have wanted. Hopefully a future enhanced version will correct that !

 

Final thoughts

I’m very glad I participated, it was a very good experience.

Bonus : some screens from the development !

My isometric map generation function wasn’t right the first time !

 

The tile MovieClip

 

Starting to look good with the procedural map generation done ! The function is based on perlin noise

 

Starting to work on the “generate land” animation. Little depth problems in the beginning as you can see

 

The game at the end of the first day. Ressources aren’t coded yet, there are no building upgrades and the disasters don’t work

 

The first disaster I coded was flood. As you can see it works alright :)

 

Play Tinysasters

 



to the blog...