Hacker News Reader

2 seems easy to defeat. If you know you're going to slow down 30 seconds to 5 minutes, you could just send the start packet 4 minutes and 30 seconds in, instead of at the beginning.

3 seems easy to defeat too. Just add a duplicate set of fields, which default to the same values as the original ones, and have the first set control the RNG and the second set control the display. Then you can change the second set all you want.

View on HN

For 2, the server can send back a random number (let's call it a nonce) for that attempt session. This nonce can be used to seed the prng such that you couldn't have started the attempt before telling the server that you're starting, only after.

3 is not fully solvable I think, it's the same class of hacks as x-raying. You can only make it really difficult. At the end of the day, you can't control what's being rendered client-side, short of cloud gaming. I have seen ML approaches to detecting behaviour server-side for things that shouldn't be humanly possible (like seeing through a wall) but it's an arms race.

The start packet should contain something from the server like the level seed, so you can't "start" without it.

Reply on news.ycombinator.com