Lucas

Another point of interest would be how to include API methods for the legacy system (and its inter-operation with the new system), and how to phase them out when support...

There are also two other ideas that I think are worth considering: ### Separate named root tags from nameless root tags The idea here is to clearly delineate the differences...

Sorry for the late reply as well. It works just perfectly for my use case. As for the named tag, it was more of a suggestion. If you already considered...

Yes, that is it. When the nbt data starts with a 0 (tag end), nothing follows. That has been the behavior before and after the removal of root tag names...

Another issue with the way things are done at the moment is related to change I mentioned on https://github.com/BenWoodworth/knbt/issues/13#issuecomment-1747769762. This recent change in 23w40a will allow not only Compound Tags,...

Yes, the issue I'm trying to point out is that very assumption (named tags are compounds with one entry), which in my view at least has always been more of...

Awesome, I will gather my ideas and make a post here when I have some time then. Some of the points are still more aligned with #36, so I will...

> Probably not the best place to put this stuff, you should create a gist :) > > If I understand it correctly, the root tag is a feature of...

> Sorry for the late reply! The new design (in [the issue description](https://github.com/BenWoodworth/knbt/issues/29#issue-1660087615)) gets rid of the root compound entirely, so `encodeToNbtTag`/`encodeToByteArray`/etc. work exactly the way you want. Nameless, "raw",...