0.4.0

Added

• Copy light sources to another world (#11). A new Import or Export Light Sources menu in the module settings saves the world's light sources, the GM's edits to sources that modules provide, and the System Compatibility settings to a JSON file, and loads such a file in another world. The import shows what it will change before writing anything. Compatibility is applied only between worlds of the same game system. A source whose item does not exist in the new world is still imported and keeps working by name and type.

Changed

• Light sources registered by other modules are no longer stored in the world. Each module registers its sources again every session, on every client, and only the GM's own sources and the GM's edits are saved. A module that is disabled takes its sources with it, unless the GM edited them. Modules using the API must call registerSources on every client, not only the GM's. See the API docs.
• A source's id is its item's UUID. activate takes that id, and getActive reports it as sourceId. A pattern's id is the name its module registered it under.
• Light sources configured before this version are not kept. The module now stores them in a new setting, so a world updated from 0.3.0 starts with no sources of its own and has to set them up again. Lights burning during the update can still be put out and still burn out, but they can no longer be dropped, picked up or handed over.

Fixed

• A light with no color works in Daggerheart. A pattern whose color was left blank made Daggerheart throw an error when it was lit, and the token stayed dark. Such a light now shines with no tint, as it always did in other systems.
• A light source the GM removes stays removed. Removing a source registered by another module used to last only until the next session, when the module registered it again. It is now listed under Removed module light sources, where Restore brings it back.
• registerCompatibility no longer tries to write world settings from a player's client, which only a GM may do.