This feels just like the real game. I am just missing the predictive/"test" move that lets you see what would happen without actually moving the tiles.
I think the game mechanics are off slightly, compared to the iOS app.
I had this layout (with some other unrelated tiles):
- - - -
- - - -
1 - - -
2 - - -
And, pressed down to combine the 1 and 2, but it wouldn't let me until the column was full of tiles to "push" them together. In the iOS app, swiping down at that point would have combined the 1 and 2 into a 3 at the bottom-left position.
I hate to nitpick though. Great job overall.
edit: Strange. I just tried again and can't reproduce that behavior now.
Think I know what's happening here! My way of preventing too many keystrokes in quick succession is pretty hacky—basically, if you keypress <300ms after your last physical keypress, it doesn't fire an event. More appropriate would be to only suppress the event if it's <300ms after the last keypress that actually fired an event (vs all keypresses). Will fix ... :P
(The game mechanics should be identical to the iOS app though, with the exception of the occasional high-number tiles provided. Also in my todo list to figure out the algorithm the game uses to generate them, haha.)
You must have figured out how they score the different numbers. 96 is like 780 points, 192 gets 3500, 384 gets around 6200 points, 768 gets 22000 or so... Did you find an obvious pattern? I was curious about this but too busy enjoying the game to think about it.
Purposely made it nonfunctional (or mostly nonfunctional) on mobile devices, to not step on the toes of the original creators—they're coming out with an Android version soon!
I found it interesting that you used Meteor to build this game -- I initially thought it was a fully client-side Javascript only canvas-based game. Is there any reason for using it considering this app doesn't appear to be using any backend?
Grabbed the strategy from this article (http://www.kotaku.com.au/2014/02/tips-for-playing-threes-the...)! Basically there is a deck of 12 cards (four 1's, four 2's, four 3's) that is shuffled, drawn from, and reshuffled when the deck is empty. Originally I just had it populate randomly from the same distribution, but it resulted in a startlingly high frequency of terrible boards with like 10 red tiles floating around and no blues.
As mentioned in an earlier comment and in the article, the actual iOS game also inserts higher-number cards (6, 12, 24, ...) into the stack occasionally, though I haven't added that element to this version yet.
[+] [-] madsushi|12 years ago|reply
[+] [-] silvertab|12 years ago|reply
[+] [-] jaredsohn|12 years ago|reply
[+] [-] Encosia|12 years ago|reply
I had this layout (with some other unrelated tiles):
And, pressed down to combine the 1 and 2, but it wouldn't let me until the column was full of tiles to "push" them together. In the iOS app, swiping down at that point would have combined the 1 and 2 into a 3 at the bottom-left position.I hate to nitpick though. Great job overall.
edit: Strange. I just tried again and can't reproduce that behavior now.
[+] [-] angelaconstance|12 years ago|reply
(The game mechanics should be identical to the iOS app though, with the exception of the occasional high-number tiles provided. Also in my todo list to figure out the algorithm the game uses to generate them, haha.)
[+] [-] rileyjshaw|12 years ago|reply
I got this far (http://imgur.com/MR3lC4U) before realizing I should really get some sleep.
[+] [-] evan_|12 years ago|reply
http://js1k.com/2014-dragons/demo/1667
Such a great game.
[+] [-] damon_c|12 years ago|reply
*edit Someone figured it out here: http://bitsplitting.org/2014/02/11/threes-scoring/
[+] [-] prezjordan|12 years ago|reply
[+] [-] hayksaakian|12 years ago|reply
Should call it Threes for PCs.
[+] [-] angelaconstance|12 years ago|reply
[+] [-] nacs|12 years ago|reply
I found it interesting that you used Meteor to build this game -- I initially thought it was a fully client-side Javascript only canvas-based game. Is there any reason for using it considering this app doesn't appear to be using any backend?
[+] [-] davepeck|12 years ago|reply
Out of curiosity, what distribution of "next" tiles is produced?
[+] [-] angelaconstance|12 years ago|reply
As mentioned in an earlier comment and in the article, the actual iOS game also inserts higher-number cards (6, 12, 24, ...) into the stack occasionally, though I haven't added that element to this version yet.
[+] [-] podperson|12 years ago|reply
The simple alert at the end for the score is a bit of a weakness.
I agree about the partial slide movement testing. Perhaps hit the arrow to test the move and double-tap it to actually make the move.
[+] [-] andyhmltn|12 years ago|reply
[+] [-] jbeja|12 years ago|reply
[+] [-] kevinflo|12 years ago|reply
[+] [-] ndrake|12 years ago|reply
[+] [-] saltylicorice|12 years ago|reply
[+] [-] glifchits|12 years ago|reply
[+] [-] evan_|12 years ago|reply
[+] [-] zamalek|12 years ago|reply
[+] [-] andrewfelix|12 years ago|reply
Confusing name, I immediately though you were using three.js
[+] [-] thecasualgamer|12 years ago|reply
[+] [-] Davertron|12 years ago|reply
Great job!
[+] [-] angelaconstance|12 years ago|reply
[+] [-] n1ghtmare_|12 years ago|reply
[+] [-] robertchung|12 years ago|reply