itch.io

Thank you!!! So glad you enjoyed :D

Thank you so much for reading, glad you enjoyed <33 And thank you for the heads up re: the Decker file!! It was working alright for me locally but I will review and see if I can improve it

thanks so much for reading!! <3

thank you for reading :')

Thank you for reading!! Glad you enjoyed :))

Thank you so much for reading, glad you enjoyed! <3

thank you <3

super gratifying to read this - thank you so much for playing :') elite username also

Thank you!!! Loooove Of Piers & Bays, can't wait to read Celestial Counterfeiter <333

thank you so much :')

Thank you!! I'm really glad to have been able to work in Decker for this, so many neat features and interesting limitations to explore

Thank you!!! <33

Thank you!!! <3

Thank you :)))

Thanks so much for making such a great program!!! It was an absolute blast to work with, so intuitive with just enough restrictions to encourage creativity.

Thank you so much for reading!!! Glad you enjoyed ^_^ I wonder some of those same things truthfully! Someday I'd like to revisit this world...

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

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?