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 .
×

Token Sight (DM vs. Player Placement)

I could be missing something entirely obvious but am encountering an issue with token sight. I'm using a map with Dynamic Lighting that has the below settings in place. When a player drags their token from the journal to the map and I check "Has Sight", they are able to see the map/token and control it as normal. However, when I (as DM) drag their token from the journal to the map and check "Has Sight", they are unable to see the token or map, at all, and can't even select the token if I tell them where it is. I encounter the same issue if I use Updated Dynamic Lighting and things like Bright Light/Darkvision/Daylight mode etc, which leads me to believe it has something to do with the distinction between player and DM. The token has both myself and the player as "can control" and "can edit". Any help would be greatly appreciated!
1588882277

Edited 1588882373
1st take yourself off of can control and edit.  You as the DM always have that power, even when it doesn't have you in those slots, but I've heard that having yourself in them can cause bugginess.  Next, have you set up the token completely (meaning sight, hp bars, represents character and then saved as the default token on sheet through the edit tab on the sheet)?  Once you do that, they should be able to drag it onto the map and have all of those things already set rather than having to be set each time.
Also, be sure you are dragging their token to the Objects & Token Layer.
1588885242

Edited 1588885262
Well, I feel dumb but didn't realize that I had to default the token to represent a player character. Dragged all the PC's on to the map, configured sight settings, then "replaced" their existing token with the newly-configured one as default. All fixed and works like a charm! Thanks very much for the quick replies.