No, I was suggesting you use cron(8) and lynx(1) to assist you with your problem, unless you are using Windows, in which case you'd need a batch script and "Task Scheduler".
As for the other option, the old saying is "there's more than one way to skin a cat." Use whatever is best for you and your situation. If you want me to do a feasability study, it's $nnnn.nn and 3 months waiting.... 😉
If you use the DB/timestamp idea, you'd have to also account for the possibility that there might be several consecutive hours during which no one would log in. It might be preferable to use this method, though; if it's a gaming site (and it sounds like it is), and someone finds your "secret.php" and bumps it more than once an hour, they might win, eh?
Of course, you could get round that with a secret "key" that would have to be in the URI, or whatnot.
As for timestamps, there are UNIX timestamps available from PHP (see [man]time/man, for example), or native SQL timestamps (see the docs for your particular breed of SQL server....)