Dylan T.
Dylan T.
Currently, a duplicate key appearing anywhere in some NBT data tree will cause the entire tree to be undecodable using this library. This is severely problematic for legacy PM worlds,...
There's no sensible use case for this that can't be filled by simply doing `new ListTag`.
This was originally added as `protected` when the new `toString()` format was implemented. However, it would be useful for third party implementations (in PM it would be mainly useful for...
If recursive references appear in NBT trees, the encoder will loop until either it segfaults or the process runs out of memory. Recursive references should be detected to prevent this...
This will be needed for 1.13 world saves. This is identical to `IntArray` but with 8 bytes per member instead of 4.
Usage examples are particularly needed for the encoder/decoder API.
Far too often I've seen users who serialize() internal data (like item NBT) in order to store it. This is not only stupid (because it defeats the entire point of...
incomplete list of things that should be tested: - CompoundTag/ListTag API - [x] iterating in foreach - [ ] getValue() - [ ] getters and setters - [ ] array-access...
The maximum possible size of a TAG_ByteArray's payload is 2GiB, but this is not currently capped by the library. While this is a less immediate problem than the old StringTag...
Experimental gameplay is no longer enabled by a single flag in 1.16.100+.