Actually, re bluescale, I think I kind of figured that out: it can be psuedo-controlled, it's based on the number of on pixels in each column. The more in each column, the closer the column gets to black-and-white. When there are ~5 pixels off, it looks like B/W, but only in that column. Nothing fancy, but it might be good for effects and such.

Wut? Serious observation in ridiculous discussion? Okay then, how about replacing Solver with WFRNG?

Don't diss GM! So long as you're not using drag/drop actions, it's actually quite nice. Saves you the trouble of writing structure code so you can get to the fun stuff

I'll download this as soon as I get the chance.

You keep on trying to sell me on weaponized cookware lowest weapon speed EVER

(Although I suppose it makes more sense than Fire Emblem, where silver weapons have 20 uses even if you miss and deal more damage than any other weapon type even though silver DOESN'T MAKE FREAKING SENSE AS A WEAPON MATERIAL.)

(also, FE8 Ephraim Difficult is total bullshit. This freakin' undead pirate ship's been kicking my ass for the past seven hours now. That's right, I've been trying to beat this one chapter for seven freaking hours.)

That said, I lol'd.

Deep Thought, you make some very good points and I hope you're right.

If it's just for enemies moving around, what I did in Zelda Dark link quest is something like this:

While 1
<other code goes here>
0->F
If F=0:Then
1->F:Move enemy in your direction
Else
0->F:Move enemy in a random direction
End
End

That ensures the enemy won't move towards you too fast, but will still somewhat tries to touch you.

For bosses, if for example hitting the boss causes him to act differently, I just change a variable when hitting him and the code launched every loop depends of the variable value.

Though if you're using coordinates multiplied by 16 / 32 / 64 or whatever, this obviously isn't necessary.

All of my other projects, save composing for Tsukasa, are out of the way. I am now attempting to convert Cubes to an APP. Unfortunately, Axe 0.5.1 seems to break compilation even in normal mode: instead of fixing it, I'm downgrading to Axe 0.4.8 and resuming development. Hopefully I can get all the interface tweaks and error checks coded soon, and if I poke my level designer hard enough maybe he'll make some more levels. Basically, after four years of off-and-on development, spanning multiple languages and more than one name, the project is nearing completion. I'd like to thank everyone who's brought it this far: your kudos and suggestions helped keep me motivated to continue. So, without further ado, the features that will appear in the first full release:

TL:DR; It's almost finished, here's what's left:

EASY + LOW PRIORITY
New splash screen
Improved feedback during editing (current tile, flash matching teleporters) DONE!
Level and levelset descriptions

EASY + HIGH PRIORITY
Bounds checking on level size
Level buffer creation (allows creators to surpass ~700-tile size limit)
Better handling when no levelsets are present/ DONE!

HARD + LOW PRIORITY
None

HARD + HIGH PRIORITY
RLE compression for external levels (and the editor changes this entails)
APP conversion using an external buffer (which requires me to manually change roughly 150 offsets, ENGAGE RAGE MODE)
Better scrolling through levels in edit mode

1.5 weeks. Okay. I can do that. No problem. Easy as pie. Piece of cake. Generally speaking, as non-difficult as sweet pastries and/or confections. You can't see me right now, but hopefully I've managed to convey the hyperventilating, ultra-panicked state I'm in right now. If not...


Well, I guess I know what I'll be doing this weekend!

Oh, and when I tried to do a piano version of the title theme, this was the result... so I'll likely be finding some new VSTs soon or actually getting a legit recording setup.