This site requires JavaScript, please enable it in your browser!
Greenfoot back

SPower's Comments

Back to SPower's profile

It must be possible in another way. So please don't upload 20 scenarios in 2 hours :)
STOP SPAMMING THE GREENFOOT WEBSITE!!!!!
I used mjrb's scenario: http://www.greenfoot.org/scenarios/261
SPowerSPower

2013/11/23

It's about 30 fps average; sometimes it goes up to 40 and sometimes down to 20. When I download it it's faster, of course. And great job btw!
Thanks a lot man!
SPowerSPower

2013/11/15

Ok. But why leave this comment on MY scenario? I posted it at yours, so it's more obvious to continue there
Well, it's quite hard to optimize. Switching to deferred rendering was a big improvement, but now it looks like it will hit a ceiling of performance close in the future... I'll do my best!
SPowerSPower

2013/11/11

Well, hashing is essentially turning a lot of data into a small form, which is almost impossible to crack, because a small change results in a completely different hash (The code for to hash the passwords is in the Coder class). This means that you can only compare the hash of the entered password to the stored one, and check if they are the same: the same data always has the same hash. And I wasn't really offended :) And yes, of course you may use the classes! That's why I posted the source! And ScoreBoard is from the greenfoot team, not me. And if you want to know more about hashing, I saw a good video about it: https://www.youtube.com/watch?v=b4b8ktEV4Bg
SPowerSPower

2013/11/11

Really, I don't think that's bad. Your password is hashed, so I can't access it (you can't un-hash something). And also, banning a user only happens when you enter the wrong password too many times. Ok with all that? And if I wanted to use it to my own advantage, why would I post the source?