temp_vc ¶
Temporary voice channel management service.
This module provides automatic creation and management of temporary voice channels for Discord servers, allowing users to have their own private voice channels that are automatically created when joining a designated channel and deleted when empty.
Classes:
-
TempVc–Discord cog for managing temporary voice channels.
Functions:
-
setup–Set up the TempVc cog.
Classes¶
TempVc ¶
TempVc(bot: Tux)
Bases: BaseCog
Discord cog for managing temporary voice channels.
Initialize the temporary voice channel service.
Parameters:
-
bot(Tux) –The bot instance to attach this service to.
Methods:
-
on_voice_state_update–Handle voice state updates for temporary voice channels.
-
get_config–Get a configuration value from CONFIG with support for nested keys.
-
__repr__–Return a string representation of the cog instance.
-
unload_if_missing_config–Check if required configuration is missing and log warning.
Attributes:
-
db(DatabaseCoordinator) –Get the database coordinator for accessing database controllers.
Attributes¶
db property ¶
db: DatabaseCoordinator
Get the database coordinator for accessing database controllers.
Returns:
-
DatabaseCoordinator–Coordinator providing access to all database controllers.
Examples:
>>> await self.db.guild_config.get_guild_config(guild_id)
>>> await self.db.cases.create_case(...)
Notes
This property provides convenient access to database operations without needing to access self.bot.db directly.
Functions¶
on_voice_state_update async ¶
on_voice_state_update(member: Member, before: VoiceState, after: VoiceState) -> None
Handle voice state updates for temporary voice channels.
If the user joins the temporary voice channel, a new channel will be created for them. If the user leaves the temporary voice channel and the channel is empty, it will be deleted.
Parameters:
-
member(Member) –The member that triggered the event.
-
before(VoiceState) –The voice state before the event.
-
after(VoiceState) –The voice state after the event.
_handle_user_join async ¶
_handle_user_join(member: Member, channel: VoiceChannel | StageChannel) -> None
Handle the case when a user joins the temporary voice channel.
Parameters:
-
member(Member) –The member that joined the channel.
-
channel(VoiceChannel) –The channel that the member joined.
_setup_command_usage ¶
_setup_command_usage() -> None
Generate usage strings for all commands in this cog that lack explicit usage.
The generated usage follows the pattern: <qualified_name> <param tokens>
Where: - Required parameters are denoted as <name: Type> - Optional parameters are denoted as [name: Type] - The prefix is intentionally omitted (provided by ctx.prefix)
Examples:
ban <member: Member> [reason: str] config set <key: str> <value: str>
Notes
Respects explicit usage strings if already set on a command. Errors during generation are logged but don't prevent cog loading.
_handle_user_leave async ¶
_handle_user_leave(
before_channel: VoiceChannel | StageChannel,
after_channel: VoiceChannel | StageChannel | None,
temp_channel_id: int,
temp_category_id: int,
) -> None
Handle the case when a user leaves a voice channel. Deletes empty temporary channels.
Parameters:
-
before_channel(VoiceChannel) –The channel the user was in before.
-
after_channel(VoiceChannel) –The channel the user moved to. Could be None if the user disconnected.
-
temp_channel_id(int) –The ID of the temporary voice channel the bot manages.
-
temp_category_id(int) –The ID of the category holding temporary voice channels.
_generate_usage ¶
Generate a usage string with support for flags and positional parameters.
This method inspects the command's callback signature to detect: - FlagConverter parameters (e.g., --flag value) - Positional parameters (e.g., <required> or [optional])
Parameters:
-
command(Command) –The command to generate usage for.
Returns:
-
str–Generated usage string, or qualified command name as fallback.
Notes
Delegates to shared usage generator for consistency across all cogs. Falls back gracefully to command name if generation fails.
get_config ¶
Get a configuration value from CONFIG with support for nested keys.
Parameters:
-
key(str) –The configuration key to retrieve. Supports dot notation for nested values (e.g.,
"BOT_INFO.BOT_NAME"). -
default(Any, default:None) –Default value to return if key is not found, by default None.
Returns:
-
Any–The configuration value or default if not found.
Examples:
>>> self.get_config("BOT_INFO.BOT_NAME")
'Tux'
>>> self.get_config("MISSING_KEY", "fallback")
'fallback'
Notes
Errors during retrieval are logged but don't raise exceptions. Returns the default value on any error.
__repr__ ¶
__repr__() -> str
Return a string representation of the cog instance.
Returns:
-
str–String representation in format
<CogName bot=BotUser>.
unload_if_missing_config ¶
Check if required configuration is missing and log warning.
This allows cogs to detect missing configuration at load time and return early from init to prevent partial initialization.
Parameters:
-
condition(bool) –True if config is missing (should unload), False otherwise.
-
config_name(str) –Name of the missing configuration for logging purposes.
Returns:
-
bool–True if config is missing (caller should return early), False if config is present.
Examples:
>>> def __init__(self, bot: Tux):
... super().__init__(bot)
... if self.unload_if_missing_config(not CONFIG.GITHUB_TOKEN, "GITHUB_TOKEN"):
... return # Exit early, cog will be partially loaded but won't register commands
... self.github_client = GitHubClient()
Notes
When this returns True, the cog's init should return early to avoid initializing services that depend on the missing config. The cog will be loaded but commands won't be registered properly, preventing runtime errors.
For complete cog unloading, the bot owner should remove the cog from the modules directory or use the reload system to unload it programmatically.
_unload_self async ¶
_unload_self(extension_name: str) -> None
Perform the actual cog unload operation.
Parameters:
-
extension_name(str) –Full extension name to unload.
Notes
This is called as a background task by unload_if_missing_config(). Errors during unload are logged but don't raise exceptions.