Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics


A member registered Apr 08, 2020 · View creator page →

Creator of

Recent community posts

(1 edit)

It looks like this is the same error Dave encountered in the comment below. I posted the fix there (change instance_create_depth to instance_create_layer or adjust the Muffel script the other way around, refer to the comment below for more details).

I‘m not sure yet how to fix Muffel to allow both of those functions to be used, might have to look into it later.

Hmm, did the object get deleted by any chance? I think I have a check if the object that’s executing the code still exists but I may have missed a check somewhere.

Alternatively, how do you create the object? You might have the same problem the other commenter had. 

If you still have the old code with the bug, you can send it to me at 

For completeness' sake: The bug probably occurs when using "instance_create_depth" which adds a new layer for that specific object and Muffel can't find it (due to limitations of GM). I have not heard back from Dave if this resolved his problem yet, but I would be surprised if not. If anybody else has the same problem, feel free to contact me! Here is the fix if you want to try it for yourself:

Either use "instance_create_layer" instead of "instance_create_depth" in your own script, or do the opposite in the Muffel script (replace "instance_create_layer(0, 0, layer, obj_muffel)" with "instance_create_depth(0, 0, 0, obj_muffel)")

Thanks for the report!

What I can gather from your error log is that the object which is calling the "execute after 60 frames" was deleted/destroyed in the meantime? I thought I caught all errors of that type, but I might have missed a checked somewhere. I will look into it and update when I find the error.

It would be really helpful if you could share your project with me, so I can debug it faster (you can also create a new project that reproduces the same bug). You can reach me via ribbyteapps at-symbol

If you find any more bugs, feel free to report all of them.

Sorry to hear that! We tested it on some computers and old phones and it was mostly working fine - I think it's the physics that's problematic for some devices. Thanks for the comment though!

Glad you like it!