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/oopsy: support jobs instead of names in triggers #5916

Merged
merged 1 commit into from
Nov 10, 2023

Conversation

quisquous
Copy link
Owner

You can now also write ${player.job}, ${player.role}, ${player.nick}, or ${player.name} in triggers now as well if you want to override output strings individually.

If the property isn't there (somebody not in your party, bugs, typos), it will default to nickname.

Fixes #3000.

You can now also write `${player.job}`, `${player.role}`,
`${player.nick}`, or `${player.name}` in triggers now as well
if you want to override output strings individually.

If the property isn't there (somebody not in your party, bugs,
typos), it will default to nickname.
@quisquous quisquous merged commit 2d1f7d1 into main Nov 10, 2023
6 checks passed
@quisquous quisquous deleted the add_party_name_option branch November 10, 2023 22:52
github-actions bot pushed a commit that referenced this pull request Nov 10, 2023
…gers (#5916)

You can now also write `${player.job}`, `${player.role}`,
`${player.nick}`, or `${player.name}` in triggers now as well if you
want to override output strings individually.

If the property isn't there (somebody not in your party, bugs, typos),
it will default to nickname.

Fixes #3000. 2d1f7d1
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.

Option to use job name instead of player name
1 participant