Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

GM edits to Token are not propagated to Players. Players edits are fine.

Hello All, By the way - I use JUMPGATE. So this post only applies to that version of roll20, though it may work in the regular version too. Just in case anyone else has this problem: As GM, when I drag a PC onto the map, the token setting for "Controlled By" is typically blank. This means every time I go to a new map, I have to set every player's "controlled by" setting so they can move their token. It's a big hassle. I did find a workaround. DOING THIS AS GM Open the character sheet Click on the EDIT the Character button (top of page) ADD your name to the 'In Players Journal" section SAVE CHANGES Click on the EDIT the Character button (top of page), again ADD your name to "Can Be Edited & Controlled By" section SAVE CHANGES Click on the EDIT the Character button (top of page), again Click 'Edit Token Properties" Make all the updates you want on the token (bars, dynamic lighting, etc...) SAVE CHANGES Drag the Player onto the board so their token appears Double-click the token Under Controlled By, ADD the players name, and your name SAVE SETTINGS Go to MY SETTINGS, upper right gear Click RE-JOIN AS PLAYER Click once to select the token you're working with...it should be outlined OPEN the CHARACTER SHEET for the PC you're updating Click on the EDIT the Character button (top of page) Click the USE SELECTED TOKEN Click SAVE CHANGES Close out the CHARACTER SHEET Go to MY SETTINGS, upper right gear Click RE-JOIN AS GM Delete the token on the map Drag the Character back onto the map Double-click the token to make sure the setting held This worked for me. It's rather tedious, but once set up, it makes adding players to a new map much easier. If you have savvy enough players. I think this would be a lot easier if they helped . That way you could avoid logging in as a player yourself. You could set all the settings for the token in one fell swoop - including the "can be controlled by" setting and then tell the player to 1) click on their token, 2) open their character sheet, 3) edit their character, 4) click the USE SELECTED TOKEN. I think that would do it, but I can't test it. Let me know if it works for you. Good luck!
1744322753

Edited 1744322846
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
Hi Brian! Much simpler method: Drag the token to the map. Make sure it is set up to represent the correct character. Link all bars and set all visions so that the token is exactly how you want it. Save the token editing window. Open character sheet (again, make sure that these are the same, you can double check by using the "open character" menu on the token's right-click menu. When the sheet is open, put it into edit mode (this is dependent on sheet, in general you will have an edit button at the top of the journal window, of a gear icon if this is a beacon sheet. Make sure both permissions are set correctly. Make sure you have the token selected, and press "Use Selected Token" When you pull out the character from the journal tab next, the default token should come with it. The character permissions are tied to the sheet , not the token . As long as the token represents the correct sheet, it should have the sheet's permissions. I'm not sure why you are logging in as a player in your steps above. This should not be necessary for any reason.
I will try that the next time a player creates a character, but the reason I'm logging in as a player, is because when I set the Controlled By setting as GM and save it - the setting doesn't stick. I have to be logged in as a player to get that setting to stick. I read about it in other searches that people were having the same problem, which is why I posted my work-around. I hope yours works. Thanks, Brian