Kube Utils Changelog
[20.1.0]
Changed
- Backported to 1.20.1
Kube Utils Changelog
[20.4.0]
Changed
- Updated to 1.20.4
Kube Utils Changelog
[0.1.3]
Added
- Released for 1.18.2
Kube Utils Changelog
[1.0.0]
Added
- Ported 1.19.2
Kube Utils Changelog
[0.1.4]
Added
-
A new
ku.player.starter-items
event that, once used and successfully gave items, will stop running-
You can define an item and equipment slot (For things like armor) too ```javascript onEvent("ku.player.starter-items", event => { // Item.of is optional here event.addItems("5x minecraft:gold_ingot", Item.of("2x minecraft:grass_block"))
// Valid options are part of the EquipmentSlot Enum event.addEquipmentItem("chest", "minecraft:golden_chestplate") event.addEquipmentItem("offhand", "minecraft:stone") }) ```
-
-
A new
Ku.Player
class that brings some helpful methodsshowActionBar(text: string, color?: Color = Color.WHITE, bold = false, italic = false)
- Uses the built-in client action bar to display a message. This is already supported through the player class but this method allows for less boilerplate and stable code ports
showActionBarComponent(component: Component)
- Mostly the same as the above but gives you access to use a JS Object as your component which might look a something like this
javascript const player = Ku.Player(event.player); player.showActionBarComponent({ text: "Hello", bold: true })
clearStarterItemsFlag
- This method simply reset the flag for the
ku.player.starter-items
meaning on the next login, the player will be given the items once again isClientSide
- Lets you know if the client being wrapped is client side. This was mostly a helper for my code but it could be helpful
Changed
- Renamed the internal binding classes to be suffixed with Ku so they're visually different from vanilla and KubeJS
Kube Utils Changelog
[1.0.1]
This is features ported up for 0.1.4 (1.18.2 update)
Added
-
A new
KuEvents.playerStarterItems
event that, once used and successfully gave items, will stop running-
You can define an item and equipment slot (For things like armor) too ```javascript KuEvents.playerStarterItems(event => { // Item.of is optional here event.addItems("5x minecraft:gold_ingot", Item.of("2x minecraft:grass_block"))
// Valid options are part of the EquipmentSlot Enum event.addEquipmentItem("chest", "minecraft:golden_chestplate") event.addEquipmentItem("offhand", "minecraft:stone") }) ```
-
-
A new
Ku.Player
class that brings some helpful methodsshowActionBar(text: string, color?: Color = Color.WHITE, bold = false, italic = false)
- Uses the built-in client action bar to display a message. This is already supported through the player class but this method allows for less boilerplate and stable code ports
showActionBarComponent(component: Component)
- Mostly the same as the above but gives you access to use a JS Object as your component which might look a something like this
javascript const player = Ku.Player(event.player); player.showActionBarComponent({ text: "Hello", bold: true })
- Mostly the same as the above but gives you access to use a JS Object as your component which might look a something like this
clearStarterItemsFlag
- This method simply reset the flag for the
ku.player.starter-items
meaning on the next login, the player will be given the items once again
- This method simply reset the flag for the
isClientSide
- Lets you know if the client being wrapped is client side. This was mostly a helper for my code but it could be helpful
Changed
- Renamed the internal binding classes to be suffixed with Ku so they're visually different from vanilla and KubeJS
Kube Utils Changelog
[1.0.2]
Added
- Added a new Level method to allow for finding a single block within an area
findSingleBlockWithinRadius
- Added a
triggeredBy
field to theKuEvents.playerStarterItems
event as we now trigger the event for a player joining as well as a player changing dimension. If the event does not place and item in the inventory. We assume it failed and will retry on either a join or a dimension change
Kube Utils Changelog
[1.0.3]
Changed
- Updated support to KubeJS 6.1! This will cause issues when attempted to use with 6.0. You have been warned!