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

[Feature] Allow using "{current}" variable in other contexts #2

Closed
unilock opened this issue Jul 7, 2022 · 0 comments · Fixed by #3
Closed

[Feature] Allow using "{current}" variable in other contexts #2

unilock opened this issue Jul 7, 2022 · 0 comments · Fixed by #3

Comments

@unilock
Copy link
Contributor

unilock commented Jul 7, 2022

Currently you can only use the {previous} and {current} variables in the server_switch_message. However, it would be useful to be able to use these variables in other messages, especially the latter.

Some examples:
({username} = "player", {current} = "vanilla", {previous} = "modded")

~

This works fine:

server_switch_message="**{username} moved from {previous} to {current}**"

Result:

player moved from modded to vanilla

~

This does not work:

join_message="**{username} joined {current}**"

Result:

player joined {current}

Desired result:

player joined vanilla

~

Another case where this would be useful:

message="[{username}@{current}] {message}"

Desired result:

[player@vanilla] hello, world

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant