Linked text and voice channels #210

New issue

Closed

opened 2026-01-07 12:25:59 -05:00 by MrFleff · 4 comments

MrFleff commented

2026-01-07 12:25:59 -05:00

(Migrated from github.com)

Problem

Our stupid free chat bot we use for linking a history erasing text chat to a voice channel dies sometimes.
Almost more annoyingly is when the bot comes back to life users are still not properly removed from channels until they Re-enter the linked voice chat and leave.

Solution

We do it in house.
It should function somewhat like the following.

A new command needs made for linking a voice and text chat.
When a user joins a voice chat they are automatically added to the private text chat.
When a user leaves a voice chat they are automatically removed from the private text chat.

Notes 1

It should be tested to ensure the following alternate methods for leaving and entering channels also work

Admins/mods moving people
Joining an event auto puts you into its channel
Users being disconnected
Users being timed out

Notes 2

Whenever the bot starts up it'd be a neat feature to have it quick check who's in one channel and who has access to the private channels.
Basically a safety check for if enduragrok was ever down that it'll fix the text channel permissions for people when it returns.
Not required, especially cause we have few outages afaik.

Brought to you from my phone and hopefully formatted somewhat tastefully.

# Problem Our stupid free chat bot we use for linking a history erasing text chat to a voice channel dies sometimes. Almost more annoyingly is when the bot comes back to life users are still not properly removed from channels until they Re-enter the linked voice chat and leave. # Solution We do it in house. It should function somewhat like the following. 1. A new command needs made for linking a voice and text chat. 2. When a user joins a voice chat they are automatically added to the private text chat. 3. When a user leaves a voice chat they are automatically removed from the private text chat. ## Notes 1 It should be tested to ensure the following alternate methods for leaving and entering channels also work 1. Admins/mods moving people 2. Joining an event auto puts you into its channel 3. Users being disconnected 4. Users being timed out ## Notes 2 Whenever the bot starts up it'd be a neat feature to have it quick check who's in one channel and who has access to the private channels. Basically a safety check for if enduragrok was ever down that it'll fix the text channel permissions for people when it returns. Not required, especially cause we have few outages afaik. *Brought to you from my phone and hopefully formatted somewhat tastefully.*

sirdog3355 commented

2026-01-12 04:39:28 -05:00

(Migrated from github.com)

@MrFleff, I know you aren't expecting updates but... why not:

My progress so far is that:

Commands to list, add, and remove links between channels are done
Logic to give user permission to text channel based on VC joined is done
I've confirmed current logic will account for staff moving members between channels

Still gotta finish out the listener to detect when users leave, ensure there is proper cleanup when users move channels, and test the other edge cases you mentioned in Notes 1.

This feature may still take awhile to be released to production as I am undecided if I want to push it as it's own thing or bundle it with other things, such as #212 and #209. I am indecisive. Not to mention that I'll need to update the documentation.

As you may or may not have noticed I separated out Notes 2 into #211; the complexity of that is a tad higher and so that'll come after whatever the next release is for the bot.

@MrFleff, I know you aren't expecting updates but... why not: My progress so far is that: - Commands to list, add, and remove links between channels are done - Logic to give user permission to text channel based on VC joined is done - I've confirmed current logic will account for staff moving members between channels Still gotta finish out the listener to detect when users leave, ensure there is proper cleanup when users move channels, and test the other edge cases you mentioned in `Notes 1`. This feature _may_ still take awhile to be released to production as I am undecided if I want to push it as it's own thing or bundle it with other things, such as #212 and #209. I am indecisive. Not to mention that I'll need to update the documentation. As you may or may not have noticed I separated out `Notes 2` into #211; the complexity of that is a tad higher and so that'll come _after_ whatever the next release is for the bot.

sirdog3355 commented

2026-01-15 20:46:28 -05:00

(Migrated from github.com)

Logic is completed. I've confirmed that the logic applies for all items mentioned in Notes 1. Just a matter of cleaning up the branch and pushing to dev.

Logic is completed. I've confirmed that the logic applies for all items mentioned in `Notes 1`. Just a matter of cleaning up the branch and pushing to `dev`.

sirdog3355 commented

2026-01-15 22:52:09 -05:00

(Migrated from github.com)

@MrFleff

Feature completed and is in dev awaiting push to production. See: #214. Need to update documentation prior to closing this issue.

@MrFleff Feature completed and is in `dev` awaiting push to production. See: #214. Need to update documentation prior to closing this issue.

sirdog3355 commented

2026-01-28 03:36:35 -05:00

(Migrated from github.com)

Documentation updated. Closing.