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 for backup UI backends #11

Open
Trigary opened this issue Dec 14, 2019 · 1 comment
Open

Support for backup UI backends #11

Trigary opened this issue Dec 14, 2019 · 1 comment

Comments

@Trigary
Copy link
Owner

Trigary commented Dec 14, 2019

Support for backup UI backends, eg. inventory, conversation API, Tom's ChatMenuAPI based UI "rendering" backends should be added. They should probably be treated the same way as Iodine GUIs. A function should exist that determines which backend to use for a given player. The backends must have a method that returns whether a specific player is supported.

The class linking the backends together should be able to open a new GUI instance for each player or reuse the existing instance. It should be kept in mind that while Iodine GUI instances can be shared and are synced between multiple players, other backends might not have that property.

@Trigary
Copy link
Owner Author

Trigary commented Dec 18, 2019

I now believe that this should be a separate project since it is just a wrapper around this one.

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

No branches or pull requests

1 participant