I think this game is a bit different than http://gabrielecirulli.github.io/2048/ Take a look at this situation: ___________________ |___2|____|____|____| |___2|____|____|____| |___2|____|____|____| |____|____|____|____| in the original the result of going up would be ___________________ |___4|____|____|____| |___2|____|____|____| |____|____|____|____| |____|____|____|____| but in this game it's ___________________ |_…
no score too! :( how am i suppose to know when i break my own record [i.e. 3012 - never got passed 512 on the tiles]
2048 in sed
31–39 of 39 posts
Re: 2048 in sed
#32We just need now the 2048 in assembler, and we'll be done! Just joking, I love these and I'm unemployed. Keep'em coming!
Re: 2048 in sed
#33Re: 2048 in sed
#34Sed awesome. Also, disappointed no one has blatantly embedded https://github.com/progranism/Bitcoin-JavaScript-Miner to put all this time wasting to good u$e.
Sadly that javascript miner is stupidly slow. You could have a top Hacker News post and still only make pennies.
Re: 2048 in sed
#35Earlier quoted context omitted.
Score is now implemented -enjoy!
thanks! edit: you broke it :(
As a bonus, the score calculation is now done in pure sed.
If you notice any other issues, please let me know!
Re: 2048 in sed
#36Hey Matt... I mean "Sed and Awk the great" :)
Re: 2048 in sed
#37Earlier quoted context omitted.
thanks! edit: you broke it :(
Fixed! The score is now calculated as the sum of all merge results (like the original game), instead of the sum of all cells (like I was doing). As a bonus, the score calculation is now done in pure sed. If you notice any other issues, please let me know!
Re: 2048 in sed
#38Earlier quoted context omitted.
Fixed! The score is now calculated as the sum of all merge results (like the original game), instead of the sum of all cells (like I was doing). As a bonus, the score calculation is now done in pure sed. If you notice any other issues, please let me know!
thanks
The gameplay should now be identical to the original 2048.
Re: 2048 in sed
#39Earlier quoted context omitted.
If your well-beloved GNU coreutils did not breach every POSIX standard and add new flags to every program, no such problem would exist. Seriously, I do not know whether Mac OS is using a custom implementation of UNIX utilities, or distributin BSD coreutils, but I know that it is a licensed, certified UNIX.
UNIX certification means nothing if the utils are intentionally outdated and incompatible with the de facto UNIX-like implementation due to petty licensing concerns. At the end of the day, whether some script works is the issue, not a UNIX branding.