Closed GoogleCodeExporter closed 5 years ago
The problem with this is that it's pretty much impossible to make a high score
system
that can't be hacked. That said, two things can be done:
1) Make a high-score system that's nontrivial to hack and hope that no-one
bothers to
try it (maybe add disincentives like have the scores fade away after a month or
so).
2) Put a personal best score in the cookie so people can track their own
progress.
1 involves more work but is likely more satisfying.
Thoughts?
Original comment by hjfreyer
on 22 Mar 2010 at 4:21
The word "impossible" should not be uttered here.
I like Idea 1. I think Idea 2 is a cop-out. And people like me clear cookies too
often for it to matter.
Frankly, I'm at a loss as to how I would begin to hack a high scores list
(probably
because I would never want to), so I'm not sure I can provide insight on how to
prevent it without hearing a few examples. If you're using a database to store
the
scores, there are a couple of things you could do to prevent people from
messing with
it, but I'd be fuzzier on the JS side of things.
Original comment by angelatr...@gmail.com
on 22 Mar 2010 at 4:39
Infeasible.
Original issue reported on code.google.com by
angelatr...@gmail.com
on 22 Mar 2010 at 3:15