Right now we base iterations on framerate, which has proved to be the wrong way to do it. We're going to work on making it time based.
Yup, I changed the license.
That's a valid criticism - I don't know how it could be fixed. Maybe more colors could be added? Game balance has been really tricky with this game, as changes play out very differently on mobile devices and "real…
That'd be great! We were thinking of doing that for the homepage, but didn't find the time. I'd happily merge it in if someone were to make an AI for Hextris.
We thought about adding that, but we weren't sure where we'd put it - any ideas?
The iOS version is essentially just a static website inside of a webview. Since we only use paths to render the shapes, Hextris doesn't require too much space.
Hi, I'm one of the main developers of the game - I just made an issue for that on GitHub. I'll try to address it later this weekend - thanks!
Right now we base iterations on framerate, which has proved to be the wrong way to do it. We're going to work on making it time based.
Yup, I changed the license.
That's a valid criticism - I don't know how it could be fixed. Maybe more colors could be added? Game balance has been really tricky with this game, as changes play out very differently on mobile devices and "real…
That'd be great! We were thinking of doing that for the homepage, but didn't find the time. I'd happily merge it in if someone were to make an AI for Hextris.
We thought about adding that, but we weren't sure where we'd put it - any ideas?
The iOS version is essentially just a static website inside of a webview. Since we only use paths to render the shapes, Hextris doesn't require too much space.
Hi, I'm one of the main developers of the game - I just made an issue for that on GitHub. I'll try to address it later this weekend - thanks!