bedrock-development
Advanced tools
Changelog
[1.1.3] - 3/7/2023
Bug fixes.
bed new item --type attachable
would fail to add a transition back to the no_item
state after adding multiple attachables.Changelog
[1.1.2] - 3/3/2023
Bug fixes.
bed pkg import
always wrote lang file changes to en_US.lang
instead of the file on the package.Changelog
[1.1.1] - 3/2/2023
Bug fixes.
bin
was not specified for this project, so it could not be run with bed
.Changelog
[1.1.0] - 3/2/2023
This version deprecates the standalone CLI Tool in favor of folding the CLI directly into this project.
bed new entity
command has two new options: --no-geo
and --no-texture
wich prevents the command from making a new geo and texture file respectively when used with --client
.bed new item
's type
option can accept a new value attachable
which for now is identical to weapon
, but in the future will create a basic item with an attachable, while weapon will create an item with damage values, durability, etc.'bed entity property add
command has a new option: --event
which streamlines the old flow of running bed entity property add
to create your properties, and bed entity property event
to create events to set the values. Now adding --event
will automatically add an event for every valid value a property can have (everything within its range
, or everything in its values
). Though you may still want to use bed entity property event
if you want to create events that set the value to things like q.property('property_name') + 1
.--lang
option have been changed. Adding a lang entry is now the default, and the --no-lang
has to be used if you don't want a lang entry.--file
option have been changed. --file
is now a mandatory field, and the command cannot be run without it. Providing --file
without a value still affects all entities, but making the option required should reduce the chance of accidentally affecting all entities in a project without meaning to.