Allow selection tools to be stored in blueprint library

[ratchetfreak]

In FFF number 0xFF it was mentioned that selection tools cannot be stored as blueprints in the library or books

The big limiter to that would be the possible extra state associated with it. The upgrade planner for example stores what is being upgraded to what. This state needs to survive during export and import and transfer to other saves to be useful.

One way to solve that would be serialization to a string, the selection tool when deposited into a book/library has to condense all its state as a string, that string is then used in the export string along with mod-id and other relevant meta info.

If a book with a modded selection tool is imported into a save without that mod show a warning and drop the selection tool from the import.

I'm not entirely sure how that serialize/deserialize interface should look like but it must be possible to opt out.

[Rseding91]

It's probably never going to happen. The blueprint library stores blueprints and only blueprints. Making it store other stuff is essentially completely re-writing it and nobody is going to do that any time soon.

[ratchetfreak]

It's probably never going to happen. The blueprint library stores blueprints and only blueprints. Making it store other stuff is essentially completely re-writing it and nobody is going to do that any time soon.

in 0.17 it (and books) will also store upgrade planners,

When a mod needs a ton of selection tools the inventory and hotbar is going to fill up quite fast, allowing books to be used with them is going to reduce that a lot.

once you reduce the selection tool to the mod id, item prototype name, the name to display when looking at it in the library, any custom icon stuff and the serialized string it's not that different to a exported blueprint