Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Temp Voice Channel Category Location / Placement #67

Open
Vexbane opened this issue Jun 18, 2019 · 0 comments
Open

Temp Voice Channel Category Location / Placement #67

Vexbane opened this issue Jun 18, 2019 · 0 comments

Comments

@Vexbane
Copy link

Vexbane commented Jun 18, 2019

Great Option for having the Temp Voice Channel!

When temp voice channel is created = options to have it go under a specific category

  1. Option 1 - pre selected by server owner he chooses for default
  2. Option 2 - chosen during !tmp < name > < category name >
  3. Option 3 - auto created under the category the !tmp cmd was typed in
  4. Option 4 - make sure this cmd to create temp channel (permissions) is available for @everyone to use by default or cmd @ < specific roles >

Issues presented in Valkyrja discord server by Rhea, why this can't be implemented "API does not support Categories"

Possible Solution:

  1. Remove temp channel features from Valkyrja, Create a new bot that revolves solely around temp voice and text channels that can have a different API that allows for use of Categories (and possibly other features can't in current API)
  2. In creation of this 2nd bot, have 1st bot (Valkyrja) be able to communicate with 2nd bot. So if there are commands in Valkyrja to create those temp channels, they are only cmds to talk to 2nd bot in order to create these channels
  3. The 2nd bot could (perhaps should) be also allowed to work as a stand a lone bot with these features

~~ other side requests ~~

  1. Need temp #text-channels too!

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant