Slime Salad

Day 7 & 8: Crikey the contest is getting on! I don't think I've slacked off this much on a contest game in years. I basically refuse to do anything without having a plan. What I said on day 4 about being able to start was a bald-faced lie. So I've been reading/watching a mountain of board game ...

I hope that's a joke ... I would rather just submit by the original deadline, and I basically wanted to pretend it was a one week contest plus allowance for discussion and speedbumps.
I agree with Hawk that longer contests lead to worse turn-outs and more drop-outs.

Day 6: Was a busy day today, so no free time for the game. Going to bed early to catch up on sleep. I'm moving house over the weekend and won't even have internet access for several days, so the plan is to get the game playable in the next few days and then we can add in content/graphics over the w...

Those look great!

Are you using sliceatpixel/findcollidingslice? If so, maybe there are some slices left over from a previous screen in the same location, which are "hiding" the intended slices. (Recall that sliceatpixel/findcollidingslice return the bottom-most slice).

Hmm, an argument to findcollidingslice and sliceatpixel to ignore invisible slices would be nice...

Day 4: Some back-and-forth discussion on the game design. Reached the point of being able to start on the game in theory, although pretty much every detail is up in the air. Searched around the net for reference material. Day 5: Today I actually worked on the scripting for some hours, as well as re...

That's a good idea! The visibility of slices can easily be updated every tick based on tags.

Foxley, if setting a slice to invisible instead of deleting it would solve your problems... then it sounds like it would solve your problems regardless of how you set it to invisible.

Wow oh wow. I'm not fond of the grid pattern of the trees, but otherwise it's great. But I'm not sure how to read that that bridge; is it a rail line? The scale of the stone steps (and cliffs in general) also seems absurd, maybe it's not intended to be on that tileset? Day 3 : This was one seriously...

That basically is the best way to script it. Actually, I'm glad to see someone finally make use of being able to write $1="" as a script argument.

Ah, good point. But that still results in the cursor being underneath textboxes. So instead I added move slice above (cursor, lookup slice (sl:textbox layer)) Note that some things (menus and strings) still aren't drawn using slices, they're drawn above the sl...

Distracted by a lot of other features/bugs. I'll add the command if you still want it, otherwise I'll simply wait until later.

Hey, you lot forgot the dev logs! I guess this is approximately the morning of the 3rd full day in many time zones. Day 1 & 2: Have been slowly discussing ideas with Ichiro via PMs, but this time I have very little in the way of ideas; he's provided some breif snippets but doesn't seem confident...

Regarding the hitboxes, I had thought enemies had a child on each side, but I see now in the slice debugger there's only one. That's normal, but means the script can be quite a bit simpler (using findcollidingslices instead of two nested while loops). I don't know why you used "seed random"...

Heh, looking at the screenshot I have no idea how it works!

Well come to think of it, mouse-only (not keyboard) is more interesting because those games are likely to be playable on a smartphone. Which is the whole reason that James was tagging them. So maybe we could rename "mouse supported" instead to indicate the other games with mouse controls. ...