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

Color in eco messages #5734

Open
100petr opened this issue Mar 10, 2024 · 0 comments · May be fixed by #5738
Open

Color in eco messages #5734

100petr opened this issue Mar 10, 2024 · 0 comments · May be fixed by #5738
Labels
bug: confirmed Confirmed bugs in EssentialsX. misc: adventure Issues and PRs related to the Adventure refactor. Temporary label during 2.21.x cycle.

Comments

@100petr
Copy link

100petr commented Mar 10, 2024

Type of bug

Other unexpected behaviour

/ess dump all output

https://essentialsx.net/dump.html?id=84105a9e33454ca9a0ceb02ef086a77f

Error log (if applicable)

No response

Bug description

The eco take command has the amounts in yellow, the eco give has the entire message in green.
image
image
image

Steps to reproduce

Try /eco give nick amount
and also /eco take nick amount
Compare the color of the amount

Expected behaviour

The format will be unified

Actual behaviour

The format is not uniform

@100petr 100petr added the bug: unconfirmed Potential bugs that need replicating to verify. label Mar 10, 2024
@pop4959 pop4959 linked a pull request Mar 11, 2024 that will close this issue
@pop4959 pop4959 added bug: confirmed Confirmed bugs in EssentialsX. misc: adventure Issues and PRs related to the Adventure refactor. Temporary label during 2.21.x cycle. and removed bug: unconfirmed Potential bugs that need replicating to verify. labels Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug: confirmed Confirmed bugs in EssentialsX. misc: adventure Issues and PRs related to the Adventure refactor. Temporary label during 2.21.x cycle.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants