Rehosting lobbies command

[qwertyperky]

Is your feature request related to a problem? Please describe. People rehosting lobbies where users join it when they have already done the prior lobby, but due to the volume of rehosts this may not be apparent until they are invited, by then the raid is messed up as it will contain one less person

Describe the solution you'd like Command: $rehost (Optional args) Channel: Raid channel only Permissions: Raid host only (maybe raid mods?) Behaviour:

• Kicks all users except the host from the lobby
• Re-advertises the raid in the channel it was reported from, and the #active-raids channel if applicable, with a specific marker to show it's a rehosted lobby
• Remembers who has been in the lobby prior, so those members can't rejoin it.

Describe alternatives you've considered Putting "rehost #2" or "lobby 4" in the status/gym name, but these are seldom ignored by people spamming the ticket when tthey get a ping.

Additional context If this is to be implemented it would be good to do this once we can add parameters to the $raid command, such as specifying min/max joiners, denote weather boost etc. as these could also apply to the $rehost command. e.g. $rehost WB if it is now weather boosted.

Got this idea from another server (40k members with a custom bot only for that server which has the rehost command - it works very well). I don't know how feasible it would be for Pokenav to remember who has been in the prior lobbies where $rehost is used across all servers Pokenav is in

[TheGerontocracy]

People joining reposted raids they have already completed is a serious issue, that this would solve. An additional benefit is that it would save the host the work of setting up the raid again.

As a player who has done a fair share of rehosting the last few days I would not use the feature as implemented. It would actually slow me down. The reason is that I do not want to close the original channel before I can be sure that the raid-party has successfully completed the raid. With a new channel I can start setting up the new raid party while the old party is still waiting in the lobby.

Instead of the implementation suggested, I would like $rehost to set up a new raid restricted to new members possibly marked as a rehost. The bot can reply with a link to the new-channel so that the host can easily navigate there.

This allows members of the original party to ping the host in the original channel if they have problems. It's hard to reassemble that party once it does'n have a channel or role attached to it.

[FlipsCat]

I’m not sure how to upvote open suggestions, but just the suggested $rehost command that clears the channel would be a welcome start. Near the end of the raid timers especially I usually have to $kick 5-10 users manually after prompting via ping to type $bye several times. Being able to just tell the ones left to rejoin and clear the lobby would save a load of time.

[FlipsCat]

People joining reposted raids they have already completed is a serious issue, that this would solve. An additional benefit is that it would save the host the work of setting up the raid again.

As a player who has done a fair share of rehosting the last few days I would not use the feature as implemented. It would actually slow me down. The reason is that I do not want to close the original channel before I can be sure that the raid-party has successfully completed the raid. With a new channel I can start setting up the new raid party while the old party is still waiting in the lobby.

Instead of the implementation suggested, I would like $rehost to set up a new raid restricted to new members possibly marked as a rehost. The bot can reply with a link to the new-channel so that the host can easily navigate there.

This allows members of the original party to ping the host in the original channel if they have problems. It's hard to reassemble that party once it does'n have a channel or role attached to it.

