[Bug] Simulating events triggers spam-prevention #2672
Assignees
Labels
Bug
A defect in the app
Dev Approved
The issue has been approved by a team member and can be worked on.
Dev Complete
Ready For Review
Issue has a PR opened and is undergoing dev review.
Comments
CaveMobster
added
the
Dev Approved
phroggster
added a commit
to phroggster/Firebot
that referenced
this issue
Feb 22, 2025
- 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
- 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
added
Dev Complete
Ready For Review
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
When you Simulate Events with a user account that have a spam-prevention measure like Follow and Raid, those measures are triggered despite it being a test run
Expected Behavior
Simulate Event specifically says it's for testing, and tests should not have lasting changes in the environment they are run in. I had a friend who thought Firebot broke because subsequent tests after the first were silently failing, and I do not believe a user Simulating an Event with a specific username prior to a stream, only to have that same user actually trigger the event and have it fail on them live is expected behavior.
I am aware that Force Event to Run works, but, this does not address the case where an actual Event may silently fail if the user happened to test that Event beforehand with the same username
Steps To Reproduce
Version
Firebot: 5.63.0-beta2
What operating system are you using Firebot on?
Windows 10
Relevant log output
No response
Contact Details (Optional)
No response
The text was updated successfully, but these errors were encountered: