Ludum Dare

About Team Luminous

Entries

Browser pest

Ludum Dare 33

Lenore: Dark Days Ahead

Ludum Dare 30

Team Luminous's Trophies

Team Luminous's Archive

First of all: the game!

What we did

We thought about the theme for a bit and decided almost immediately that our monster would have to be cute and cuddly. Then someone recalled the cookie monster computer malware and we realized that we wanted our game to be related to it somehow. After different ideas we settled on a monster who eats browser cookies. In the end we were quite happy with the result – we managed to completed the goals we set for ourselves and even had time to go over the code and eliminated most of the bugs.

What went well

We got a good idea fairly quickly.
Our framework was ready in time.
Two artists meant even more cool art and wonderful colors.
One of the artists also did a bit of coding, lending a helping hand where needed

What could have gone better

Maybe a little less time spent petting the cat…
There are still a few bugs we could not catch, even with those sticky cookies…

Just play the game!

Bob in his natural habitat.

Bob the Monster

This is Bob. A vicious and terrifying monster.

This is NOT an Oreo

Attention, this is NOT an Oreo. I repeat, this is NOT an Oreo. This is a Generic Sandwich Cookie or GSC for short.

Choosing toppings all five people like was trickier than expected.

Our mascot.

(And the #LudumDare IRC)

The team:

We are from a small country in the Northern Europe called Estonia.

Most of us have previously participated in Ludum Dare under the same team name at different times.

We’ll be staying together during the event and going to have lot of fun, no doubt. Will try to keep you updated as well.

Estonia

Rao

Programmer and
.gameplay designer He is the most experienced LD participant in our team. Recently converted to open source-ism. He is supposed to get our build engine working.

ervion

Programmer and experimentator. A fan of open source and liberty and freedom and all that. Can do some SVG magic; likes pushing systems to the edges of the possible.

Ether

The story writer and a professional distractor. She might not be 100% sure about what she’s doing on the team, but she’s good at it. She’ll also get involved in coding.

põssa

Programmer/artist. Has the most vivid imagination among us all. She will play a key role in our idea generation process, but only if she doesn’t decide to spend the LD petting cats.

Rei

Our artist; she made our logo. She’s amazing in art stuff, so she’ll be focusing on that. Most likely she ends up sitting motionlessly hours and hours with her Wacom creating our visuals.

Our platform:

html5+css3+js A browser based came is our choice – it’s a trend thingy
Pixi.js to make life little easier
to work together and sync stuff
Bitbucket to store the code
hosts our server

and our custom build system:

It minifies, validates, optimises, and embeds all css, js, and other assets into a single js file, downloads it while showing a nice loading screen and is generally awesome.

First of all: The game

otherdude

What we did

We made a-maze-ing game. (And a lot of bad puns as the tiredness levels neared fatal.) We found an idea that we all liked quite quickly. The concept was a maze game where the character has to navigate and do tasks in a maze that exists in parallel worlds.

Rei actually knew how to create art for the game and immediately started illustrating it. We thought out the storyline and implemented world generation. Then we started working on the levels.

In the end we almost completed our goals, at the cost of many many bugs despite of which you can still occasionally play the game.

What went well:

* We knew right away what kind of a game we wanted.

* We had art from Rei who seemed to work non-stop from dusk til dawn.

What could have gone better:

* The haste caused the code to become quite unmanageable which resulted in a lot of bugs. (Refresh often fixes most of them.)

* Our framework was not quite ready and tested in time.

* We had some issues with hardware which caused unnecessary stalling.

What will be redone:

* Bug fixes, refactoring code.

* Adding art that we forgot about…

* Complete ambitions. (And more.)

Try it out!

lenorespriteaxe01

We, Team Luminous, are officially taking part of LD jam!

Venue:

We are from the small Baltic(not to be confused with Balkan) country Estonia and for Ludum Dare we are gathering to a small town in the middle of the country, Paide, where one of the team members lives.

We are likely to be the biggest, if not the only, team to represent Estonia.

What we use(and who we are):

The Platform:

– Gotta be modern.
Because why not. It’s JQuery.
for deploy
And a custom build solution using Ant and Closure compiler that isn’t quite ready but it might get ready by the start.
– Hardcore mode! Phaser is for the weak.
Ammo.js – Physics simulation is compulsory
(If we decide to fall back to 2D – Pixi.js and PhysicsJS)
– gotta stalk our users, after all.
To implement the Analytics: node-uuid, CryptoJS
A virtual machine
for code storage