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

Odd Waypoint Bug

We logged in for our weekly game last night, I first explained a few of the new features introduced with the Rugged Re-Roll launch. When I got to the explanation about waypoints, my players found that no matter what they did their character icons would always rubber band back to their original start point. It wasn't until I moved them once as GM that the players could then move their character icons around as usual. Not a game-breaking bug but odd nonetheless.
Were the players able to move their tokens without the "rubber banding" if they weren't using the waypoints?
Right, even just regular movement attempts did not work. I had to move them all at least one space myself as GM before they again had control over their character icons.
1387306190
Gauss
Forum Champion
Please send me a join link and I will come take a look.
Well, the problem resolved itself once I moved their characters 1 space, I don't think I could duplicate it now.
1387342257
Gauss
Forum Champion
Ok, if it happens again please let us know.
Well, I do have a duplicate campaign for another group of players that hasn't been touched yet, so the condition may still exist there.
1387343334
Gauss
Forum Champion
If it does go ahead and send me a join link to that campaign please.
I have a campaign I'm in that's doing the same thing (GM hasn't logged since the update). I can't send an link because I'm not GM, but it affects all properties of a token. I have the console log if you'd like me to PM it or post it?
1387397154
Gauss
Forum Champion
Emile , please have your GM send me a join link. Go ahead and post the console log.
FIREBASE WARNING: update at /campaign-160857-9nqyoUz9Uaw-xaSTMvFIKg/graphics/page/-JAiOnmsraTPiYrKYBcF/-JAic_9Ya6F6Eti2-iOn failed: permission_denied firebase.js?2:34 setting src app.js?1387244832:24 Do top/left snapping app.js?1387244832:22 Update changed! app.js?1387244832:22 FIREBASE WARNING: update at /campaign-160857-9nqyoUz9Uaw-xaSTMvFIKg/graphics/page/-JAiOnmsraTPiYrKYBcF/-JAic_9Ya6F6Eti2-iOn failed: permission_denied firebase.js?2:34 Do top/left snapping app.js?1387244832:22 Update changed! app.js?1387244832:22 FIREBASE WARNING: update at /campaign-160857-9nqyoUz9Uaw-xaSTMvFIKg/graphics/page/-JAiOnmsraTPiYrKYBcF/-JAic_9Ya6F6Eti2-iOn failed: permission_denied firebase.js?2:34 Render character view app.js?1387244832:28 Render character editor app.js?1387244832:27 Render character view app.js?1387244832:28 FIREBASE WARNING: update at /campaign-160857-9nqyoUz9Uaw-xaSTMvFIKg/graphics/page/-JAiOnmsraTPiYrKYBcF/-JAic_9Ya6F6Eti2-iOn failed: permission_denied firebase.js?2:34 window resize on that note, I dragged an image out of my journal entry on to the table, and it gives me full token control of it. Not sure if this is just leftovers from the update. Also, I PMed him, but I'm not sure if he'll be getting back to you before game time :(
1387405005
Gauss
Forum Champion
Emile and I have determined the following: 1) The moment a GM makes an alteration to a map (such as renaming the map) or moves the token the problem goes away for that map's token. 2) The "permission_denied" Firebase Warning happens each time the user tries to move a token that is going to have the bug. 3) After the GM moves the token and the user can move the token again the Firebase Warning does not happen again for that map's token.
Yep, that sounds about right... I've been at work all day (still am) and haven't had a chance to send you an invite, Gauss. Do you still want to look at my campaign later this evening, or do you think you have enough information already?
1387406570
Gauss
Forum Champion
Brett, if you have an instance of this I would like you to confirm and post the Firebase warning you get.