-
Notifications
You must be signed in to change notification settings - Fork 383
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
raidboss: convert NetRegexes.echo/message/dialog to params #5451
Conversation
I'm not sure about exposing even more variables into the global namespace for user triggers. Maybe this should be under Also it sure feels like |
This is part of #4986. This is an alternative PR to #5451. In order to switch entirely over to `netRegex: { params }` style triggers, this PR adds a `gameLogType` field for `GameLog` triggers only. If specified, it will add the right `code`. Downsides: kind of awkward if `code` is already specified (and this will throw an error) Other options: * add a bunch more types so you could say `type: 'GameLogEcho'`, but this seemed much more hairy than was worth and the TriggerTypes type is already very very long * export the codes from some common location, import them everywhere, but this is even more nonsense to import so that user triggers can eval properly
This is part of #4986. This is an alternative PR to #5451. In order to switch entirely over to `netRegex: { params }` style triggers, this PR adds a `gameLogType` field for `GameLog` triggers only. If specified, it will add the right `code`. Downsides: kind of awkward if `code` is already specified (and this will throw an error) Other options: * add a bunch more types so you could say `type: 'GameLogEcho'`, but this seemed much more hairy than was worth and the TriggerTypes type is already very very long * export the codes from some common location, import them everywhere, but this is even more nonsense to import so that user triggers can eval properly
a952b1c
to
f5017c0
Compare
f5017c0
to
d9ea386
Compare
Given the lack of response from anybody else here, I'm just going to make a decision.
Moved to Util after some thought, and I'm going to go with this approach over #5452. |
Part of #4986.
Closes #5452.