6 Replies
you can't queue for a respawn B that is empty when you are already hunting at A
as there is no queue for the respawn B
I got this same error when I pressed enter after only typing the code
Waiting for the drop down and clicking the resp, so that it has the full name, the it worked
But if you quickly type the code only, then send the command, it crashes
I also didn’t get the yes/no option to claim/next/leave a spawn. Not sure if that is intended or not
this is intended, because we tried to avoid "useless" confirmations to reduce amount of needed interactions to be handled
if someone sends a "harmless" command we take it that they really want to do it
except for management/admin commands, like kicking, deleting, etc, then we confirm as good practice
and for "impactful" commands, such as "resp leave"
but claim and next are "free" if you make a mistake so no need to confirm
your messages fit so well into the other thread that I am not sure if you also meant it for here or really for the other one https://discord.com/channels/441991938200305674/1256376594403037285
let me know if it applies to this one, as the nabbot error message does not seem to make sense with what you described
I meant it for here, but I can't replicate it on my phone, and I'm not at my pc all day
Closing both (https://discord.com/channels/441991938200305674/1258074286539935764), if anything is missing or the details above do not match expectations, feel free to reopen