I !HOPE that your HBIT bot catches up with missed (valid) HBIT token mining commands, taking into account the different days (UTC) such commands were made. 🤗 !LOLZ
Prolonged downtime is exactly what is required. Either that or I can shut it off for a day and test it that way. A test bot? That would be way overkill for something like this. We'll just see how it goes.
If you have time, you can have a test token (basically any cheap token you like on #HiveEngine) and a test bot, then test your new codes there alongside your HBIT bot. 🤓 You can keep both bots running for some time where the test bot also tips a token (only for Hive users who want them), then turn off temporarily the test bot for at least 2 days (UTC) to see if it will catch up to missed commands while respecting the time zone !INDEED. 😎 !WEIRD !HOPE !ALIVE
I like your thinking, but don't think that would work. Running an a test bot would be possible, but tying to another h-e token would not. The bot needs permission to send tokens. I wouldn't have permission to have the bot send h-e token XYZ. I can only give it permission for HBIT and the BLAQ tokens. However doing that would negate the purpose of preventing 1/day. I think we're OK just letting it test out in real life. When the occasion comes up (and it will!) We'll find out if it works.
I meant using your owntest bot using a test token that you would buy (at very cheap prices) on #HiveEngine, so no permissions needed !INDEED from anyone else for such testing. 🤯🤓 !WEIRD !HOPE !PIZZA
I still don't think that would work. The bot requires both posting and active keys to post and send the tokens. The purpose of testing the bot would be to see if it can do both of these things. I would not have those credentials for another token. I suppose I could do it for HBIT, but I don't want to double-send the tokens (from the regular bot and a test bot, as well as more than once per day).
You could also create a test Hive account (or use an existing extra account) too for that though. 🤯 You don't need to be the issuer of a #HiveEngine token that you will use for testing !INDEED. 😅 !WEIRD !HOPE !PIZZA
I !HOPE that your HBIT bot catches up with missed (valid) HBIT token mining commands, taking into account the different days (UTC) such commands were made. 🤗 !LOLZ
Trying to implement this. Will have to see if it works next time things go down and then the bot tries to catch up.
I !HOPE that it does not require another (prolonged) downtime of your HBIT bot to see if your implementation works as intended !INDEED! 🤗
I would have suggested a test bot for trying out that implementation, though I know that it would require more time from you. 🧘♂️😅 !WEIRD !ALIVE
Prolonged downtime is exactly what is required. Either that or I can shut it off for a day and test it that way. A test bot? That would be way overkill for something like this. We'll just see how it goes.
If you have time, you can have a test token (basically any cheap token you like on #HiveEngine) and a test bot, then test your new codes there alongside your HBIT bot. 🤓 You can keep both bots running for some time where the test bot also tips a token (only for Hive users who want them), then turn off temporarily the test bot for at least 2 days (UTC) to see if it will catch up to missed commands while respecting the time zone !INDEED. 😎 !WEIRD !HOPE !ALIVE
I like your thinking, but don't think that would work. Running an a test bot would be possible, but tying to another h-e token would not. The bot needs permission to send tokens. I wouldn't have permission to have the bot send h-e token XYZ. I can only give it permission for HBIT and the BLAQ tokens. However doing that would negate the purpose of preventing 1/day. I think we're OK just letting it test out in real life. When the occasion comes up (and it will!) We'll find out if it works.
I meant using your own test bot using a test token that you would buy (at very cheap prices) on #HiveEngine, so no permissions needed !INDEED from anyone else for such testing. 🤯🤓 !WEIRD !HOPE !PIZZA
I still don't think that would work. The bot requires both posting and active keys to post and send the tokens. The purpose of testing the bot would be to see if it can do both of these things. I would not have those credentials for another token. I suppose I could do it for HBIT, but I don't want to double-send the tokens (from the regular bot and a test bot, as well as more than once per day).
You could also create a test Hive account (or use an existing extra account) too for that though. 🤯 You don't need to be the issuer of a #HiveEngine token that you will use for testing !INDEED. 😅 !WEIRD !HOPE !PIZZA