Are you using the code in a script-entity or elsewhere?

EDIT: Ah, and the name of the function has to be set in quotes. Corrected my code above.

use GameMode.fadeIn(color, length) GameMode.fadeOut(color, length) e.g. function fade() GameMode.fadeOut(0,1) delayedCall(self.go.id, 5, "fadeBack") end function fadeBack() GameMode.fadeIn(0,1) end You might want to think about disabeling the champions during the five seconds of black? Then use Game...

And I already had to leave out a whole tileset, some objects and a few other monsters...

ratman wrote: ↑

Sun Feb 28, 2021 2:18 am

sure, this weekend sounds good

done

This is another collection of assets originally built for Grimrock 1 that now got converted for the Grimrock 2 scripting system. Included are a lot decorations, breakables, some rune symbol locks, 16 kinds of monsters, several new items and also the Cows on Wheels mini-game by antti. In addition the...

I can't remember, where exactly I bought my game, but it included no key. I have one for LoG1, but not for 2.

Sometimes a script or an object can produce effects on a wrong level. e.g. when you reppell something on a certain square but forgot to query also for the right level. Maybe something like that is going on.

Good point, maneus.
I've in addition thought if anything with other custom objects may cause the problem. Maybe one has a door component or a ProjectileCollider. Maybe with an offset.

A good way would be to delete all objects one by one and see, if anything changes when doing it.

Not all have responded. Wallasaurus did.

And, yes - I'm going to release the pack. At the weekend?

Wa? The not present minimalSaveState should keep a door from being not in the state you have left it. Every door stays open or close as it was when reloaded. Concerning the lever: I'm a bit lazy at the moment to write a script, but if you use the onActivate hook in its definition, you should be able...