I think it's preferable to just file all issues directly on the GitHub repo.

BrotSagtMist wrote: ↑Wed Dec 08, 2021 1:24 pmIs there a buglist?

Yes: https://github.com/Davidobot/love.js/issues

Actually, it works with the love.js player without any arguments. I guess it does something different.

For what it's worth, I'm on a love.js version from September 2020, but the commits since then don't seem related to my problem, so it doesn't look like it's worth updating to try and fix my issue.

Hey guys. I noticed Zabuyaki stopped working with love.js (remember, it is auto-refreshed from sources, so it's auto-updated regularly). The error visible in the browser console is: "Uncaught RangeError: source array is too long" According to my tests, it seems related to the size of the g...

Nice job ! On Linux, it works perfectly on Falkon browser (Webkit based) but not at all on Firefox. The Compatibility version work with Firefox. I guess it doesn't work with Firefox simply because it's missing the required headers: In Firefox, the normal version can throw Uncaught ReferenceError: S...

Maybe Safari needs that security header thingy like Firefox does? Or does it only work in compatibility mode?

Sheepolution wrote: ↑Sun Oct 25, 2020 4:24 pm This works with LÖVE, but not with Love.js

This probably doesn't work with LÖVE on case-sensitive OSes. In other words, it probably only works on Windows. Better be consistent with your casing.

I've figured out why our canvas had the wrong dimensions when the DPI settings are not set to 1.0. It's due to the fact we used the push lib with the highdpi parameter set to true. Setting it to false fixed the issue and makes Zabuyaki behave like other lovejs games. Fix commit: https://github.com/t...

not working for me in Firefox 81.0 Thanks for reporting this. I have rebuilt the games in compatibility mode and it now works with Firefox (although the audio is buggy). I guess it's a tradeoff between working perfectly in Chrome vs working without audio across browsers. https://2dengine.com/arena/...

I'm not sure this is right. I noticed the game.js file is different, for example, as at the end of the file it specifies the size of the game, and also attaches an id to the bundle (which might be used as the client cache key, I'm not sure). By simply replacing the game.data file, the behavior I got...