I've been told more than once to implement the Adventure API, and I generally think that's a great idea. My only issue with that is that I don't want to lose the ability to use UILabs on Spigot or any other environment that doesn't natively support Adventure API.
After some thinking, I've come up with an idea: A system that supports both String and Component input via a custom object that I'm for the time being just going to refer to as TextObject.
Furthermore, I've been wanting to implement the PlaceholderAPI as well and I think TextObject would be the perfect place for that. Like Adventure API, PlaceholderAPI should should only be used if available. It should be optional, not required.
Let's recap,
The TextObject must:
- Support both
String & Components (if AdventureAPI is found)
- Support Placeholders (If PlaceholderAPI is found)
- Compatibility with Inventories and ItemStacks
Let me know your thoughts on this and and as always anyone is welcome to make PR's or give their opinion on this.
I've been told more than once to implement the Adventure API, and I generally think that's a great idea. My only issue with that is that I don't want to lose the ability to use UILabs on Spigot or any other environment that doesn't natively support Adventure API.
After some thinking, I've come up with an idea: A system that supports both
StringandComponentinput via a custom object that I'm for the time being just going to refer to asTextObject.Furthermore, I've been wanting to implement the PlaceholderAPI as well and I think
TextObjectwould be the perfect place for that. Like Adventure API, PlaceholderAPI should should only be used if available. It should be optional, not required.Let's recap,
The
TextObjectmust:String&Components(if AdventureAPI is found)Let me know your thoughts on this and and as always anyone is welcome to make PR's or give their opinion on this.