Hello Everyone! Welcome to the 6th GiTD of 2020, the world is a little crazy right now (well, more than a little) but that doesn't mean we can't make some games and spread a little joy. So let's take a look at the blueprints board and see what takes your interest this month?  We've still got 7 intriguing blueprints left to pick from, so choose the most interesting looking one, drop your vote down below and i'll see you all back here on the 12th to start the jam! PS - I will be giving another copy of Retro Vaders: Reloaded's DLC away to the winner (assuming it's not a repeat winner) # Key Dates **Theme Selection / Voting Time:** Now until June 12th **Theme Reveal & Game Development Begins:** June 12th **Game Development Ends:** June 22nd

#11

#11

Guess I'm shooting for #11 too.

#10 because I'm curious what that is.

I vote **#10**! timer-based games are not my strong suit, and that's what 11 looks like, so let's even it up a little.

voting for #11!

# #10

Much as the mischievous side of me wants to keep the tie, I actually have had a concept that I've been wanting to make into a timed game for some time. So I'm going to vote for 11. :)

I'm going to enter this one for real this time, I swear! I vote #11.

I'm having a bit of a debate on which engine I should use for GITD. Engine A is an engine that I know. It is good for paticular types of games. Its web implementation can be slow. Engine B is less familliar. Although it is designed to be intuitive, it has quite a few quirks that I'm not used to yet. Its web implementation is smooth. Engine B has better performance overall, but I would be able to get more work done with Engine A. I want my game to make a good impression. Which engine should I choose?

> *Originally posted by **[senshisun](/forums/1021798/topics/1912532?page=1#13407372)**:* > Which engine should I choose? Quick (ish) game jams like these allow you to learn and try out new things. Is Engine B something you'd like to learn/use more in the future? Then this might be a good time to see what it can do. Remember, since your game is going to be made in only 10 days, you probably won't be doing too many fancy things in your game. This'll allow you to get a hands-on approach on where everything is in the engine, and some of the basics on how its used. You might want to do a quick tutorial before the GiTD starts though to at least get the fundamentals down. Of course on the other hand, since Engine A is something you're familiar with, it'd be easier to make a "larger/complex" game since you already have an idea on how to implement it. It all comes down what you want to get out of these next 10 days. Do you want a well polished "complicated" game and maybe a bit of learning along the way? Engine A. Do you want a more concise game that may be a bit rudimentary but you learn a lot such that making games is easier in the future? Engine B. Having said all that, don't decide just yet. First wait for the theme to be announced and come up with your game idea. I don't know if there's a 2D vs 3D difference between the 2 engines, but like I said earlier there may be implementation differences that would cause you to prefer one engine over the other when you have a more specific game. Another idea: You could make the GiTD game in Engine A, so you can do the competition with an engine you know, and itll be polished. THEN, once it's all done, you go to Engine B and you try to remake the game as best as you can (you can even give yourself the 10 day time limit if you want). Seems like the best of both worlds, but you would essentially be duplicating your work. But that's a small price to pay for learning a new engine. :) And since I'm here,** I vote #10**, because I have no idea what it is!

> *Originally posted by **[say892](/forums/1021798/topics/1912532?page=1#13407403)**:* > Having said all that, don't decide just yet. First wait for the theme to be announced and come up with your game idea. I don't know if there's a 2D vs 3D difference between the 2 engines, but like I said earlier there may be implementation differences that would cause you to prefer one engine over the other when you have a more specific game. Good point. At this time, we don't know what the theme is. There are definitely major implementation differences between the two engines. No matter what I'll choose, I'll be able to learn and have fun. That's what jams are really about.