You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I open the same gui for multiple players at once and one of them clicks a GuiStateElement, the Element is changed for the other players too. If I understand this api correctly, the goal is to have one InventoryGui instance that you open for all players. If you need to change something dynamically, you use DynamicGuiElements. If I have to create a new InventoryGui for every player, then why is there a DynamicGuiElement?
The text was updated successfully, but these errors were encountered:
Well the library wasn't really designed with such usage in mind (one instance was meant to be self-contained and always provide the same information no matter who viewed it, a new instance was meant to be created per player) so providing different information to different players was an afterthought and that can be done now by using the DynamicGuiElement.
So it's already possible to do what you want: Use a DynamicGuiElement and return the appropriate GuiStateElement per player so I'm unsure if the GuiStateElement really would need to change/be expanded to support that natively as that would just add more overhead.
If I open the same gui for multiple players at once and one of them clicks a GuiStateElement, the Element is changed for the other players too. If I understand this api correctly, the goal is to have one InventoryGui instance that you open for all players. If you need to change something dynamically, you use DynamicGuiElements. If I have to create a new InventoryGui for every player, then why is there a DynamicGuiElement?
The text was updated successfully, but these errors were encountered: