-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
[Bug] System Commands Forwarded from Run Command Ignore Restrictions #2999
Comments
this is not a bug that is working as intended the issue is the restrictions are in the handel chat message and would need to be moved to firecommand handel chat message checks the restrictions and then runs fireCommand fireCommnad is used in 3 places so then the question is should the restriction check be in the fireCommand and be bypassed by isManual and then isManual exposed in the runCommandEffect as a Enforce Permission Rules and Cool Downs the other option is we add a checkbox and switch from runCommandFromEffectt to handelChatMessage striping the original trigger and replacing it with the trigger from the ID supplied and this will allow the usage of the command to be tracked as well Firebot/src/backend/chat/commands/command-runner.ts Lines 194 to 213 in aca4608
Firebot/src/backend/chat/commands/chat-command-handler.ts Lines 93 to 265 in aca4608
i personally think reusing the handelChatMessage with option to enforce cooldowns and restrictions is the better way to go here. |
Description
With a currency literally named
totally-fake-internet-points™
, we attempted to add a custom command!currency
that used a Run Command effect to trigger the!totally-fake-internet-points™
command with$arg[all]
as the argument, and$user
as the triggerer.!currency set @username [amount]
then bypasses the streamer/moderator restrictions of thetotally-fake-internet-points™ set
subcommand.Steps to Reproduce
Expected Behavior
Warn that the restrictions weren't met.
Firebot Version
v5.63.2
Submitted By
phroggie
The text was updated successfully, but these errors were encountered: