Skip to main content

The Power of Pride Bundle 2026 — $10 PWYC Edition
On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+2)

Hi all! I've been building a visual novel in Decker using the Dialogizer module for the past month and it's been a great experience, but I've run into a sudden and unexpected problem where none of my "sleep[]" functions within cards seem to be firing properly any longer; I'm not sure what I might have done or what elements might be clashing to cause this. I'll give an example of the usual code structure I'm using on individual cards below:

on view do   
    dd.open[deck o] 
    dd.say[source.value] 
    dd.show[0] 
    sleep[30]  
    dd.show[1] 
    dd.say[source2.value] 
    dd.close[]
    go[drawer2 "Dissolve"]
end

While this string was working fine for me when I first started creating the deck, now Dialogizer simply fires immediately to "source2" after playing "source" without pausing as I would expect it to in tandem with the "dd.show[]" command, and it's a problem that persists through the entire deck anywhere I've used "sleep[]". Has anyone encountered an issue similar to this before or know what might be causing it?

(+1)

Is it possible you've named a card "sleep" or defined a function in the deck-level script that likewise shadows the built-in sleep[] function?

Normally if you type "sleep" in the Listener and evaluate it with shift+enter you should see a response like

on native x do ... end

If it's being shadowed by a card you might instead see "<card>", for example.

(+2)

YEP, that was the problem, I had named a miscellaneous card "sleep" without considering the ramifications - thanks!!