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

Add a tool to auto-generate rendered MiniMessage strings #52

Open
zml2008 opened this issue Feb 13, 2022 · 5 comments
Open

Add a tool to auto-generate rendered MiniMessage strings #52

zml2008 opened this issue Feb 13, 2022 · 5 comments
Labels

Comments

@zml2008
Copy link
Member

zml2008 commented Feb 13, 2022

Currently, the examples for each MiniMessage tag are produced manually by entering the MiniMessage string into a game instance and taking a screenshot.

We should be able to rig something up to generate this automatically, taking in a properties file of IDs and MiniMessage strings to generate and running the Minecraft client's font renderer headlessly to produce images from this file.

@kezz
Copy link
Member

kezz commented Feb 13, 2022

Perhaps KyoriPowered/adventure-webui#67?

@rymiel
Copy link
Member

rymiel commented Feb 13, 2022

What about webui? (KyoriPowered/adventure-webui#67 is sorta related but that one is more long-shot)

@zml2008
Copy link
Member Author

zml2008 commented Feb 13, 2022

I'd like to make the documentation site fully functional as a static site -- an embed would be useful for users to try things out, but I wouldn't want to have to render a whole bunch of strings on every page load. I'm not sure webui is super suited to running at build time.

@MiniDigger
Copy link
Member

we can both have an embed for try-it-out kinda stuff and expose an api that the docs can use at build time (generate html+css or generate pictures, idk what would be better)

@MiniDigger
Copy link
Member

Maybe SVG could be a good middle ground?

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

No branches or pull requests

4 participants