I am going to guess that it's minmay's "Tower of Babble".

That's very peculiar that I don't get an error with mine, but yours does. Okay, try this variation on the script: altar_1.surface:addConnector('onAcceptItem', self.go.id, "itemSwap") function itemSwap(surface, item) local checkItem = "rock" local itemReplacement = "figure_skeleton" if item.go.item:g...

Try the script as-is, in a new project; place an altar and the rocks.
*Also, what is the item that you are using?

First (and you may have already), please double check that the copy / paste was exact. I do not see this error in the editor or in the game. :o *Also, please ensure that you are running version: 2.2.4 of the engine. __________________________________ Here is the same script as above, but with an eff...

altar_1.surface:addConnector('onInsertItem', self.go.id, "itemSwap") --< change altar_1 to the ID of your altar > function itemSwap(surface, item) local checkItem = "rock" -------------------------------< Name of the user placed item > local itemReplacement = "figure_skeleton" ----< Name of the rep...

This really needs to be in the forum for your intended game; nearly all scripting advice will be very different between the two. Question(s): [Assuming LoG2] Do you intend that the user-placed item becomes something new when put upon the [empty] altar, or will there be an item already on the altar t...

For which game? (Presumably LoG2; because it's a Sky.) This is usually done via script, in a script_entity. Every object has a destroy:() method. you can destroy an object in either game, by calling the [[ object.id ]] : destroy() For example: swamp_sky_1:destroy() ___ Create (or select) a script_en...

... And for whatever reason the Grimrock 2 modding scene never attracted as many people as the Grimrock 1 one. My guess is the change to the component model for scripting; a powerful improvement, but breaks old scripts, and old habits. *I think that if they had released LoG2 with some support for i...

QuickTime event huh?

Misnomer aside, I thought those were almost universally despised, or is that just me?

This bug is result of an overlooked pair of print statements that should have been deleted; they had no conditional checks to ensure that the champion(s) in position 1 or 2 exist.

It's now fixed in the development version.