Page 1 of 2
Posted: Sun Jun 01, 2008 3:49 am
by Eonix
I was booted accidentaly today, and I wasnt able to return to the team...
Posted: Sun Jun 01, 2008 8:45 am
by Dark_Sponge
That's not a bad idea Eonix....
Posted: Sun Jun 01, 2008 9:02 am
by Eonix
Was wondering if this happened to anyone else.
Posted: Mon Jun 02, 2008 4:36 am
by Eonix
...
Do the rest of you acknowledge?
Posted: Mon Jun 02, 2008 4:27 pm
by Dogbones
This has come up in the past. As I recall the general feeling was it would be too much of an annoyance >99% of the time to deal with an issue that happens <1%
Perhaps a better solution would be an #unboot command so that if a com really did boot someone by accident they could 'clear' their boot flag and they could get back in if they wanted to.
But a solution for this already exists. Just log back in with one of your 2 other nicks.
Posted: Thu Jun 05, 2008 9:08 pm
by lexaal
or #boot name reason(optional)
It would really help if people who got booted get the reason why they got booted.
Posted: Thu Jun 05, 2008 9:25 pm
by Andon
I like having an optional reason for a #boot command, as it allows for quick boots but also boots with reasons
Posted: Thu Jun 05, 2008 10:56 pm
by Dogbones
Agreed, an #boot name <reason> would be very handy, although it would not address Eonix' original point, namely an accidental boot. That pretty much means the com likely hit the boot button instead of accept when he was trying to join. No one 'accidentally' types in "#boot Eonix"
Edit: I still stand by my earlier post about this being a non-issue
Posted: Sat Jun 07, 2008 1:45 am
by aarmstrong
I fully support this change.
I very seldom boot anyone and 50% of the time it's a mistake. At the very least, make a toggleable option to enable the boot confirmation screen (even if it's defaulted off).
Posted: Sat Jun 14, 2008 9:25 am
by DrBeginner
Even then. You can still accidently boot a person by clicking yes anyway. No point in it.