4 ms·

Thanks. The way inactivity is handled is covered in the FAQ: https://bgammon.org/faq/#what-happens-if-a-player-goes-inactive https://bgammon.org/faq/#what-happe

Thanks. The way inactivity is handled is covered in the FAQ: https://bgammon.org/faq/#what-happens-if-a-player-goes-inactive https://bgammon.org/faq/#what-happens-if-a-player-goes-inact... You shouldn't need to wait more than 30 seconds to see a win in your history after you also leave the game. Will you please share a screenshot of the dice issue?

oldmariner 2y ago
https://imgur.com/a/bqyWblS https://imgur.com/a/bqyWblS Maybe it was the Firefox addon Canvas Blocker? That addon was crashing the game, so I disabled it and appears to work now. The game still makes my laptop fans kick on though.
- tslocum 2y ago
  Thanks. Yes, that makes sense. The web version of the game is powered by WebAssembly and renders to a canvas. The game is only able to utilize one CPU core when running in the browser, maxing that core out probably set off your fans.
  - NooneAtAll3 2y ago
    ...isn't webassembly supposed to be more efficient?
    - tslocum 2y ago
      The reduced performance is a Go problem rather than a WebAssembly problem. See this issue for more info: https://github.com/golang/go/issues/28631 https://github.com/golang/go/issues/28631
  - deleted 2y ago
    [deleted]