"re-join as player" issues

Hi guys. I'm a new roll20 user and game creator. As creator/GM i have to check what my player's interface and view of the game actually looks like. But it seems that the "re-join as player" has actually a quasi non effect for me. All the GM tools and view stay actives. It seems only the fog of war is correctly displayed (parts of my map are covered in black accordly to what i set as GM) but, in this player mode, i'm still able to move or modify any other players or GM tokens exactly as if i were the GM... I'm almost certain it's not a hide/modify setting issue on the tokens. I tried to create another roll20 account to join my game as a "true" external player, and everything is fine this way. I could use it to test my game, but i have to delog, relog with my other account and reboot the game each time... I also tried the crtl+L shortcut, no more sucess. I thought when the "re-join as player" mode was set, the experience was the real player experience (so no status bar appearing or nb of PV remaining for the enemy's token, no way i could move enemy token...) Did i set something wrong ? Thanks for your help

Do you have the campaign open in more than 1 Browser Tab? IF so, this might be your Problem! "Re-Join as Player" for me hides all the Layer selection and other controls. I only see the shortened sidebar and in the journal only those Handouts / characters I set the permission for. 

You're right, maybe it's open on other browsers at my home, on another laptop. I will check for this tonight.

Hi Faman_MJ! To be absolutely and totally certain (Re-join as Player does not remove permissions you specifically gave to yourself as GM, for example), I suggest the use of a  Dummy Account . If you log into that account through a private browsing window, you'll completely avoid confusing Roll20.

Upon closely re-reading the OP, this sounds like a Bug or a Glitch, based on all the factors combined that Faman said, if it really happened just like that. He says he tried the Dummy Account method and it works as-expected for the Dummy.  I would advise, Faman, try it a couple more times, to make sure that's what happened.  The GM Toolbar including the Layers still continuing to show in "Relaunch as Player" mode for Faman is the biggest clue, as this factor elminates any possible crossover in Token Permissions setups.  Having your Home computer (a different computer) open to GM Mode is something that shouldn't matter in this situation. You're not hitting REFRESH on your browser are you? There is a surprise with Refresh, if you have multiple browsers open to different Roll20 Games at the same time, but this is not what Faman seems to be describing. 

Ah, I missed the dummy account reference in the OP.

Using a dummy account as kiethcurtis described is the only way to really see what a player will see, because even though it says "rejoin as player", you will still be able to see the GM layer and other "GM only" information. Instead of completely logging out of roll20 and logging back in on with your dummy account, log in with the dummy account using a second browser. I normally use Chrome as my preferred browser and log in with my dummy account  using Firefox. That way I can keep both windows open simultaneously and see the player's view update as I make changes under my "real" account. I read that you can also do this using the same browser by setting up different profiles, but I've never tried that method.

Hi Faman_MJ,  To add to what the others have said, Rejoin as Player has had a long history of still having elements of a GM.  This is one of the major reasons (there are others) that a Dummy Account is preferable, as you have discovered.  Whenever I am setting up things and I want to see how things look for the players I do a side-by-side with Chrome for one account and Firefox for the other. Or Chrome for one account and Incognito Chrome for the other account. 

Ok. Many thanks to all of you for the clarification. You're not hitting REFRESH on your browser are you? There is a surprise with Refresh, if you have multiple browsers open to different Roll20 Games at the same time, but this is not what Faman seems to be describing.  Actually, it's not. I tried many refresh, clear cache and cookies, tried on firefox... It seems the dummy account is the best way for me. I will continue to use it as its seems to be more reliable, and "Rejoin as player" only when i want to quickly set and check the fog of war. I normally use Chrome as my preferred browser and log in with my dummy account  using Firefox. That way I can keep both windows open simultaneously and see the player's view update as I make changes under my "real" account. I read that you can also do this using the same browser by setting up different profiles, but I've never tried that method. Great idea. Thanks Rick A.  for this tip. I will try this. Many thanks to all for your help.

Rick A. said: Using a dummy account as kiethcurtis described is the only way to really see what a player will see, because even though it says "rejoin as player", you will still be able to see the GM layer and other "GM only" information. I think you might be conflating two features. While previewing sight through a token , a GM will still see the GM layer and other GM information. When using "Rejoin as Player", they are truly a player. The danger comes when they have specifically assigned themselves permissions to particular tokens. They will still retain those permissions, and that can lead to undesirable results when testing a dynamic lighting set up, for instance.

I sit corrected. :) keithcurtis said: Rick A. said: Using a dummy account as kiethcurtis described is the only way to really see what a player will see, because even though it says "rejoin as player", you will still be able to see the GM layer and other "GM only" information. I think you might be conflating two features. While previewing sight through a token , a GM will still see the GM layer and other GM information. When using "Rejoin as Player", they are truly a player. The danger comes when they have specifically assigned themselves permissions to particular tokens. They will still retain those permissions, and that can lead to undesirable results when testing a dynamic lighting set up, for instance.