respawn next while having a current claim
When you have a current claim and try to get next on a respawn that is empty, it will automatically kick you from your current claim and claim the spawn you wanted next on.
User dabs was hunting 816, tried to get next on 1712 but since it was empty, it kicked him from 816 and accepted 1712.
12 Replies
Yes, we built next to work exactly as claim. If the resp is free, claiming next is the same as start hunting now
Is there at least a confirmation?
"1712 is free, if you accept you will lose 816, are you sure"
If so, I think it's fine
If not, then it can cause problems
Nope
We assumed if you are claiming next to a respawn that is empty the intention is to hunt there
For us it makes no sense to be claiming next in empty respawns
yeah that's true, but a lot of people don't even check if it's free or not
their process is
1. claim a free spawn
2. spam next on a bunch of others to get a spot to hunt afterwards
they now have to check each one I guess
kind of system abuse imho 😅
yeah lol
well nobody has complained about this on my server yet
in my opinion, I think ideally a confirmation would be good, but it's not urgent
We’re getting a lot of complaints and I agree that a confirmation would be good. But we can also just tell people to be more aware.
i'll consider a confirmation for the cases where they are already hunting
and continue to skip confirmation if they are not hunting anywhere
this is also a matter of performance, the more interactions users have, the more opening for communication issues we create, like confirmations timing out, etc
hmm, true
didn't consider this perspective
actually I just realized that this can't be done when you are hunting and claiming a non-empty respawn
https://discord.com/channels/441991938200305674/1256380706775498825
this is what happens in this case
so I think both of these topics can be closed as they complement each other
- if you are not hunting and claim a respawn, you start hunting with no confirmation if it is empty, or added to the queue with no confirmation if it is used
- if you are hunting and claim a busy respawn, you get added to the queue
- if you are hunting and claim an empty respawn, you get this error, to notify that you are already in an ongoing hunt
yep, looks good to me
☝️ @emxp if it's fine with you
Closing both, if anything is missing or the details above do not match expectations, feel free to reopen