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

Scoreboard "objective_criteria" does not have entries such as "teamkill.<team_color>" and "killedByTeam.<team_color>" and an error occurs #1474

Closed
Ho9tocraft opened this issue Jul 4, 2024 · 7 comments · Fixed by #1501
Assignees
Labels
🐛 bug Something isn't working 👍 good first issue Issues that are easy to work on for new code contributors /java-edition
Milestone

Comments

@Ho9tocraft
Copy link

As the title says, I have no idea how to write "spyglass.json" or where to put it, and the site that explains it is still under construction, so I am unable to do anything about it.

@MulverineX
Copy link
Member

The Spyglass config goes at the root of your workspace. We will investigate this report soon

@Ho9tocraft
Copy link
Author

The problem with Spyglass.json has been solved, but still the problem as described in the title has not been solved. if you say you can solve the problem with mcdoc, I would like to ask you to improve the wiki. As it is now, it is more likely that beginners will be confused.

@MulverineX
Copy link
Member

This is a bug with the extension, not with vanilla-mcdoc nor mcmeta.

@MulverineX MulverineX added 🐛 bug Something isn't working 👍 good first issue Issues that are easy to work on for new code contributors /java-edition labels Jul 9, 2024
@misode misode self-assigned this Jul 9, 2024
@misode misode added this to the Release 4.2.0 milestone Jul 9, 2024
@Ho9tocraft
Copy link
Author

Could a hotfix-like version update reflect this as soon as possible? The teamkill and killedByTeam errors continue to occur even after Release 4.1.0 has been applied, because the changes that are currently scheduled to be applied in Release 4.2.0 have not yet been reflected.

@MulverineX
Copy link
Member

We should probably release 4.2 soon yeah, I'll try to push it along

@Ho9tocraft
Copy link
Author

It has been two weeks since I heard back from them that they will be released soon. But what is the reality? The number of open issues is only increasing, and nothing has been reflected in the VSCode extension.
This has not resolved the bug reports received from users, and the errors still continue to appear. If the merge is done, it would be easy to release it as a hotfix already. Even if they are stuck in the review process, it would be easier to pass this as a stand-alone fix.
Of course, we are aware that they have their own circumstances, and we understand that they would like to add and improve functions all at once and only fix bugs.
Even so, this bug needs to be fixed and patched as soon as possible. As a developer of data packs.
I hope you will do your utmost to fix this bug, including moving up the schedule.

@TheAfroOfDoom
Copy link
Contributor

@Ho9tocraft please be patient. this team consists entirely of volunteers and most of us have been on vacation.

we plan on releasing a new patch soon to include some new features and fixes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working 👍 good first issue Issues that are easy to work on for new code contributors /java-edition
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants