Skip to content

Token migrations for v11

jalensailin requested to merge jalenml/fix-token-migration-v11 into master

Intent

In Foundry v11, items on unlinked tokens had their UUIDs changed. It used to be of form "Scene.id.Token.id.Item.id", and now it is of form "Scene.id.Token.id.Actor.id.Item.id". Notice the "Actor.id" that was added. Hopefully this MR migrates that in all the places we track uuids.

  • This is meant for a hotfix
  • This is meant for the next release (see milestone)
  • This needs more reviewers than normal; there may be controversy or high complexity
  • This intentionally introduces regressions that will be addressed later
  • There is/will be documentation changes on the wiki
  • Please do not send commits here without coordinating closely with the owner
  • This is a Build System change

Related Issues

Steps to Test

  1. Create a world in v10,
  2. Create a scene with an unlinked mook token and an unlinked character token.
  3. To both tokens, add a weapon and load some ammo.
  4. Add an item and install some item upgrades into it.
  5. Add cyberware and install it into the actor (like a cyberarm).
  6. Install other cyberware into that cyberware.
  7. Add cyberdeck and install programs (and upgrades).
  8. Zip up this world for later use.
  9. In Master, migrate world to 0.88/FVTT v11.
  10. Observe that unlinked mook sheets will not open.
  11. Observe that character sheets may open, but installed items probably disappeared/lost their connection.
  12. Delete botched world.
  13. Unzip earlier v10 world.
  14. Checkout jalenml/fix-token-migration-v11, migrate to 0.88/FVTT v11.
  15. Ensure that unlinked mook sheets open.
  16. Ensure installed items all work as expected.

Merge request reports