Could you describe in detail what you're doing to export to HTML?
What browser are you using? Are there any errors visible in the JS console?
What version of Decker are you using?
I'm saving the deck as an HTML file through the "protect" or "save as" function.
I've tried it on various browsers (Firefox, Opera, Chrome).
It's Decker version 1.22
I've noticed that when I open the deck in the WEB version of Decker, my cards just break—everything is ok until card #29. Further cards are empty, and all their content (widgets and images are mashed into two last cards. I'm attaching screenshots (from Firefox).
Sure. Uploaded on my Google Drive:
https://drive.google.com/file/d/12NOJVtMrx9ZNP9pVGqJMq4SKZpayk5H3/view?usp=shari...
I believe I have identified and patched the issue. Your card naming-scheme hit a nasty edge-case in web-decker's deck parser.
The version of web-decker on beyondloom (http://beyondloom.com/decker/tour.html) already includes the fix, so if you clear your browser's cache you should be able to import a deck there and re-save from it as an HTML export.
2 years ago(+1)
Patch definitely worked in the way that now the deck doesn't get ruined when opened via Web Decker.
But exporting still didn't work. Renaming all of the cards also didn't help,
Eventually, I figured that the problem was in the first card's script. I wanted it to play a sound file on a loop during the title screen, and this made HTML file unplayable for some reason. Deleting the script solved the issue. I attached the sound to the "begin" button, so it's a decent compromise. :)
Thanks a lot for the assistance!
Ah, I see. It was possible for a background loop to be queued before Decker had set up an audio context. Fixed.
It's generally not a good idea to have background sound on the first card of a deck, because web browsers will often block audio playback until a user has "interacted" with a page, but Decker certainly shouldn't crash if a script attempts it anyway.