I personally (because i'm usually out hosting via two phones - one for discord coordination and one for the actual game) would prefer still one channel that can clear the lobby and disable ppl who joined already from rejoining. That's just because swapping channel to channel would confuse me (as i'm sending invites, waiting for the timer so I can backout resend in pogo, I also read chat and answer things as they come up for the next lobby). Would be harder doing that easily if I'm having to swap to 5+ different channels hah.

Also would like to note that just a toggle to disable users for any raid from rejoining the channel I would love. Users that have left either completed the raid or got kicked by a moderator. I don't want anyone rejoining 98% of the time.

[aya-hammasters]

I’m not sure how to upvote open suggestions, but just the suggested $rehost command that clears the channel would be a welcome start. Near the end of the raid timers especially I usually have to $kick 5-10 users manually after prompting via ping to type $bye several times. Being able to just tell the ones left to rejoin and clear the lobby would save a load of time.

@FlipsAndGrips , when you $kick users, their raid count is not updated in their profile right?

[aya-hammasters]

The way I have been managing this is putting all previous raiders IGNs, in su: these can't join again: user1,user2,user3,.... , and hope those users pay attention. I can easily do this when I have Discord on desktop/laptop, nearly impossible to do when I'm out driving around with just one phone with no switch screens, lol.

[aya-hammasters]

For this behavior:

Behaviour:

Kicks all users except the host from the lobby

I would like it to be that the users raid counts are also updated in their trainer profile ($my-stats)

[FlipsCat]

I’m not sure how to upvote open suggestions, but just the suggested $rehost command that clears the channel would be a welcome start. Near the end of the raid timers especially I usually have to $kick 5-10 users manually after prompting via ping to type $bye several times. Being able to just tell the ones left to rejoin and clear the lobby would save a load of time.

@FlipsAndGrips , when you $kick users, their raid count is not updated in their profile right?

I'm pretty certain if you join a raid channel and the host + 2 are in it it counts? Regardless I don't care if not as I only $kick after repeated $p reminders to type $bye

If they don't respect my time enough to follow that simple protocol their "stat" is the least of my worries lol.

[FlipsCat]

For this behavior:

Behaviour:

Kicks all users except the host from the lobby

I would like it to be that the users raid counts are also updated in their trainer profile ($my-stats)

As i said, channel with a host + 2 counts no matter what. the "stats" though from an admin and mod perspective are the last on the to-do list. I would rather help my hosts raid easier and more efficiently with less effort than have a few more numbers on a board as I'm sure they would too.

[soulus98]

Regardless I don't care if not as I only $kick after repeated $p reminders to type $bye

If you mean people who have already done the raid, why not just kick them immediately?

+1 for this command I personally would prefer it to make a new channel so that it is properly advertised at the bottom of the raid lobby. Although, I would love it as soon as reasonable in whichever form is chosen. If kicking/blocking everyone who is currently in would be significantly faster to develop, then that is preferred.

[FlipsCat]

Regardless I don't care if not as I only $kick after repeated $p reminders to type $bye

If you mean people who have already done the raid, why not just kick them immediately?

+1 for this command I personally would prefer it to make a new channel so that it is properly advertised at the bottom of the raid lobby. Although, I would love it as soon as reasonable in whichever form is chosen. If kicking/blocking everyone who is currently in would be significantly faster to develop, then that is preferred.

Because sometimes they glitch with the raid pass bug, just aren't paying attention, ect.

EDIT: after joining and hosting on two new servers specifically I figured out how to ferry via a new channel each wave. "$r landorus lobby1 mm:11 "su: Lobby 1 of 3 Flips Landorus" $r landorus lobby2 mm:11 "su: Lobby 2 of 3 Flips Landorus" $r landorus lobby3 mm:10 "su: Lobby 3 of 3 Flips Landorus"

(third wave failed my first try tho bc so many repeats from 1 and two joined all three. I now know how to manage this lol)

[aya-hammasters]

EDIT: after joining and hosting on two new servers specifically I figured out how to ferry via a new channel each wave. "$r landorus lobby1 mm:11 "su: Lobby 1 of 3 Flips Landorus" $r landorus lobby2 mm:11 "su: Lobby 2 of 3 Flips Landorus" $r landorus lobby3 mm:10 "su: Lobby 3 of 3 Flips Landorus"

When I have Discord on desktop when hosting, the way I have been managing this is by putting previous raiders in su

$r landorus Gym1 40 "mm: 10" "su: lobby1"
$r landorus Gym1 30 "mm: 10" "su: lobby2. These can't join again: raider1,raider2,raider3,....,raider9"
$r landorus Gym1 20 "mm: 10" "su: lobby3. These can't join again: raider1,raider2,raider3,....,raider18"

Which is why this is painful. Regardless, ppl from lobby 1 and 2 sometimes still joined 🤦‍♀️

In another Discord server that uses custom bot (not PokeNav), all I do is just type -rehost in the raid channel, a new raid announcement is posted, ppl sign up but the bot takes care of preventing previous raiders to join.