Competition Forum > Competition Freetalk

Thinking about MLGJ #2

(1/2) > >>

Lemonaids:
Now that it's totally over, we can think about what we should do again and what could be improved- this topic is intended to consolidate those thoughts.
Feel free to move it to Post Mortem if that would be more appropriate. (Those are more anecdotal about the last jam, imo).

Suggestion
My main suggestion for the next MLGJ would be to add a bug report section on the game page. My game ran fine for me, but Oracion just got a blank window. How many others had that problem? I have no idea! This applies to small glitches too; I'm here to learn as much as to have fun making a game. ;) As a developer I would love to get bug reports to help make my future games more robust.
I know there was a general comments section, but a small text field under the Twilight Sparkle rating or a button beside the download might get more people to give feedback specifically on this.

What worked well
As far as experiments that worked, ordering by number of ratings seems to have helped even out the voting, and adding the comments section was pretty good for getting general feelings about the game.

What ideas to do you all have about the next jam?

Rylius:
Great idea, I like that. Should be pretty easy to implement in the new site as well. :)

Website layout and design will be redone, I found it kinda hard to see things myself.
The voting will also change completely, we haven't settled on a specific system yet though. Open for ideas!

We'll also tie together all parts of our site. Right now there are forums, theme voting and game submission/voting, each with their own "authentication".
Besides being much cleaner and safer this also allows us to send notifications for new comments/bugs on your games.

Further comments, criticism and suggestions are of course welcome - post away!

AnsisMalins:
Google Game Jam Analytics

Have a dashboard where the jammer can see how many times his game was downloaded and by whom. Gather statistics through JavaScript: screen resolution, OS version, etc. When somebody downloads a game for the first time, have a JavaScript function spin for a a few milliseconds and guess their CPU speed from that. If their browser supports WebGL, you can even probe their graphics card similarly.

Lemonaids:
That would be totally cool. Last time, I spent too long wondering what the best window size would be.
I'd probably comment my code more if I knew it was being downloaded, too ^^'

Amiisato:
I like your information a lot.

Navigation

[0] Message Index

[#] Next page