About project Little Goblin

Game Description

Little Goblin will be a browser game where you fight against monsters, find treasure and advance in experience - always one step away from the next encounter, which may very well be your last...

If your character dies, you get an entry in the highscore list and loose some of your status. Then, you may once again try to win the game (which means vanquishing all the monsters to be found in the dungeons).

The goal is to create a rogue-like fantasy game without a map. You leave a room, you encounter the next monster (or another interesting situation). No running around as I have a strong dislike for games which keep the player wandering through endless levels without anything happening.

Development

Little Goblin is currently a one-man hobby project, which I code in my spare time. It is intended as a project where I can add a little code or something valuable every day. It will be a journey of many little steps as I do not wish to spend months of time without seeing progress. The disadvantage of this development method is that I may need to refactor and change my code often. But then, each change should bring something new to the game.

You can see the current version on http://schedim.de

A list of changes is available on the status page.

Planned Features

• Massively parallel dungeon runs - send your character along with some friends (but be careful, for only a true friend will take care of your char and not feed him to the dragon...)
• Community features (messaging, guilds)
• Flexible Items (enhance them with runes, spells, gems, curses and blessings...)
• Ironman Challenges - can you fight without healing potions or win without selling any stuff? Perhaps your aim is to destroy a hundred pagan altars?
• Bounty hunting - your character was killed by a damned Lichking? Set a bounty for the bastard and regain some experience points when the first hero kills the next undead beast.
• ... what do you want?
  

Technical Background

Little Goblin is written with the Grails framework. Currently it is hosted on a windows server with jetty on the backend and an apache in front.

I have not yet decided if I will stay with Jetty and Windows, as this setup does not seem to agree with Grails - it is a huge pain to deploy. (Spending half an hour after uploading a new version to debug strange error messages which suddenly go away without changes to the code is not fun).