I don’t know why an entrepreneurship forum would downvote somebody for linking to their topic relevant tool. People need to share their projects and products somewhere. It’s a good opportunity to discuss things around the ecosystem if nothing else
Woah, throwback. Construct 2 is what got me confidently interested in programming, and I'd argue that it's a key reason I'm a Software Engineering major today.
If you've never tried programming a game I would highly recommend it. There are many aspects that make a game a really interesting challenge: input, rendering, sound, and managing large global mutable state. Ludum Dare is a good excuse to dip your toes in.
Especially once you realize the difference between super purpose drive micro game code (a big event loop with lots of variables at the top) and game code with well designed scaffolding (entity component systems, etc). I think everyone is destined to make at least one gobbledegook game before they can appreciate all the benefits that a well designed system brings. I recommend pico-8 or similarly designed constraint driven virtual consoles to maximize the learning experience.
LD doesn't help learn any of this. The time constraints force most entrants to use Unity, GameMaker, or some other framework/engine that abstracts learning about any of this stuff away.
If your object is to learn, better to try out Handmade Hero, entirely from scratch: https://handmadehero.org/
If you think using an engine means you're not going to need to worry about these things, you're going to have a bad time. Make games, not engines. If you want to make games, make games, not engines.
I agree that LD is not the right time to learn how to do pointer arithmetic, or how to draw a pixel.
What the time constraint teach you is to adjust to a time budget. Wear many hats. Improvise. And Finish Stuff.
All very valuable lessons that will help any developer.
There's a healthy and beautiful spectrum of tools and languages out there between the "all included" of Unity and the aridness of plain C. Have you tried Löve? It abstracts a lot, but a lot of what it abstracts is really not that important for making games, in my opinion.
I've done all of those things every time I participated in Ludum Dare, and I've used a game engine only once. The time constraints make you pick your battles. You have to pick technology you're fluent in, but there are great input/output libraries for games for literally every language out there. I picked Javascript, and even did one in 3D with a procedural audio track that was affected by the plays.
One time I decided to make a multiplayer game on a hexagonal grid. Just getting the hexagonal grid working took me over half of the time, didnt produce much of a game at all that time, but it was still fun, it's ok to fail.
This comment is wrong. You still learn all those things using a game engine. You don't have to write your game in pure C and handle everything from first principles to learn how to manage those aspects of game development.
Making your own engine is definitely a good learning experience, but it’s not required for making a game. Game engines are tools for making games, they don’t make the game for you.
You don't even have to "make your own game engine" - often you just take a windowing library, optionally with some barebones renderer (like SDL or Allegro) and simply make a game without an engine. This approach was very common at the beginnings of compos/jams like Ludum Dare, it only changed somewhat recently with increasing popularity of ready-made engines.
I have done Ludum dares on and off since #6. I have yet to use anything like unity. Closest to a framework would have been using OpenFL which is a Haxe cross-target reimplementation of the Flash API.
My favourite are the 10-14 day jams. You can make something really cool with that kind of time limit. I used a jam last year that allowed pre existing code to make a little playable scenario out of my projects game systems and it was wicked for feedback about game feel. Before that, made a little village builder game from scratch.
2 days though? I don’t know what I would do, its not much time
For something that feels decent enough to share the minimum for myself is three weeks. Functional and verification testing is really important, and then deployment testing after that. These take time.
I look at the experiences of Phil Strahl and I find it really interesting to see from year to year how his experiences with Ludum Dare have changed and what he has learned. It does seem like familiarity with tools is really important.
I like his joke in his Ludum Dare 45 post mortem about how his game launches, testing over, passed.
Getting older I know that having enough sleep is really important for having a beautiful day the next day. I'm not sure how compatible getting enough sleep is with a 48 hour hard limit. Looking after physical health and mental well-being seems really important at this stage in my life. I'm glad that people can get enjoyment out of participating in Ludum Dare and I know everyone's experience will be different because everyone is different. I wish generally people felt less stressed because some of the limits we place on ourselves are optional.
> I'm not sure how compatible getting enough sleep is with a 48 hour hard limit.
It's perfectly compatible I think. The difference between 8 hours of sleep or 16 hours over two days is 1/6 of the whole jam, but the difference in productivity will be much less, or even better with more sleep.
You can't learn it all in time, but with some prior programming experience, you could make something on the scale of Tetris in 48 hours. Even a tiny project like that teaches a lot about game programming concepts.
It's a pretty humbling experience to try though. Before you try it's not obvious why it would take this long, but all the little things really do eat up your time.
I don’t know about start to finish, since finishing a real game is a massive task, but it’s a good way to learn a specific subtopic of interest. My own game I figure has 16-24 months of full time work to go on it. Even though it looks fairly full featured at the moment, “finishing” it is still a huge task
I agree that large projects have different challenges than small ones.
Learning how to successfully manage and complete a large project is definitely something that needs hands-on experience and cannot be completely replaced by doing lots of small projects instead.
That said, the core process is the same and, especially for beginners, doing many small projects instead of one large one is important to become familiar with the gamedev process and get as much practice as possible in the shortest amount of time.
Been working on a 2D game engine. I haven't "show HN" it yet because there is still some work to before MVP. Sadly for LD you really need a browser game basically.feedback appreciated
This looks super cool and polished for an engine made by one person. You should put an image of the IDE higher up the readme though, it’ll help people browsing evaluate it immediately more than a bullet list of features.
When I’m evaluating an engine I also like some kind of high level overview of how games are made in it. You have some of that mixed in with more how-to levels of detail. Pulling out that high level info into a short intro will help attract people when you’re ready for more eyes.
Looking forward to seeing this pop up again on HN!
It’s my opinion that good games for these sorts of competitions start off as sketches and high fidelity random mock-ups of screenshots of interesting potential games, and then imagining what the possible game mechanics and objectives of it would be. Start with the end in mind or you’ll fall into feature creep.
I can never be sure if I can participate, real life puts many constraints on availability (and quality) of free time. But I try. I usually tweet a "game design document" on saturday evening, and try to squeeze 5-8 hours over the weekend to get something done. I always try to keep the games web based and compatible with mobile.
The "unstability" property can be added to any existing game, with the single pass of a vertex shader ;)
Some themes simply lend themselves to engendering more "creativity" than others. I knew it was going to be "unstable", because it's universally hated / feared. But was chagrined to see "One tool, Many uses". It's really the ideal theme for a game jam with time constraint. The inspiration just flows. And really the themes are vague enough to get away with anything.
I'm always excited to see what comes out of these game jams and seeing how people ship their one off game. I've noticed games with web versions typically rate higher than games with only locally executable versions (for obvious reasons). Web games being compiled into wasm also frequently handroll a lot of standard library logic that doesn't otherwise work out of the box, and I'm looking forward to seeing what they come up with.
