The thing which makes 2048 moderately easy to reason about is that incoming pieces are always "1". However, this game appears to spawn in random pieces, with random point values. I tried to follow the to-and-fro of the design blog in order to find out why this is, and I get the impression it's for avoiding getting the player stuck, but it does have the disadvantage of making planning incredibly hard. The good news is that by reading the blog I finally understood what was going on with the screen shake
off-topic: that "Subscribe to me blog" modal is not only bad UX (imho, of course), but also doubles down on the UX tire-fire by resetting my reading position to the top of the page. It's almost enough to warrant a command-w right there. Just one datum, but it for sure made me sad
I was afraid people would abandon good runs if too long, so started spawning 4 and 8 sometimes to speed it up somewhat. (There's 180-odd entries participating in the compo, so even 10 minutes of play time per entry is a huge commitment for people looking to vote on most / all games.)
Re: Subscribe popup: this is the sole reason I'm looking to migrate from Hashnode! All of their UX "improvements" are egregious, but this one surely takes the cake. I very much agree with your sentiment.
When I joined, it was a nice technical writing-oriented site, but these days it has entirely succumbed to terrible product managers. E.g. their blog post editor's main function is seemingly to upsell their generative AI wrapper.
I'm seconding the "incredibly fun" comment, but I would keep the occasional big numbers. It probably took me an hour to finish the game and I wouldn't want to slow it down further. The little extra bit of randomness/luck it adds is nice too.
When it comes to the UI, I was a bit confused about how the gameover and piece removal works. I guess if there are no legal moves it removes a piece?
Also, the multiple move mechanic where the last piece to move is automatically preselected sometimes tripped me up a few times and caused me to accidentally downgrade a piece.
The king will "kill" one of your pieces if he has no other legal moves, but only if you are not one move away from losing. I also noticed this very late, same as noticing that you only need one piece with value 1024 to win the game, because another one is already on the board ~
> a huge commitment for people looking to vote on most / all games.
I wanted to say that I went to vote for your game but they seem to only support GitHub login and their GH app does crazypants shit like "Act on your behalf" versus the much more sane "user:email"[1] or whatever which would prove that I'm a person without granting some rando website "sure, bro, take GitHub actions for me"
So, my HN upvote will have to suffice for Internet Points of Appreciation
The site only requests read access to your email, as the login flow message _actually_ shows.
The "act on your behalf" statement is GitHub's standard message for all GitHub apps, regardless of whether they actually ask to be granted any permissions that would let them perform such actions. There's a "learn more" link right at that statement, that would've explained pretty much exactly this. I find it curious that you bothered to venture into docs and link them, but did not bother to click _that_ one to understand what's actually going on.
It says, i.a.: "The GitHub App can only do things that both you and the app have permission to do.". Since the site only asks for read access to your email address, it cannot actually do anything else. As simple as that.
I hear you, and it's possible you're right, but that's not what the dialog said and the very link that you mentioned has -- as its very first sentence -- "Once you authorize a GitHub App, the app can act on your behalf." and shows an example of commenting as me
So, I guess just to vote on a cool game I should definitely roll the dice with my github account and trust that some Internet comment is right, or, I guess upvote and be sad for them that they tried to be kewl by creating a GH app instead of oauth2 like a sane person. Naming it "Kilobot" for sure inspires confidence for its fewer than 1k installed users, too
Once again, curious that you bothered to remember something that is relevant to community inside jokes and take dumps on that, even bothered to remember a number, but did not bother to read up on what you're dumping on.
FYI #1 It very much is a standard oAuth2 flow. Just GHs 'always on' message is unfortunate, and that's all there is to it.
There's been topics like https://github.com/orgs/community/discussions/37117 on this ever since they had been introduced. Which, again, you could've encountered if you put your energy into good faith, instead of focusing that bad faith mojo on a small community. If you really feel like proving how "sane" and above "kewl" you are, go take your dump on GitHub - i.e. the one actually responsible for those misleading messages.
FYI #2 Your vote would not count anyway, because only community member votes actually get included in scoring. Although as an outsider you'd been welcome to leave feedback.
I didn't have to "remember," they're on the tab right next to this one. I'm sorry you're butthurt about someone wanting to vote who isn't a part of the l33t insiders club. Anyway, right under the game in question it says "Voting for this edition's games is in progress - sign in to vote on this game." so how would any sane person know that it's only for insiders?
Sorry I raised your bloodpressure about something that doesn't matter to you since I'm an outsider. I'll send you virtual flowers using my totally safe GitHub App
But yeah, sure, you're free to tell yourself whatever you want.
And no, it's not only for insiders - thus the message. Outside votes get whitelisted when they meet the compos fairness criteria. It's not a popularity contest. Your vote would not count on this basis (amongst others).
Two things, one on-topic and the other off-topic:
The thing which makes 2048 moderately easy to reason about is that incoming pieces are always "1". However, this game appears to spawn in random pieces, with random point values. I tried to follow the to-and-fro of the design blog in order to find out why this is, and I get the impression it's for avoiding getting the player stuck, but it does have the disadvantage of making planning incredibly hard. The good news is that by reading the blog I finally understood what was going on with the screen shake
off-topic: that "Subscribe to me blog" modal is not only bad UX (imho, of course), but also doubles down on the UX tire-fire by resetting my reading position to the top of the page. It's almost enough to warrant a command-w right there. Just one datum, but it for sure made me sad