-
Notifications
You must be signed in to change notification settings - Fork 2
Interpreters
Interpreters are the hearth of gui engine. They are the ones responsible for showing the XML in an appropriate gui.
- All interpreters support components
- Each interpreter supports the following the load and render functions.
This interpreter is pretty flexible. It allows creating chest guis of any size
Id: default Attributes:
- width - Required. Set the width of the component. This will only have effect when the gui is being embedded
- height - Required. The height of the gui. This sets the row of slots
- title - Required. The title the gui will have
- implicit-update - Optional. This defaults to true. When set to true, each time the gui is being rendered, compute functions will be computed again. This might make sense to turn off when your gui doesn't have any compute functions that should change between gui sessions, to save processing power
Opens a anvil gui
Id: anvil Attributes:
- title - Required. Set the title of the anvil gui.
- implicit-update - Optional. This defaults to true. When set to true, each time the gui is being rendered, compute functions will be computed again. This might make sense to turn off when your gui doesn't have any compute functions that should change between gui sessions, to save processing power
Opens a chest gui. It will always have a width of 9 and height of 3
Id: chest Attributes:
- title - Required. Set the title of the gui.
- implicit-update - Optional. This defaults to true. When set to true, each time the gui is being rendered, compute functions will be computed again. This might make sense to turn off when your gui doesn't have any compute functions that should change between gui sessions, to save processing power
Opens a dispenser gui. It will always have a width of 3 and height of 3
Id: dispenser Attributes:
- title - Required. Set the title of the gui.
- implicit-update - Optional. This defaults to true. When set to true, each time the gui is being rendered, compute functions will be computed again. This might make sense to turn off when your gui doesn't have any compute functions that should change between gui sessions, to save processing power
Example:
<gui interpreter="dispenser" title="§eDispenser Interpreter">
<component type="item" material="IRON_BLOCK" name="§eBack">
<on-click type="action">[container:previous]</on-click>
</component>
</gui>
Opens a enchanting gui
Id: enchanting Attributes:
- title - Required. Set the title of the gui.
- implicit-update - Optional. This defaults to true. When set to true, each time the gui is being rendered, compute functions will be computed again. This might make sense to turn off when your gui doesn't have any compute functions that should change between gui sessions, to save processing power
Opens a furnace gui
Id: furnace Attributes:
- title - Required. Set the title of the gui.
- implicit-update - Optional. This defaults to true. When set to true, each time the gui is being rendered, compute functions will be computed again. This might make sense to turn off when your gui doesn't have any compute functions that should change between gui sessions, to save processing power
Opens a workbench gui
Id: workbench Attributes:
- title - Required. Set the title of the gui.
- implicit-update - Optional. This defaults to true. When set to true, each time the gui is being rendered, compute functions will be computed again. This might make sense to turn off when your gui doesn't have any compute functions that should change between gui sessions, to save processing power
Thank you for choosing GuiEngine for your GUI development needs. Explore the Developer Docs and User Beginner Guide to unleash the full potential of this powerful framework and create stunning GUIs that leave a lasting impression on your players!