Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

i havent found any culprits this way☹️ but when i remove go[card] from the script on the problematic card then the player is not sent to the first card anymore, but ofcourse then flipbook isnt moving. if im missing any other obvious thing let me know i am a noncoding simpleton

Try making a copy of your project and stripping it down to the smallest deck that still exhibits the problem. Remove all the cards, scripts, modules, contraptions, etc you can, a few pieces at a time, until you narrow down the conditions of the bug. 

In the process of removing things you might discover the answer on your own, and if not I can take a look at your simplified example. It's always possible there's some sort of bug in Decker itself.

(+1)

thanks for this suggestion! i now found that a contraption i made (just a resizable picture, didnt put any script) is the actual source of this issue.So i guess its just that the contraption and flipbook now suddenly wont work together on one card?  u can see here 

Ugh, shit. The problem has nothing to do with zazz, or with your code; it's a regression in Decker. The contraption is bubbling its view[] event to the card (which should never happen). As a temporary workaround, add an empty view event handler to any contraptions which don't otherwise do something with view[]:

on view do
 
end

Thanks for your help in identifying this issue.

(1 edit) (+1)

thanks for explaining ! &sorry to bother u on christmas😭

I believe I have this fixed; the version of web-decker on beyondloom incorporates the patch, and it will be included in the next binary release.

(+1)

This issue is corrected in v1.37.

(+1)

Yippeee!!!!