Improve external targetability for eggs (like for plugin/mod managers) #394
TekExplorer
started this conversation in
Ideas
Replies: 1 comment 2 replies
-
I believe Tags can take care of that |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
(ie, allow items like plugin/mod managers to easily target eggs without needing to edit the egg manually every time)
So, egg features are pretty cool, but i'd also say they're kinda limited, because it requires that anything that wants to define and use their own, suddenly needs the admins of every panel who use them to edit their eggs.
That or become so wide-spread that people go and edit all eggs in the egg repos.
This is kinda unfeasible.
Instead, I propose some kind of metadata or keyword system.
Hell, we can even keep using the egg features name, but so log as we add much more data for tools to be able to target with.
Information like if it supports forge mods, spigot plugins, paper plugins, if its a proxy, velocity plugins, and so on.
This can allow tools and frontend mods and plugins to better target certain eggs without needing to hard-code a list of egg uuids (which i AM glad is actually possible now)
So then, two possibilities. a dedicated metadata field, or adding much more data to the egg features field. Thoughts? Either way, We'd need to update pretty much all known eggs.
As the developer of the featherdactyl app, this can make it much easier for me to enable new features in-app without needing to bug the admins to edit their eggs
Beta Was this translation helpful? Give feedback.
All reactions