[JRoy]

Closes #31

[pop4959]

Not all too familiar with this; how is it intended to be used?

[JRoy]

Not all too familiar with this; how is it intended to be used?

createkit uses AbstractItemDb to serialize data, MetaItemStack parses that data.

[pop4959]

Not all too familiar with this; how is it intended to be used?

createkit uses AbstractItemDb to serialize data, MetaItemStack parses that data.

I understand that bit, what I meant was how this actually works. From the code it looks like it's adding a new item meta syntax for page<#>:<content> and dumps everything in there. It might be better if we used the method already used by book to save and load data.

[JRoy]

Not all too familiar with this; how is it intended to be used?

createkit uses AbstractItemDb to serialize data, MetaItemStack parses that data.

I understand that bit, what I meant was how this actually works. From the code it looks like it's adding a new item meta syntax for page<#>:<content> and dumps everything in there. It might be better if we used the method already used by book to save and load data.

from what I understand, that was made for making the content of a book match that of a text file on disk, book.txt. If I used that, it would break backwards compatibility :/

[pop4959]

Ah yeah good point, we'd also need to write into that too and I don't think anything does that currently (also ew, txt). I feel like there's probably still a better way than to literally dump the text wholesale into YML and generate a bunch of messy keys. If we're going into that direction then #3248 is a better solution.

[mdcfe]

Do we want to consider serializing book and quills? If they use BookMeta too, I see no reason why we couldn't allow for this.

It also currently preserves newlines: