Post by iconPost by zezo | 2017-11-20 | 15:47:32

Found a new bug. Was thinking about keeping it for a while, but it may have serious consequences, so here it goes.

Problem - commands are submitted with user-side timestamp.

Good side - you can abuse it to cheat the system and program one turn in the future without wasting cards.

Bad side - if you turn to avoid a rock NOW and your PC clock is in the future you WILL hit the rock because the sever won't execute the turn before the time gets to point of your user-side clock.

commenticon 5 Comments
Post by iconPost by karriv | 2017-11-20 | 17:16:23
Why, oh why... What can you possibly achieve (from the perspective of the system) by that?

What will happen if your clock is in the past? Command executed immediately, never, some other time?
Post by iconPost by zezo | 2017-11-20 | 17:22:03
Past commands are executed immediately. At least they got this one right.

The possible reasoning beats me. Unless you use the same command to add programmings, but then it should also charge the card use, in which case you are in even bigger trouble if your clock is not in sync with UTC within few milliseconds.
Post by iconPost by zezo | 2017-11-20 | 17:26:22
This reminds me of the time when FarmVille was big thing on Facebook, more than 10 years ago.

It used client-side times for the actions, so I wrote a script to plant tomatoes 4 hours in the past, pick them one second later and level up above everybody else in the world ;-)
Post by iconPost by woffer | 2017-11-21 | 02:05:07
Literally laughed out loud. Good for you!
Post by iconPost by nsp | 2017-11-21 | 02:08:50
lol tomato cheater
border
Topics list
Posts
border
5
border
border
Copyright 2009 by ZEZO.ORG. All Rights Reserved.