I'm really curious about why this is happening.
Notes:
- This still happens if someone joins a game with a death sound, leaves, removes it, and returns to the game.
- This stops if someone with a custom death sound joins a game, then leaves and doesn't return.
- The effects are the same on both the desktop site and the mobile site.
I don't truly understand what I'm looking at here, so I could be completely off-track, but I looked around in it anyway and made some guesses: view-source:https://epicmafia.com/javascripts/m/mafia_game.js?1480274549?1480274549
Does everything get processed linearly?
I saw there's a lot of instances of things like "player", "user", "color", etc. after "deathsound". Does it get stuck trying to find the user's audio clip and just not load anything more?
I see a large cluster of "audio"s above a bunch of platforms and browsers, followed by audio formats. Are different browsers granted different accommodations or specifications so that they're able to process and play audio properly? Could it be that the Puffin agent just needs to be read and matched to the correct method of audio processing? In that case, why would death sounds need special accounting for when it's never had an issue with any other sounds?
Standard game sounds appear to be mp3s. Are death sounds left as uncompressed wavs? Is it looking for the wrong filetype or something?
In any case, I'm tempted to struggle with other browsers just to have this as my death sound now: https://epicmafia.com/sounds/death.mp3
Notes:
- This still happens if someone joins a game with a death sound, leaves, removes it, and returns to the game.
- This stops if someone with a custom death sound joins a game, then leaves and doesn't return.
- The effects are the same on both the desktop site and the mobile site.
I don't truly understand what I'm looking at here, so I could be completely off-track, but I looked around in it anyway and made some guesses: view-source:https://epicmafia.com/javascripts/m/mafia_game.js?1480274549?1480274549
Does everything get processed linearly?
I saw there's a lot of instances of things like "player", "user", "color", etc. after "deathsound". Does it get stuck trying to find the user's audio clip and just not load anything more?
I see a large cluster of "audio"s above a bunch of platforms and browsers, followed by audio formats. Are different browsers granted different accommodations or specifications so that they're able to process and play audio properly? Could it be that the Puffin agent just needs to be read and matched to the correct method of audio processing? In that case, why would death sounds need special accounting for when it's never had an issue with any other sounds?
Standard game sounds appear to be mp3s. Are death sounds left as uncompressed wavs? Is it looking for the wrong filetype or something?
In any case, I'm tempted to struggle with other browsers just to have this as my death sound now: https://epicmafia.com/sounds/death.mp3