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.

Sign up for GitHub

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

Jump to bottom

[Feature Request] simulate events to bypass the one time per x requirement #1782

Closed
CKY- opened this issue May 29, 2022 · 1 comment
Closed

[Feature Request] simulate events to bypass the one time per x requirement #1782

CKY- opened this issue May 29, 2022 · 1 comment
Assignees
@zunderscore
Labels
Enhancement A feature request or improvement

Comments

@CKY-
Copy link
Collaborator

CKY- commented May 29, 2022

Describe the solution you'd like
While simulating any and all events reusing the username requires a restart of firebot, If you have a user only event and you simulate it you must restart firebot to test it again. the reason for this is its respecting the event cooldown

This should use the same logic as the activity feed where you can spam the event if needed.

so it would be an amazing feature to add an option to override/bypass cooldowns in event simulators.
@CKY- CKY- added the Enhancement A feature request or improvement label May 29, 2022
@CKY- CKY- mentioned this issue Jul 14, 2022
Closed
1 task
@V1perN3st
Copy link

I would like to see this as well. We should be able to simulate multiple raids (because it came happen) to not only make sure the Effects trigger (which can include conditions and have different effect for different raids) are working, but that everything is working as expected. Yes, the play button allows it to quick similar the effects, but it always uses Firebot Twitch Account and 5 people. If I use conditions for specific streamers and/or raid amounts, than it is harder to test as I have to test it once, restart the program (which wipes my chat history on the program), test the next one, restart the program, etc.... This also makes it hard for testing the queue with multiple raid messages.

@zunderscore zunderscore mentioned this issue Sep 3, 2022
Merged
@github-actions github-actions bot added Dev Complete Release Pending Issue has been resolved and is waiting to be packaged as part of a release labels Sep 3, 2022
@zunderscore zunderscore self-assigned this Sep 8, 2022
@ebiggz ebiggz closed this as completed Sep 9, 2022
@github-actions github-actions bot removed Release Pending Issue has been resolved and is waiting to be packaged as part of a release Dev Complete labels Sep 9, 2022
phroggster added a commit to phroggster/Firebot that referenced this issue Feb 22, 2025
@phroggster
fix(events): Don't Cache Simulated Events (crowbartools#2672)
fa4d9e0 
- Simulating an event trigger which had caching enabled would inhibit
  later de-factor triggerings of that event, at least until the event
  expired from the cache (12 hrs +/- 10 min).
- Raid, follow, reward redemptions, and viewer arrived events for a
  particular user name would therefore be unusable for 12 hrs.
- Yes, you could force simulate them, but not actually receive them.
- Adjust to having event simulations ignore the cache.
- ref crowbartools#2672, crowbartools#1782
phroggster added a commit to phroggster/Firebot that referenced this issue Feb 22, 2025
@phroggster
fix(events): Don't Cache Simulated Events (crowbartools#2672)
b11afd3 
- Simulating an event trigger which had caching enabled would inhibit
  later de-facto triggerings of that event, at least until the event
  expired from the cache (12 hrs +/- 10 min).
- Raid, follow, reward redemptions, and viewer arrived events for a
  particular user name would therefore be unusable for 12 hrs.
- Yes, you could force simulate them, but not actually receive them.
- Adjust to having event simulations ignore the cache.
- ref crowbartools#2672, crowbartools#1782
@phroggster phroggster mentioned this issue Feb 22, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zunderscore zunderscore

Labels
Enhancement A feature request or improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@zunderscore @ebiggz @CKY- @V1perN3st