When someone gets kicked out of the game, they cannot seem to log back in and continue playing the game as if they didn’t leave, rather they would have to join as a new player, meaning they couldn’t have their points carry forward from where they left off because they are a ‘new player’ now. Is there any way for the host to add them to the game as the player they were when they got kicked out? This is problematic for Survivor Rounds as well because if they get kicked out, they are out of the game.
1 Like
If you have players when logging in have user name and email as required, then the person can log back in with that email address and keep the same points.
To setup this go tab LEADS - Lead Capture Settings - Capture Lead Capture Settings - turn on Email settings and make email required
2 Likes
phone number works, too. But either email or phone need to be required.
Then, make sure you turn off the allow multiple sign in option under the lead settings. If you don’t, when someone comes back in with the same email or phone, they will create a new team. Turn this off and they will be logged back into the previous team.
2 Likes
Thank you @dandeibert for the great response and for helping. I can add a bit more detail:
Allow Participants To Sign Back In indeed requires a phone number or email. This will then use that unique phone number or email to reload the player/team’s account when they sign in again.
Allow Multiple Sign-Ins will give the option to returning player/teams (i.e. reloading or reconnecting to an experience) with a screen that prompts if the player/team wants to Continue Answering or Create New Player.
This screen only displays if the browser detects and existing player/team session in the browser. It will then only create a new player/team if the returning player/team clicks Create New Player. If the player/team clicks Continue Answering then Crowdpurr will restore the player/team session from their browser (that was detected).
So the setting Allow Multiple Sign-Ins thus allows a browser to create multiple player accounts. This is really only meant to be used during testing by the host, as it easily allows multiple player accounts to be created. Otherwise, you’d have to open a Private/Incognito browser window for every player you want to test. Else, it would keep restoring the same player. The browser will be “stuck” on the same player unless you click “Sign Out” or use a Private/Incognito browser window and then close it and open a new one.
If you disable Allow Multiple Sign-Ins, it does not present the above screen and if a player/team session is detected in the browser, it will be restored automatically (the same as clicking Continue Answering above).
So, in closing, you really shouldn’t have to have Allow Participants To Sign Back In enabled, if players/teams all play on the same device. Reloading, refreshing, checking text messages, etc. etc. and then returning will just restore the session that was in the browser. You only need Allow Participants To Sign Back In in the event a player/team switches devices, browsers, etc. It’s hard to know if this will happen ahead of time so it doesn’t hurt to enable it. But it only works if you make it required to collect either an email or phone number.
1 Like
Also, in Crowdpurr, players should never be getting “kicked” out of a game. I’d be curious to hear more about what you’re experiencing.
I’m sorry, I’m not 100% following here. I have participants playing individually on their own devices. Sometimes they are getting kicked out…I don’t know how or why it happens and I can’t really tell you more about it other than they get kicked out.
I’m not following what “Allow Multiple Sign-Ins” an “Allow Participants To Sign Back In” do or don’t do. I’ve always left them both on, but I’ve never required anyone to have to sign in with an email or number. I feel like that would deter people from wanting to play.
Regardless…if what you’re telling me is that the only way to get people to be able to sign back in and pick up from where they were kicked out is to have them enter a # or email, I will try that.
If there is something else that I am missing, please let me know.
I strongly suggest:
Allow Multiple Sign-Ins = Off
Allow Participants To Sign Back In = On
Email = Required
AND clearly inform participants to use an email address that they will remember throughout the night, as this is how they will reconnect to their points!
(Players will, inevitably, use fake addresses and forget them, assuming they will not lose connection. Same, I believe, if requiring phone field, instead.)
It does occur something like 1% of the time. Very difficult to determine causation but I chalk it up to user error. Tends to be less “tech savvy” players who don’t even know which browser they were using, navigating away, getting lost, accidently closing tabs or browsers. (Even when the player believes that not to be true.) It’s actually commendable how well your team has provided functionality to counter the inevitability of it. 
1 Like
This is not what I’m saying. It’s much easier and automatic than this.
When a participant joins a Crowdpurr experience, their browser saves their account in the browser’s session. So even if the participant navigates to a different app, closes the browser, goes to the bathroom, etc. etc. when the participant returns to the same browser, their account will be restored. The only time this doesn’t work is the following scenarios:
- Participant switches to a different browser (e.g. Safari then Chrome)
- Participant uses an Incognito/Private browser window and closes it
- Participant switches devices (e.g. battery dies on phone)
All of these prevent the participant from accessing the same session saved in the browser. This is why we have the Allow Participants To Sign Back In feature.
In the event one of the above happens, if you have Allow Participants To Sign Back In enabled with Email or Phone Number enabled as a required lead capture field, then the participant can use any other device and when they sign in with the email or phone number they used before, it will recall their participant account if they have previously joined that experience or the experience is in a Next Round chain of experiences.