Skip to main content

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

Looks very interesting!

Just went through the tutorial so far, but encountered some issues:

After throwing first lot of dice in the tutorial, and clicking through the explanation of score multiplier, I got an error, with an interesting bit of UI for showing details and offering to copy, but copying here (or in another log view I got to somehow) did not seem to actually copy anything to the clipboard.

(It was possible to close the error and continue after this.)

In browser log:

bunch of cross origin requests blocked

Trying to get length of sound which is not loaded yet. 20260908_AlphaDemo_v0.4.83.8_ZAR_web.framework.js.br:9:117041

(Bunch of warning level messages)

CombatController recovered stalled enemy-damage flow. Reason: Damage feedback handler 'PlayerScoreCalculationUIController.RequestCalculationFeedback' timed out after 15s realtime. Context: Stage=WaitingBeforeEnemyDamage, Room='Basic Enemy Room', Enemy='Lock Imp', Round=1, Throw=3, Score=11.5, BlankedDice=0, TimeScale=1. Damage flow will continue.

(Please try my game, Lockstep Arcade. Any feedback is appreciated!)

Thank you so much for the detailed feedback!

A few other players have also encountered the issue you mentioned. Unfortunately, it seems to be specific to the WebGL version, and we’ll be looking into it further. The browser version is not currently the most stable build, so if you enjoyed the game, we’d definitely recommend trying the downloadable Windows version for a smoother and more reliable experience.

The error screen not copying the log to the clipboard also seems to be another WebGL-related issue, unfortunately.

We hope you enjoyed ZAR despite these problems, and thank you again for taking the time to report everything in detail!

We’ll also check out Lockstep Arcade as soon as we can. :)

(+1)

Maybe you know about this already, but there's a thing with browsers not wanting to do things like interacting with the clipboard unless this happens inside a click on an actual dom element. (I had to spend a lot of time working around this issue.)