Having checkpoints based solely on location could go awry in a non-linear level like this. Ideally, the checkpoints should make sure that you're actually ready to go to that location before they trigger. That's why I added the ability to make checkpoints depend on a lot of different factors.

I think the cave is a bit simpler than it looks. The checkpoints can go awry but I don't think I can make them foolproof. I did just make a couple adjustments to them though, and I'll consider it some more tomorrow. (well, today; it's 4 a.m. )

I added some conditions to checkpoints that I think would be the most obvious problems. The event system is deeper than I thought. I'll look into using $nop to make it so that that if a tile is or isn't in a certain location then all checkpoint activity stops, and then I can program a set of what might be common errors to disable future checkpoints.

without terrain 4 it simply does not feel like a sefro cave

CaveGen might not support terrain 4 yet, but HATPCR does, so you can set it in the level file.

for what its worth i collected all the treasures and got to the top of the level, but im pretty stumped on how to get to the door

it was fun but by god i grew tired of the dynamite sounds when i did the lower right corner

Putting terrain 4 in the level file renders terrain 1. And I agree neezles, I'll change it when I can.

Thanks for playing, Isa. Regarding getting to the door:

Well, you've got to tell me these things. Apparently I only enabled terrains 3 and 4 in campaign levels. Fixed for the next version.

I didn't know it was supposed to be supported :p Forgot the campaign levels have it