The bot should check for operator status and re-op itself.
pvince opened this issue · comments
Paul Vincent commented
After net-splits the bot can end up losing its operator status.
Caveats:
- Some channels the bot is NOT operator (ex. LVL1, so it should recognize this and not constantly try to op itself)
- After the bot re-ops itself it should re-initiate an operator check for other users in the channel.
Possibly could be triggered by one (or more) of the following methods:
- Attempt to perform an operator only task, and get denied. Ex. try to op another user, and get rejected.
-- Issues: Could have multiple false flags in channels where the bot is not supposed to be operator. - Have a background process check the bot's status every X minutes.
-- Issues: Constantly checking
-- Benefits: Could also perform other "status" checks, for instance make sure the bot is connected to the server, make sure the bot is operator, maybe every X hours check the operator status of other users and adjust as necessary.