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

Discord integration #124

Open
yochaigal opened this issue Sep 20, 2024 · 1 comment
Open

Discord integration #124

yochaigal opened this issue Sep 20, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@yochaigal
Copy link
Owner

Is your feature request related to a problem? Please describe.
It might be fun to integrate Kettlewright characters/parties with discord. Even a simple call such as @username:char that pulled up a link to the character page, or pulled in data and printed it in discord. For instance, today I was playing in a PbP and I wanted to know the STR score of a PC. It was pretty easy to just look at the link (pinned in a channel) but it would be cool to do something like /kw [PC_name] and get output right there.

Just a thought.

@yochaigal yochaigal added the enhancement New feature or request label Sep 20, 2024
@oswida
Copy link
Collaborator

oswida commented Nov 5, 2024

Things we need to consider/discuss/define:

  • Security: bot can have an access to the whole system as a part of backend, but we still want to restrict data depending on the user. There is no direct relation between Discord and KW users, so we need some kind of login command or maybe user token generated in KW.
  • Command definitions: it would be good to have some list of available commands with functionality descriptions. Can be small for the beginning.
  • Deployment: I'm personally not familiar with unicorn, is it possible to run Discord bot as a concurrent task with Flask server?

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

No branches or pull requests

3 participants