We had been facing an error where movement details were not getting written to their textbox for a while, and it appeared as though old data may have been wiped. Actually, they were still available in the src of Monster documents, but because their location conflicted with the CharacterMove data model, they were marked as invalid in Foundry and hidden from use.
This changeset moves the movement details storage location to system.details.movement, which is more apt for non-gamelogic string data, and creates a data migration where all actors are checked for the old data and moves it to the new location only if the new location is empty
We had been facing an error where movement details were not getting written to their textbox for a while, and it appeared as though old data may have been wiped. Actually, they were still available in the src of Monster documents, but because their location conflicted with the CharacterMove data model, they were marked as invalid in Foundry and hidden from use.
This changeset moves the movement details storage location to
system.details.movement
, which is more apt for non-gamelogic string data, and creates a data migration where all actors are checked for the old data and moves it to the new location only if the new location is empty