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

Make timelord able to connect to multiple guilds from one deploy #22

Open
4 tasks
Errolyn opened this issue Aug 20, 2020 · 2 comments
Open
4 tasks

Make timelord able to connect to multiple guilds from one deploy #22

Errolyn opened this issue Aug 20, 2020 · 2 comments

Comments

@Errolyn
Copy link
Owner

Errolyn commented Aug 20, 2020

Timelord should be able to connect to multiple guilds and have individual configs to support this.

Things to consider:

  • Keeping input and output channels correct for each guild.
  • Adding a config set up page of some sort so the bot can be invited without needing access to the deploy server.
  • Configs should be updatable .
  • There should be some method blocking guilds in case of abuse.
@mythmon mythmon changed the title Make timelord able to run on multiple servers from one deploy Make timelord able to connect to multiple guilds from one deploy Nov 6, 2020
@mythmon
Copy link
Collaborator

mythmon commented Nov 6, 2020

Since "server" is ambiguous here between "a collection of channels and users on Discord" and "a place where code is running", I updated this issue to use "guild" to refer to the former. Guild is the term used in the Discord API to refer to server-the-collection-of-channels.

@Errolyn
Copy link
Owner Author

Errolyn commented Jun 19, 2021

work on this feature has been started here: Errolyn/tl_bot_site#1

the first step is to make a site that can allow an admin/owner to manage a the bot, then once we have that in place Then we will make the changes to consume those settings from timelord.

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

No branches or pull requests

2 participants