Hey @Jakealake!
Here’s another topic related to your situation:
As you will see, I came up with a solution, even for users to keep track with their own timers, as you can’t @them
once the timer is over, Nightbot doesn’t have the information on who was the user who triggered the command anymore at that point, but most importantly, you’ll see the issue we’ve encountered, which was that the URL headers the API uses to send more messages through Nightbot without authorization don’t last more than 5 minutes, so a timer that goes beyond the life expectancy of the URL isn’t possible.
Hopefully this answers all your questions, and I’m sorry there’s no better solution.