I have released an update for this program. Pease see the change logs in the first post.
Beastly, on 19 June 2013 - 06:38 PM, said:
Instead of removing the 0 bug, why not add a "0" button?
Added to upcoming features list
logwet, on 13 July 2013 - 02:00 AM, said:
what does the "COR" button on the monitor do?
It stands for "correction" and its basically a backspace.
Herophantom, on 21 August 2013 - 08:33 PM, said:
Here is my verison of the same thing...
Let me know what you think.
I think your layout looks really nice. One issue that I'm having with my program is that in order to use it at optimal size (scale 0.5) you need to stack two monitors or you lose the frame.
Dreossk, on 24 December 2013 - 12:05 AM, said:
Hello,
This program is great. the problem is that the hitbox of the buttons is pretty messed up, especially for the first row (1,2,3). Pressing a number sometimes even gives the wrong number. Maybe it's a scale issue? It's not usable in the current state.
Also, putting censor to false doesn't work.
Edit: In fact, none of the changeable options I tried at the beginning work.
Not sure what was going on with the hitboxes. Should only accept hits on the number itself or either of the blank spaces beside the number. Haven't had a chance to test this yet. almost all of the options were broken with the last update. I have fixed it somewhat. anything that isn't in the main config should update with 'edit pin/data'
Anavrins, on 26 January 2014 - 01:10 PM, said:
Unfortunately, SHA-256 is not suitable for 1-5 digits pins, and a simple lookup of the hash on Google
will yield the pin,
since there are rainbow tables of 00000 through 99999 on the net.
A way to mitigate this would be to implement a salt, if you need help with that, I can give you a hand, just PM me
Edit: Sorry for the bump, but I felt that it was necessary to bring this up.
ah yeah that makes sense. But to be fair this is more for show, even with protected blocks and anything else you can think of short of Adventure Mode, I am sure there are 1000 ways to break into this. if you can access the computer you could just Ctrl+T and open the lua console and write 'for _,v in pairs( rs.getSides() ) do rs.setOutput( v , true )'