Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(2 edits) (+1)

Hi, I noticed a discrepancy in behaviour between native decker and exported HTML decker  and was wondering if anyone knew why.

Basically wanted a looping sound to play “on view” of the very first card in the deck:

on view do

play[“sound1””loop”]

end

In native decker, this seems to work. I believe I also got it to work in web decker directly. But I am finding in a web decker protected export from native, it only plays the sound once (and weirdly, after clicking into the deck). However, if you do it as a second card you view through some other trigger, the same  code works in web / native.

Are there a special considerations for doing “view” actions on the very first card? 

Many thanks in advance if anyone knows…

(+2)

As a general rule, web applications are not allowed to start playing sound without user interaction. Web-Decker attempts to start its audio subsystem when the user first clicks or types on the keyboard. It's possible there's some additional inconsistency in behavior, but what you're describing sounds to me like normal webapp sandboxing constraints.

(+2)

Ah thank you that would explain it!