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
This post has been closed. You can still view previous posts, but you can't post any new replies.

Kicked Players Are Being Banned?

October 06 (3 years ago)
A.J. Falcon
Pro
Marketplace Creator

I recently kicked a few players from a game hub, because it was a copy of the Original Game, which had so much content it was slowing Roll20 Down. I tried adding them back and each one of them is receiving "Not Authorized". Yet I check their profile page and they are not banned by me, but they can't even see my active listing of the game. Any solutions?


I tried steps 1-3 (and cleared cache).
I tried Email Invitations.



 

October 06 (3 years ago)
vÍnce
Pro
Sheet Author

When you kick someone a new join link is generated.  You'll need to share the new join link with them.

October 06 (3 years ago)
A.J. Falcon
Pro
Marketplace Creator

That might be the problem, its not generating a new invite link? I tried the one ingame (that is hidden). It didn't work. So I also tried the Email Invitation Option. That didn't work either.

October 06 (3 years ago)
keithcurtis
Forum Champion
Marketplace Creator
API Scripter

That's odd. I can assure you that there is no banning going on of any kind, though. Something might be going awry, but the word "banning" can be a sensitive word.

Make sure that they are getting the new invite link from the new game. If that is not working, try sending them a link from a brand new game, just to verify that there is no overall problem. If you want to verify that kicking someone from a game does not disallow them from using a newly generated link, you can create a Dummy Account, invite it (and log in under it), kick it, and then invite it with the new link. It should work fine.

If all this still goes awry, please fill out a Help Center Request, because something is not working properly. Also, please, if you could, report back to this thread regardless. If there is still a problem, I'll do what I can to direct attention to it. If you manage to resolve it, it would be helpful for others to understand what the issue was.

October 06 (3 years ago)

Experiencing this issue right now. Cleaned out my AL one-shots room. Sent new invite link to this week's players and some get not authorized message. I created new links and players still cannot join. One created a dummy account and could join with the latest link.

To test, one player created a game, invited his dummy account, and after joining kicked the dummy. Sent new invite link and dummy could not rejoin the room.

October 06 (3 years ago)
keithcurtis
Forum Champion
Marketplace Creator
API Scripter

Yeah, I can confirm this. I'll see if I can send up any flares for the dev team.

33 people are waiting for this bug to be fixed so they can play in our community. T_T!

October 06 (3 years ago)
A.J. Falcon
Pro
Marketplace Creator

Wow Iniciativa same. I do One-Shots weekly and rotate players. Around 30+ folks cant get in. Hopefully its resolved soon. 

:(
October 06 (3 years ago)
Eve
Roll20 Team


Iniciativa+4 said:

33 people are waiting for this bug to be fixed so they can play in our community. T_T!


A.J. Falcon said:

Wow Iniciativa same. I do One-Shots weekly and rotate players. Around 30+ folks cant get in. Hopefully its resolved soon. 


Go ahead and give it another try please. We found the problem and this should be fixed!



October 06 (3 years ago)

Edited October 06 (3 years ago)

Yes!
Finally, the players were already nervous :D

Everything works fine now. ¡Thank you!


October 06 (3 years ago)
keithcurtis
Forum Champion
Marketplace Creator
API Scripter

Working for me, too. Thanks, Eve!

October 06 (3 years ago)
Eve
Roll20 Team

Glad to know it's fixed, I'm going to be closing this thread. Thank you again for reporting this!