Litemapy

Latest version: v0.10.0b0

Safety actively analyzes 682387 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 3

0.10.0b0

* Fix entity rotation support.
* Fix block state not being comparable with other types.
* Enforce valid resource location name. If a block name would not be valid for Minecraft, Litemapy prevents your from creating the block state by raising an `InvalidIdentifier` exception.

0.9.0b0

* Drop Python 3.8 support, Python 3.9 is now the minimum supported version
* All methods and field are now proper snake_case.
Old names can still be used but are deprecated and will eventually be removed.
* Blocks can now be accessed from regions using bracket notation:
`block = region[x, y, z]`, `region[x, y, z] = block`
* The built-in `in` keywork can now be used to test whether a region contains a block:
`burning = BlockState("minecraft:fire") in region`
* Added `Region.replace()` to replace all occurrences of a block in a region with a different one
* Litemapy is now aware of litematic subversions
* Type hints are now provided with annotations instead of Sphinx docstrings

0.8.1b0

* Massively improve saving performance by using Numpy to count non-air blocks (by llGaetanll).
* Obsolete region palette entries are now pruned.
* `BlockState` is now hashable.
* Region palettes are now exposed as read-only properties.

0.8.0b0

* Breaking change: the `BlockState` constructor no longer takes properties as a single `properties` argument.
Each property must be supplied as its own keyword argument instead.
E.g. `BlockState("minecraft:acacia_log", facing="west")`
* Added `BlockState.with_properties()` and `BlockState.with_blockid()` to create copies of block states
but with different ids and properties.
* Added `Region.filter()` to allow for efficient block replacement.
* Schematic palettes are now always optimized before saving

0.7.0b0

* Method to convert regions to the sponge schematic NBT format
* Fix crash with litematics created by newer versions of Litematica "id -> The required key is missing in the (Tile)Entity's NBT Compound",
It was caused by Litematica no longer specifying a TileEntity's ID in its own NBT structure
(it can be assumed by looking the block at the TileEntity's coordinates)
* Made internal list fields access only (Regionentities, Regiontile_entities, Regionblock_ticks, Regionfluid_ticks)

0.6.0b0

* Method to convert regions to the vanilla Minecraft structure NBT format

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.