Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: map cell change breaks lib tokens #3908

Closed
Jmr3366 opened this issue Apr 9, 2023 · 2 comments · Fixed by #3912
Closed

[Bug]: map cell change breaks lib tokens #3908

Jmr3366 opened this issue Apr 9, 2023 · 2 comments · Fixed by #3912
Assignees
Labels

Comments

@Jmr3366
Copy link
Contributor

Jmr3366 commented Apr 9, 2023

Describe the Bug

When you change the Map - Cell type to anything other than what the campaign map loaded with, lib tokens appear to fail (remove the .zip from the file to test)
LibBreakOnCellTypeChange.cmpgn.zip

To Reproduce

  1. Open attached campaign
  2. Move the elf token to display chat output
  3. Change the cell type via Map - Edit Map - Cell Type to something else
  4. Move the elf token - no display in chat output

Expected Behaviour

lib tokens should function properly

Screenshots

No response

MapTool Info

v1.13.0, v1.13.0b1

Desktop

Win 11

Additional Context

No response

@Jmr3366 Jmr3366 added the bug label Apr 9, 2023
@Azhrei
Copy link
Member

Azhrei commented Apr 9, 2023

Are you storing the token id for the lib token and trying to reuse it? There was a recent feature patch to maintain consistent token ids across campaign loads, but Edit Map is essentially deleting the map and creating a new one. It probably didn't receive the same update...

@Jmr3366
Copy link
Contributor Author

Jmr3366 commented Apr 10, 2023

There are two tokens, one is a lib:token (Dragon) with a onTokenMove macro. It has one line [h: broadcast(getLastPath())]
If I change the cell type to anything, it no longer broadcasts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants