Slime Salad

On my second attempt I got the good ending with a 2-3 minutes to spare; I'm mostly able to hit the correct button now! (And I didn't play for 15 minutes the first time, but I was nowhere near beating it regardless.) How does the scoring actually work? I was disappointed that I had a max combo of 37,...

Thanks for the present and Merry Christmas :) Yes, this looks fantastic, and is fun too. Though actually I'm very bad at it; with some more practice maybe I'll be able to map colours to fingers without looking at the bottom of the screen! (Foxley: I'm pretty sure the variable and maybe sometimes imp...

The low framerate does have the draw-back that movements are far less smooth than they would be at 60fps. A lot of players who play high-framerate game will notice that. I want to add an option to run the game logic at 18 fps, but draw the screen at 60 fps so everything is nice and smooth and walkin...

Umm...hi. I'm very new to the community. I mean...I've been lurking for nearly a year...but this is my first attempt at actual contact. @.@ Welcome! Feel free to ask questions or advice. Sorry for the slow reply. Pixel art definitely isn't easy, since it's so different from other media that you sta...

OK, now I understand. I thought you were talking about the parallax effect on Troll Mountain in Wandering Hamster, but you meant the introduction. Creating a backdrop slice is easy: variable (handle) handle := load backdrop slice (5) # backdrop 5 Backdrop slic...

Yes, you can use backdrop slices instead of map layers to create the parallax effect. An easy way to do that is to just parent one or more backdrop slices to a map layer, then you can just use the Fake Parallax script normally. (It's also possible to parent them directly to the Map Root slice, then ...

Wow, Axe Cop. I don't have time to commit to a big project like that, but hopefully you'll find someone. However, I don't think the OHR is terribly suited to that type of game (unless those graphical limitations are what they're looking for anyway, I guess); if you want someone else to do the progra...

That scrolling effect is called parallax. Some day hopefully it will be built into the engine, but in the meantime you can use a script which manipulates the map layer slices to create that effect, available on the wiki here . (It's called "Fake Parallax" because it's not a builtin feature...

Yes, I guess you can skip using setparent, as long as you load the walkabout after the backdrop, so it will be drawn on top by default. The other command you need is freeslice (or equivalently freesprite) to delete the slices afterwards: variable(sl, sl2) sl := load backdrop ...

Wow, a major update after six years. I wasn't expecting that! I remember that this game got criticism for still being a 'joke game' despite a lot of work being put into it, but I seem to remember (from 6 years ago) that it was fun and impressive, so would give it another go (maybe for the 2016 in Re...

Actually we do have nested scripts in HS, using the subscript syntax. They are lexically scoped but can not yet form closures, because there is not yet a way to obtain a reference to a subscript (and the main reason for that is that it requires garbage collection). A lambda expression by definition ...

'Test Game' will only show you script error messages. Aside from script errors, most possible engine error conditions (including most errors when reading data from a file) will only get printed to g/c_debug.txt and are never shown to the user regardless of any settings, unless they're really bad. Er...

It went away when they upgraded Android?? That's odd. Maybe the upgrade caused the game to upgrade to 1.4, or to clear temporary files. Or maybe it indicates that the problem is due to a bad memory access bug, in which case changing anything at all would easily change the behaviour. Upgrading Androi...

Ah, great!
When you make a typo when writing code anything could happen; the only way to figure it out is to figure out what the code is doing, e.g. where the "craft_charm_dog" script was actually getting called from.

There is something strange with the resolution, since "get_screen_size: true screen size 1179x661" gives the size of the screen without subtracting the task bar, but it is meant to be subtracted from "Desktop resolution: 1179*661". Maybe Windows has been set to scale up the scree...