Hacked 2.5

Reviews

1 ★, on 2020-06-30
I believe it's a very useful game and platform! I once played too. But now I'm not able to link my twitter. Kindly check and resolve it soon team.

2 ★, on 2020-08-10
Ok, but really do not like the fact that it requires access to your Twitter account to reveal hidden failed test cases. Seems rather shady... Edit: one star less than before because no documentation for weird syntax (documentation link yields 404 error with no functional redirects)

2 ★, on 2019-01-28
Great idea, but badly implemented I liked the problems and the way to insert code a lot, but there were some serious issues: you can't access how to use the functions you unlocked; there is no way to do some kind of debugging, to see if a line of code is doing exactly what you expect it to; the documentation doesn't open; I couldn't log in with my Twitter account (why Twitter?) to see the hidden cases; it is hard to position the cursor where you want. But it seems the developer doesn't care.

5 ★, on 2019-08-09
High Difficulty! This game requires the ability to recognize patterns, in seemingly random configurations. You don't need a high IQ to play, but it is recommended to be at least above average, so it is more enjoyable. I found the Logic Bomb tests interesting, and rather challenging. Have fun! P.S. - Did the maker of Polybius design this? It seems like it may have been.

3 ★, on 2019-03-09
i like the app, its fun, but it seems to be unsupported, the twitter sign in doesnt work, the guide and official website dont exist anymore and the link(on twitter) that once lead to a complete guide now leads to a scam website. all in all, if you want to try your skill at coding its nice, but dont expect to find any help if you get stuck (there is an ingame tutorial for the most used bits of code but its not enough to help you out in case you are stuck)

1 ★, on 2019-06-15
The game is currently broken. Any time you alter the input of any variables that were assigned to be equal to the input, every variable including the input, change. it's as if when you make var_a = input it makes var_a just act as a pointer to the memory location of the input rather than be a copy of input in its own memory space. This bug is game breaking once you get to the palindrome puzzle.