Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+2)

I'm impressed you were able to get some much content in the span of this game jam, really great job. The artwork and use of sound effects / music was wonderfully done. I thought it was an adequate challenge, and the linear story line kept me engaged.


I did have a black box appear during every "banish" phase that was a little jarring, but maybe that was a browser problem. Here is a screenshot:


Thanks! yea, our secret, apparently, is No Sleep. Glad you enjoyed the challenge. Adequate is the perfect word. On one hand the game is trivially simple once you've practice a bit, but on the other hand, it seems kinda overwhelming at first.  Balancing jam games has proven to be very difficult.

We've never seen that particular graphical glitch so that's somewhat concerning.   We mostly used Chrome browsers.  If you don't mind sharing the browser and/or OS, I'd appreciate the info.  Definitely hope it's isolated to just you (sorry!) but I'll fire it back up and see if I can figure out what's going on.

Thanks again for playing and for the feedback

"our secret, apparently, is No Sleep." : Lol!

Good News! we may have figured out your graphical glitch issue!  This appears to be a WebGL issue. The textures for the banish trick are HUGE (> 9000 pixels.  blame bad jam design decisions!).  WebGL has a value called: Max Texture Size. Often this is set to 16384 pixels, but we've noticed that sometimes this value can dynamically change. You can see the current value for your browser by heading to: https://browserleaks.com/webgl.  If the value is 16384, you'll be able to play OK. If the value is 8192, then it won't load properly.  The weird thing is, we've seen it at 8192 (causing the black box issue) then if you close all browsers and applications and open a fresh browser, it goes back to 16384 and the game plays fine, so while The Internet says this is a value set by the GPU, it seems like that value can dynamically change.

So one solution is to just close all applications and reopen everything. Or play a downloaded version. 

Anyway, sorry for the issue back when you ran into this but at least you'll know what the issue might be if you run into anything similar in the future.