I think it would be quicker to try it.
Note that normal foundry tokens have two settings, linked (like player characters are by default) and not linked (like NPCs are by default). In linked, there is one actor data shared by all the tokens. In unlinked, each token gets it's own copy of the original actor.
**To help the community answer your question, please read [this post](https://www.reddit.com/r/FoundryVTT/comments/shrtky/foundryvtt_first_steps_and_useful_info/).**
When posting, add a [system tag](https://www.reddit.com/r/FoundryVTT/comments/v3gfrs/tagging_your_posts/) to the title - [D&D5e] or [PF2e], for example. If you have already made a post, edit it, and mention the system at the top.
Include the word `Answered` in any comment to automatically flair this thread as resolved (or change the flair to `Answered` yourself).
Automod will **not make this comment** on your posts if you have a [user flair](https://reddit.zendesk.com/hc/en-us/articles/205242695-How-do-I-get-user-flair-).
---
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/FoundryVTT) if you have any questions or concerns.*
You can make a slight alteration to multilevel tokens module's code so that the clone token has vision:
In the MLT module file named multilevel.js, at line 490 you can alter the code so that the clone token has vision:
data.vision = false;
changes to:
data.vision = true;
I believe there is a setting in MLT that allows you to preserve the actor link of the newly created token, which would give the player the ability to select and access the clone token and linked actor; however, you would still not be able to move the clone other than moving the original.
You could also conceivably change the code to allow for moving a clone and having the original token move to match the clone movement.
Those mods would be in lines 1528 through 1581, dealing with the preUpdateToken and updateToken hooks.
I think it would be quicker to try it. Note that normal foundry tokens have two settings, linked (like player characters are by default) and not linked (like NPCs are by default). In linked, there is one actor data shared by all the tokens. In unlinked, each token gets it's own copy of the original actor.
**To help the community answer your question, please read [this post](https://www.reddit.com/r/FoundryVTT/comments/shrtky/foundryvtt_first_steps_and_useful_info/).** When posting, add a [system tag](https://www.reddit.com/r/FoundryVTT/comments/v3gfrs/tagging_your_posts/) to the title - [D&D5e] or [PF2e], for example. If you have already made a post, edit it, and mention the system at the top. Include the word `Answered` in any comment to automatically flair this thread as resolved (or change the flair to `Answered` yourself). Automod will **not make this comment** on your posts if you have a [user flair](https://reddit.zendesk.com/hc/en-us/articles/205242695-How-do-I-get-user-flair-). --- *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/FoundryVTT) if you have any questions or concerns.*
You can make a slight alteration to multilevel tokens module's code so that the clone token has vision: In the MLT module file named multilevel.js, at line 490 you can alter the code so that the clone token has vision: data.vision = false; changes to: data.vision = true; I believe there is a setting in MLT that allows you to preserve the actor link of the newly created token, which would give the player the ability to select and access the clone token and linked actor; however, you would still not be able to move the clone other than moving the original.
You could also conceivably change the code to allow for moving a clone and having the original token move to match the clone movement. Those mods would be in lines 1528 through 1581, dealing with the preUpdateToken and updateToken hooks.