search

grandseiken / foundryvtt-multilevel-tokens

Multilevel tokens for Foundry VTT
MIT License
42 stars 20 forks source link

Cloned NPC Tokens not moving within the target zone when the original token moves within the source zone #106

Open Revonworc opened 3 years ago

Revonworc commented 3 years ago

Cloned NPC Tokens are not moving within the target zone when the original token moves within the source zone. I can't seem to get this to not happen and I don't know why. I'm using Foundry version 0.8.8, 5e version 1.4.2, Multilevel Tokens version 1.5.2, Plutonium version 1.36.0, and Skill Customization version 2.3.0, if that helps at all. Does anyone know why this happens or how to fix it?

Revonworc commented 3 years ago

Upon further experimenting, it seems only a single NPC token was effected, and subsequent new ones I placed worked as intended.

Biglulux commented 3 years ago

I've also had this issue, and I was at a loss until I read your second comment. It appears that any tokens with a condition placed on it (using the right click menu -> assign status effects) will not update in a target zone when moved from within the source zone. Note that they do show up in the target zone when they are first moved into the source zone, and they disappear when moved outside of the source zone, but they do not update their position within the target zone when moved from one tile in the source zone to another tile in the source zone. Getting rid of all conditions on a token will cause the token to behave correctly.

Here's the error from my console log. foundry.js:16786 Uncaught (in promise) TypeError: Cannot read properties of null (reading '_preUpdate') [No packages detected] at TokenDocument5e._preUpdateTokenActor (foundry.js:16786) at TokenDocument5e._preUpdate (foundry.js:16725) at async ClientDatabaseBackend._preUpdateDocumentArray (foundry.js:8868) at async ClientDatabaseBackend._updateEmbeddedDocuments (foundry.js:8824) _preUpdateTokenActor @ foundry.js:16786 _preUpdate @ foundry.js:16725

Shuggaloaf commented 3 years ago

I am also getting this issue. I can confirm it is related to cloning as I removed tokens from a cloned area and refreshed FVTT and the error went away. Moving the tokens back and the issue reappears.

However, I do not think it is linked to conditions as Biglulux mentioned. I narrowed it down to a token that had no status effects or active effects either. I won't report my error message as it was basically the same as above, just with different numbers after the colons.

The only thing I can think of, and only because Revonworc mentioned Plut., is that there was a brief period where I had updated Plut. but not the 5e systems. Actors imported during that time had a blank armor class issue (and possibly other, unseen issues). After updating 5e, that issue went away. But the token I was just having this issue with was one of those. Could be pure coincidence, and I'm not even sure if @Biglulux has Plut. installed. I can say for sure though that it happened to me without any status effects checked in the right-click menu.

Biglulux commented 3 years ago

@Shuggaloaf I do have Plutonium installed.

Mystara1 commented 2 years ago

I've run into this 'feature'. Running Foundry 8.9, Pathfinder 79.10. After setting up clone area and logging out the tokens no longer clone movement. Entering and leaving works. Making new token clones movement until logging out. Then the 'new' token stops working. Creating most tokens using SBC PF1 statblock convertor. If I create a 'raw and blank' token then I have no problems even through a log out. SBC creates the tokens with a Permanent Conversion Buff placeholder. If I delete said buff before dropping the token on the scene then again no problems. Hoping this helps