Popping in to say you're thinking of Battle Painters: http://www.saitogames.com/battlepainters/index.htm

I enjoyed the original but always felt it was a bit limited (even as a kid) so I'd be interested to see what you do with it.

Aww yeaaaa-

That was a surprisingly fun multiplayer game, even if it was really simplistic. But I guess almost any game is better with multiple players on the same keyboard.

After a creative pause, I think I'll actually try to get this damn thing done now, by looking at it from the "finite state machine" perspective.

Besides that other game, I've actually been working more on March's project in February (which correlates with the fact that it's frankly more fun to work on). I'll make a devlog for that soon.

This is coming along pretty nicely, I love games with a strong theme that covers every detail of their execution.

Still looks quite too crude for what I have in mind, but it's all the more functional.

The best shmups come from the east. Every Extend, everything Kenta Cho has touched, Touhous

This thread has really brought out the worst in TIGSource.

I wish this page hadn't happened.

This is one of those threads that could benefit from stricter moderation, like being locked while it's not Saturday in any time zone. There's too much idle chatter, posts that quote the same images we just saw, generally things that aren't weekly in-game footage.

It lives!

http://i.imgur.com/KQr3ilb.gif

http://i.imgur.com/KNnL0mx.gif

Looks like something that should be turn-based. Like a platformer + chess thing. what

This is very 2010s.

C++ woes. A template function didn't compile, so I was told to move it into the header... which revealed some circular dependency issues... that only got worse as I started fixing them.

My ideal environment is a level editor that allows you to edit and playtest rapidly. Jetpack and N are good examples. I try to make a simple editor early on for my games that have clear levels.

But I also rely on pen & paper a lot. It's a better medium for thinking in concepts, puzzles, and themes rather than tiles.

Sketching in an image editor is quite rare for me, it's like the worst of both worlds.

Unreal World is considered a shareware classic in Finland, but I guess it's only recently started to get recognition elsewhere.

Just an afternoon cruise on an invisible spaceship.



C++ and SFML. I'm not sure if it's Stockholm Syndrome or what, but I'm beginning to like the language.

New MBV yesyesyesyeyseyyseysssss

"Worth the wait" -Gaben

I have somewhat of a "writer's block" with this project. I think this is partly because some of the rules are clumsy, so the gameplay isn't as fun as I'd hoped, and it's not convenient to make puzzles that make you think in states.

Firstly, even simple levels have pretty convoluted programs. That's not necessarily a bad thing in itself, but movement code is tedious. It feels like handling C char arrays when you really just want Python strings.

So I've been gradually taking the in-game language to a different direction, resembling finite state machines. Commands can place the bot in multiple states that have constant consequences, and each of them influences what states can be activated or deactivated. For a trivial example, you can't drop items when you're not in the carry state, and you can't carry when you're already in the carry state.

Ultimately, it has to do with spaces. Functions are spaces that have their interrupt values and return values. The language can be seen as a space containing a variety of states. In a larger sense, even a puzzle is a space, where you're supposed to get into a state where it's considered solved. It's something that I feel like I've been trying to grasp, and makes me think why didn't I approach the in-game programming like that in the first place.

In the meantime, I've already started building the foundations of March's project, because I just want to get some work done. I've reached the point where I can't view this project objectively anymore; there are times when it stops being a fun project and instead just some task I want to "get over with". Luckily I'm too much of a perfectionist to release it before I'm completely satisfied with it.

It's time to look at Control Room from a different perspective, to re-evaluate what's supposed to make it fun.

http://q-gears.sourceforge.net/gears.pdf

It's a long and technical read, but I think curious gamedevs can get much out of it.