Sigh.
Alright, I was trying to avoid further derailing this from the important parts of the topic, but if you really must goad me into this discussion to be satisfied then let’s have at it.
I don’t believe that the cooldown was 24 hours thru most of December and up until 211 went live, I know. The reason that I know is because I spent the entire time padding my footfall income daily by having my remaining alts, that had no permissions to my shop, walk into my shop, and every single night after doing that, server reset or otherwise, I would get the footfall from each of those characters. I would collect with the shop owner, walk all my alts thru, and collect again. There is absolutely no reasonable explanation involving a 24 day timer that would explain how I was able to do that.
Could it be a fluke that affected some beacons / planets and not others? I highly doubt it but it is not within my ability to disprove it, I can only attest to how my own beacons were behaving, and they were, very predictably, following a 24 hour reset.
So yes, it’s not a matter of believing. It’s not a matter of convincing you either, because I can’t control what you think or do, feel free to keep on clinging adamantly to your position, but I will certainly defend mine, and not presume to tell you how to behave or what to say or stop saying.
It is, however, a matter of the developers being made aware of how their game is behaving in actuality, regardless of what the patch notes say. That is how bugs, such as the 24 day cooldown, are found and fixed.
Here’s how this exact process went when the 24 day mistake was figured out, if you care to read it (tho I doubt that you will). I was directly involved, and just as steadfastly insistent on standing behind my test results as I am now:
In this particular instance, it is ironically enough the opposite, and some people such as yourself, now believe that it was still 24 days. Yet strangely enough a lot of people on the posts above commented on how much lower their daily or weekly footfall now is, how curious.
I can’t speak for the developers. They might be aware that it was corrected back to 24 hours, it might have been a happy accident, it might be a case of the left hand not knowing what the right was doing. I have no idea. But if they think that it was still 24 days, then they too are wrong. Once again, much in the same way as when everyone was swearing up and down that it was 24 hours, reality as backed by extensive testing begs to differ.
It is how the game actually behaves, and not the patch notes or developer announcements, that matter, that is how mistakes are found and fixed, and sometimes this requires having long, boring talks like this, with folks such as yourself, for the facts to come to light, but once again, it must always be backed by extensive testing until reproducible, predictive and consistent results are able to shed a light on the actual mechanics.
Edit: Minor nitpicky clarification, I can attest that it was a 24 hour timer between December 7 and the release of 211 with the exception of 23 to 26 of December since I was out of town with family and couldn’t play to do my daily padding of my shop footfall then. ![]()
Edit 2: Incidentally, Discord is the reason why I know exactly when I noticed it, but not when the change actually happened, that must (obviously) have happened earlier than my noticing it, at a minimum two days before I’d wager:

Does that in itself prove anything conclusively? No, of course not, go on and keep calling me a liar. Heck, I might be so committed to perpetuating this fraud that in no way benefits me that I could have just Photoshopped the thing. So keep on with the name calling if that makes you happy, but it marks the date when I started taking notice of it enough to start testing it again (and subsequently use it to make a little bit of extra footfall every day). It turned out to be 24 hours exactly rather than during daily reset, by the way, which was an earlier point of contention before the 24 day mistake was discovered, and my reason to start the extensive testing back then. ![]()