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

Update dispatching system #458

Merged
merged 13 commits into from
Mar 14, 2024
Merged

Conversation

TrustyJAID
Copy link
Collaborator

@TrustyJAID TrustyJAID commented Mar 12, 2024

  • Bump to version 4.1.1
  • Now all dispatches happen after the session has started.
  • Dispatches provide the whole game session if more information is needed.
  • Provides some but not all backwards compatibility since it's a game session being sent now not a context object.
    • A send method was added to the session object so it can be used that way.
    • The session channel was added to the session object so it's closer to a context object.
    • If context specifics are required they're already on the session via session.ctx.
  • When a psychic reveals a special attribute about the monster it will now dispatch that event as if the adventure had started. No need to ping people when you find out it was transcended after, the bot will do it for you.
  • Attach the adventure cog to the dev environment for devs in the dev list.
  • Include the current server stats in [p]adventurestats.
    • These stats are used in filtering what monsters are available.
  • Fix an issue where monster dynamic stats were potentially affecting everyone instead of adjusting for the specific adventure session.
  • Add [p]adventureseed to investigate information about a given seed without starting an adventure.
  • Allow [p]adventurestats and [p]adventureseed to bypass lock requirements.

- Bump to version 4.1.1
- Now all dispatches happen after the session has started.
- Dispatches provide the whole game session if more information is needed.
- Provides some but not all backwards compatibility since it's a game session being sent now not a context object.
 - A send message was added to the session object so it can be used that way.
 - The session channel was added to the session object so it's closer to a context object.
 - If context specifics are required they're already on the session via `session.ctx`.
- When a psychic reveals a special attribute about the monster it will now dispatch that event as if the adventure had started. No need to ping people when you find out it was transcended after, the bot will do it for you.
- Attach the adventure cog to the dev environment for devs in the dev list.
- Include the current server stats in `[p]adventurestats`.
 - These stats are used in filtering what monsters are available.
Make stats display consistent for both places in adventurestats command.
Change adventureresults to accept the guild instead of a context object. We only ever used the guild ID anyway from it.
…specific guild stats we can run the command in the guild or provide the ID.
Add `[p]adventureseed` to see details about a given seed without starting an adventure. Owner only.
Include the seed in `[p]adventurestats`
Edit only buttons that change value when users interact with it.
…veryone instead of adjusting for the specific adventure.
@aikaterna aikaterna merged commit 8053ea4 into aikaterna:master Mar 14, 2024
2 checks passed
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

Successfully merging this pull request may close these issues.

2 participants