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

Barbarian arena bucket lack unique id. #2618

Open
2 of 5 tasks
Isaakk opened this issue May 8, 2024 · 2 comments
Open
2 of 5 tasks

Barbarian arena bucket lack unique id. #2618

Isaakk opened this issue May 8, 2024 · 2 comments
Labels
Priority: Medium This issue may be impactful and needs some attention. Stale No activity Status: Pending Test This PR or Issue requires more testing Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@Isaakk
Copy link

Isaakk commented May 8, 2024

Priority

Medium

Area

  • Datapack
  • Source
  • Map
  • Other

What happened?

The Barbarian test bucket is lacking the unique id that the script requires in order to fill the horn with mead, I do not even know why unique id is used here when this bucket is already unique.
The enemy Spirit of Fire have incorrect damage values and some attack have it's minDamage is higher than the maxDamage.

What OS are you seeing the problem on?

Windows

Code of Conduct

  • I agree to follow this project's Code of Conduct
@Isaakk Isaakk added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label May 8, 2024
@github-actions github-actions bot added Priority: Medium This issue may be impactful and needs some attention. Status: Pending Test This PR or Issue requires more testing labels May 8, 2024
@majestyotbr
Copy link
Contributor

Update your issue with more infos about the problem.
There are people that doesn't play the game on the official server or don't know about it, so explain better and with details to help understand how to fix.

Copy link
Contributor

github-actions bot commented Oct 9, 2024

This issue is stale because it has been open 120 days with no activity.

@github-actions github-actions bot added the Stale No activity label Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Medium This issue may be impactful and needs some attention. Stale No activity Status: Pending Test This PR or Issue requires more testing Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

No branches or pull requests

2 participants