I win:
window.GAMEABOUTSQUARES.Interface.completeLvl()
Game about squares
81–90 of 208 posts
Re: Game about squares
#82Advice to author. Create iOS and Android versions of games ASAP. You are just hours away from getting cloned on app stores.
I'm hoping the author is way ahead of us. If he were smart, the game should be approved in iTunes and uploaded to Google Play, just ready for him to click "Publish" the moment this web version picks up some traffic. Otherwise, Google Play will have a clone by the weekend if not sooner, and iTunes, maybe a week or two.
This requires an order of magnitude more effort
Re: Game about squares
#83The author is intentionally limiting this app to touch-only for touch-capable users. This breaks the game for anyone wanting to use a touchpad or mouse on their touchscreen laptop. The offending code (from http://gameaboutsquares.com/game.c.js , beautified): (function($) { try { document.createEvent("TouchEvent"); return; } catch (f) {} var eventMap = { mousedown : "touchstart", mouseup : "touchend", mousemove : "tou…
I use a touch-enabled laptop and come across this far too often. Even nytimes.com is guilty of this, as is Stripe Checkout.
Re: Game about squares
#84There are game stats: http://gameaboutsquares.com/statistics.html
Can someone tell me how those graphs were made? They look cool. I tried looking into the HTML code, but couldn't find the info "right away". Edit: got it. http://www.flotcharts.org/
It's right at the footer of the page, "Using flot 0.8.3"
Re: Game about squares
#85Cool. Reminds me of Boxxle / Sokoban, but adapted for touch screens. It's PSPACE to solve, right?
The levels with arrows seem PSPACE complete even. I wonder if the levels without arrows are in P.
Re: Game about squares
#86I love this kind of games. Reminds me of good ol' Sokoban. Where are the mobile versions? I'd like to play it in my iPad. Kudos.
Save it to your homepage!
Re: Game about squares
#87Earlier quoted context omitted.
Google would probably ban the developer for life. Not sure about iTunes AppStore.
Fair enough, but look at all the duplicates out there for that piano keys game or...pretty much everything. My question was supposed to geared more towards functionality. What advantage do you have making something in html5 when it's easily stolen. How do you prove it was yours first? I believe I read a blog post on HN about a guy who was cloned like this before he made it into the play store and google banned him in…
I think google cache can show that you created the website with the game first, then create a text file or something on the server that the support could access to show that you actually operate the site. If the other developer that has stolen the code can't provide a proof then it's fairly easy for the support to decide. The problem is of course that you need sane support for this to work.
Re: Game about squares
#88Amazing game, loved the stack on level 21. Made it to level 26, will have to come back and play more later. Go sell it on an app store and make some money for your time.
Re: Game about squares
#89Finished the game after some two-three hours. The last level and the 31st level were the most difficult for me. I know that the statistics page that no identifying information is showed but it would have been interesting to see some individual stats.
Re: Game about squares
#90Earlier quoted context omitted.
Any solution is on the form 12232322... where the number expresses what square to click. It's pretty easy to brute force the game from there. Sure, you can use tree search and prune the search a bit, but it's still brute force and may take exponential time for tough levels. You can also look into some of the research that has been done on Sokoban AI's.
There's no need to search all move sequences, because so many of them end up in the same game state (a game state is a combination of positions and orientations of arrows, with a cut off on positions because far away ones because don't affect whether there's a solution or not). Of the levels I saw (up to 31), the relevant board area was never more than 20x20 and there were never more than 4 arrows. So the state space…
I've written a solver that does exactly that here, it prunes positions whose blocks are too far outside the bounding rectangle: