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

Support all Vanilla Component types in MiniMessage #678

Closed
5 tasks done
zml2008 opened this issue Feb 12, 2022 · 0 comments · Fixed by #843
Closed
5 tasks done

Support all Vanilla Component types in MiniMessage #678

zml2008 opened this issue Feb 12, 2022 · 0 comments · Fixed by #843

Comments

@zml2008
Copy link
Member

zml2008 commented Feb 12, 2022

Currently, MiniMessage only provides tags for some of the vanilla component types, but for completeness sake we should support all of them.

Supported

  • text (as literal content)
  • KeybindComponent (via <key:key.id>)
  • TranslatableComponent (via <tr:lang.key[:args...]>, and translate or lang aliases)

Not yet supported

  • SelectorComponent
  • ScoreComponent
  • BlockNBTComponent
  • EntityNBTComponent
  • StorageNBTComponent
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants