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

raidboss: convert NetRegexes.echo/message/dialog to params #5451

Merged
merged 2 commits into from
Jun 25, 2023

Conversation

quisquous
Copy link
Owner

@quisquous quisquous commented May 30, 2023

Part of #4986.

Closes #5452.

@quisquous
Copy link
Owner Author

I'm not sure about exposing even more variables into the global namespace for user triggers. Maybe this should be under Util?

Also it sure feels like gameLogCodes is a variable vs NetRegexes which is more of a static class (and thus capitalized, theoretically), but it sure looks funny next to the rest of the exposed variables too.

quisquous added a commit that referenced this pull request May 30, 2023
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
quisquous added a commit that referenced this pull request May 30, 2023
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
@quisquous quisquous marked this pull request as ready for review June 9, 2023 19:28
@quisquous quisquous marked this pull request as draft June 9, 2023 19:29
@quisquous quisquous marked this pull request as ready for review June 25, 2023 21:16
@quisquous
Copy link
Owner Author

Given the lack of response from anybody else here, I'm just going to make a decision.

I'm not sure about exposing even more variables into the global namespace for user triggers. Maybe this should be under Util?

Moved to Util after some thought, and I'm going to go with this approach over #5452.

@quisquous quisquous merged commit 5f38b03 into main Jun 25, 2023
@quisquous quisquous deleted the convert_gamelog_triggers branch June 25, 2023 21:18
github-actions bot pushed a commit that referenced this pull request Jun 25, 2023
github-actions bot pushed a commit that referenced this pull request Jun 25, 2023
quisquous added a commit that referenced this pull request Jun 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant