LeXdPyK Debug Commands

The LeXdPyK kernel comes with hidden debug commands for bot owners to update and manage their bots uptime, along with blacklist users and guilds.
All commands are invoked as <command> <botid> [args]
This is because the kernel commands have no prefix and are instead tied to the specific bot, allowing cross guild bots with the same ui and same guild lexdpyk bots that dont collide

Command	Description	Args
debug-add-guild-blacklist	Adds a guild to the LeXdPyK system level blacklist	bot_id guild_id
debug-add-user-blacklist	Adds a user to the LeXdPyK system level blacklist	bot_id user_id
debug-remove-guild-blacklist	Removes a guild from the LeXdPyK system level blacklist	bot_id guild_id
debug-remove-user-blacklist	Removes a user from the LeXdPyK system level blacklist	bot_id user_id
debug-modules-load	Loads new command/dlib files and unloads ones not present, does not reload prexisting files	bot_id
debug-modules-reload	Reloads all current command/dlib files, but does not load new ones, will fallback to previous import if reimport fails, ensuring uptime of as much as possible. Also calls drop-ramfs	bot_id
debug-logout-system	Exits the bot, used for remote shutdown (and dramatic effect)	bot_id
debug-drop-ramfs	Deletes the ramfs and resets it to a new one, used for debugging and module reloads	bot_id
debug-drop-kramfs	Deletes the kernel_ramfs and resets it to a new one, NOTE the bot is designed that the kernel_ramfs does not get reset until reboot, this may cause odd behavior, notably uptime statistics being reset	bot_id
debug-drop-modules	Drops dlib modules entirely, used for extreme edge cases where a dlib is causing problems but cant be reset, and rebooting is not an option	bot_id
debug-drop-commands	Drops command modules entirely, used for extreme edge cases where command is causing problems but cant be reset locally	bot_id
debug-toggle-logging	Toggles the log level between INFO and DEBUG	bot_id