Looks like it too!

https://www.youtube.com/watch?v=C3hiCKTvC0k Showed up 6 hours late and now I'm 6 hours in. Looking pretty good for the time I've spent on it.

I'm enjoying workign with these graphical limitations.

I'm using my own JSON format for the levels, so maybe I'll make a level editor too?

Now on to making levels, enemy movement, and more actions

I took a break from making core mechanics to try my hand at procedurally generating animations (stars, buildings) for my ending. I don't think it looks bad, at least.

Signing off for tonight as it's 1 AM PST.

Done: Input framework, player character art, random enemy movement, ending cutscene, some graphics, level format, level loading.

TO-DO: Audio, enemy art, more tiles, tutorial, more levels, more input, puzzles, enemy pathfinding.

Sentries will return to their post when they're done investigating instead of wandering randomly

I've sent the game out to a few people to playtest and may refine it some more tomorrow, but for now, I'm content complete!

3 hit basic combo is now animated and confirms I programmed the system correctly! Unfortunately GIFs don't have sound, but all you're missing out on is a kick drum playing quarter notes.

As someone who's done this a few times before and made all of these mistakes, some things to keep in mind:

1. Don't stay up for 48 hours straight constantly working in an attempt to squeeze out the most time. After a few hours you will lose steam; this is a great opportunity to take a few minutes to eat, make a blog post, discuss with your team (if you have one), etc. You will keep thinking and solving problems in the background and usually the main factor of solving those problems is giving yourself enough time, not working constantly.
2. Remember to stay hydrated! Always have a mostly full glass of water available. If you run low, go refill it; the trip will give you a brief break and may give you space to help solve a problem.
3. Start polishing now. If you're doing the Compo, you're already basically out of time for adding new features. For every hour you spend adding a feature, know that at least 2-3 will be spent polishing and bug fixing.
4. Scope down throughout the jam. Every 12 hours evaluate (with your team) where you are and if you'll need to cut anything. If you wanted to have 3 levels but don't have 1 done yet, maybe just make 1 level. Wanted two main systems that play off each other but aren't completely finished with the first one, maybe cut the second system and just make the one you have really good.
5. Enjoy the experience! This is supposed to be fun. If you find yourself stressing out about the deadline or a bug you can't squash, take a breath and remember that in the long run, Ludum Dare doesn't really matter, and that's kinda the point. It's ok to fail! It's ok to not know how to do something perfectly your first try!

Enemies now have internal state machines with a placeholder sine wave movement, take damage, and drop souls for harvesting.

Definitely falling behind my schedule, so I'm glad I'm working with a team for this LD to help cover level design, art, and audio. The extra day over the Compo schedule helps, too :D

https://youtu.be/pdJyNEUm7a4

We're definitely cutting some features, but that's just LD :smile:

https://youtu.be/JokMby435U4

(Splashscreen TBA)

How can you honestly check the box if the rules link doesn't work!

@pov :stuckouttonguewinkingeye: https://ludumdare.com/rules/