Hello and welcome!

You’ve had some good tips there already from @Walop@sopuli.xyz but I definitely want to emphasise the “have fun” part! Pace yourself, ask for help when you need it, and if you start to feel like you’re burning out and losing the fun please take a break.

If you get something submitted by the end, great, but if you overrun a little bit you should still be proud of what you made.

The biggest advice I have, which you’ve probably heard before but it bears repeating, is to make something small. When you think you’ve whittled down your idea to the simplest it could possibly be? Simplify it some more. Remember if there’s time left at the end of the jam you can always add more stuff, but overscoping from the start will stop you from finishing anything at all.

And on that note! Get a victory condition and game ending in as soon as possible. That way you’ve got a full start-to-end experience that could technically be submitted and would work, even if something unexpectedly takes you away from the jam.

You didn’t say which engine or anything you’re planning to use but on a jam-specific note, in their Discord you can ping mentors in each engine with e.g. @unity or @godot if your fellow jammers aren’t able to answer something you’re stuck on. I’m in there too (same username as here), technically only a Unity mentor but I’ve been learning Godot so will be keeping an eye on questions in that too.

Oh and p.s. we’d love to see what you make! You can update here, or I’ll be starting off a weekly “what are you working on?” thread so keep an eye on that too 🙂

And p.p.s please use version control.

Just have fun and publish anything, no matter how silly it feels. My advice would be more about the preparation:

• Choose and familiarise yourself with the tools, so you can concentrate more on the game and less learning the tools
• You don’t have to do everything from scratch, premade assets and reusing your own stuff is not cheating
• manage your expectations, go through the lower rated entries of previous jams to see what other people have managed

Re-iterating TeaHands and Walops points. I think for me the biggest one is to start small. Like…pick something small, and then go smaller than that. I find that it can be useful to set a bronze/silver/gold endpoint for yourself:

• Bronze is something you are sure you can complete in the time frame.
• Silver is where you think you can get to if you really push yourself and nothing bad happens
• Gold is where you can go if everything goes right all the time.

This can help with motivation, because “failing” can often make you stop working because you de-motivated yourself, but not quite reaching your furthest estimation is motivation to push yourself.

Also something to keep in mind is that if you don’t make your bronze goal at first, this just means that you have a skill that needs to be improved: scoping. This is something everybody struggles with. I have been a professional gamedev for 10 years and I still scope things to how I think things should go, or I scope time to “feature-complete” (ie it ticks the all the boxes it was supposed to), but not “complete” (there might be bugs, the art doesn’t look right/etc…)

Also, version control is super useful, not just for tracking down bugs as Walop called out, but also for motivation. If you commit at least one thing at the end of everyday, you are basically keeping a journal of your work. This can be useful to look back on and realize even if you feel like you didnt get that much done, you can go back and see “hey I actually did all this stuff over the last week!”