Hi, when running through the discobot new user tutorial, there is a prompt to flag a very mean message. However, if the kind of flag chosen is not “inappropriate” but one of the other options, the tutorial hangs. I don’t see a way to add another flag to the post once it has been flagged for another reason besides “inappropriate.” Is there a way for discobot to say, “You flagged my post, but not for being inappropriate. Let’s try again!”
That isn’t a bug; the instructions indicate which flag type to use. So at best this would be an enhancement.
(also @tgxworld I’d expect any flag type to work, really… except contact staff which is a different thing.)
3 Me gusta
I agree with this 100%. If I had an instance where I wanted some of the flag options (including the inappropriate one) hidden via CSS, discobot would essentially be broken aside from overriding the step completely and telling the user to skip. Edge case of course, but it would be nice to allow all types of flags for that step 
Yea, especially because it is designed to help a new user feel comfortable flagging a post. Setting them up for success = winning.
I’m comfortable calling this a feature rather than a bug - I see the point.
1 me gusta
This is strange because I made the bot respond to all none custom flag types when the tutorial was added.
Are there any specific steps you took when you got stucked? Currently I’m unable to reproduce this locally or on your site.
2 Me gusta
I tried here on Meta with the “Something Else” flag and it does break the flagging step. Based on flag_types_without_custom.values, I’m assuming selecting the “Something Else” option doesn’t work since there is a custom value involved.
I really like that flag given its versatility. While I can’t think of a true downside to having all of the flag options visible, I have considered hiding all but “Something Else” and modifying the text to further convey a general usage. Just a simpler UI presentation to users.
If allowing the “Something Else” flag to continue the step is not an option (it would be nice if it was 
), I guess another idea would be to hide it or disable it specifically for the discobot tutorial.
2 Me gusta
So @outofthebox I dispute the premise of this topic; almost any flag type will work except “something else” which is a PM to staff and requires typing in a custom reason.
Also in the discobot narrative, the user is explicitly told to use the “offensive” flag type, on top of that.
The problem isn’t that something-else doesn’t work (it’d be fine if Discobot replied back with “Oh no! You didn’t use the right flag type!” the same way it does when you reply without flagging the post). The problem is that, when the user takes this ill-advised action, the tutorial becomes deadlocked instead of giving them a chance to try again.
By the way, I’m actually able to un-deadlock the tutorial by posting a reply and then flagging Discobot’s “oh no, my nasty post hasn’t been flagged yet” response 
4 Me gusta
Shouldn’t be the case – the bot will post a “hey, haven’t seen you in a while, want to continue?” message eventually.
1 me gusta
Yeah, but that’s still a soft lock and requires a “skip” command to keep going.
1 me gusta
The bot is designed for a new user who feels uncomfortable with forum software so they try discobot to learn the ropes, right? I think if there are ways the new user can make discobot fail, that is an area worth improving, if the resources required to do it aren’t unreasonably high.
11 Me gusta
Acabo de probar esto en https://try.discourse.org. Si se selecciona la opción “Algo más”, el tutorial no se reanuda; no se le dan instrucciones al usuario. El tutorial se puede reanudar publicando @discobot resume tutorial.
La respuesta que se recibe al reanudar el tutorial no es muy clara:
¡Oh no, mi mensaje desagradable aún no ha sido marcado. ¿Puedes marcarlo como inapropiado usando el botón marcar (icono)?
Esta respuesta debería informar al usuario de que debe marcar el último mensaje de discobot. No es posible marcar el mensaje “desagradable” al que se refiere discobot.
Edición: es posible que no esperara lo suficiente para que el tutorial se reanudara tras el paso fallido de marcado. Esperé unos minutos, pero en try parece que se necesitan 10 minutos para que se genere el mensaje de discobot “solo revisando porque no he tenido noticias de ti hace un tiempo”.
7 Me gusta
Solo para opinar aquí: acabo de tener un usuario que se confundió por esto. Seguro, no siguió las instrucciones exactamente bien, pero el tutorial podría ser más indulgente y reanudar rápidamente.
6 Me gusta
Estamos teniendo el mismo problema. Algunos de nuestros miembros marcaron el mensaje de Discobot como “Otra cosa” porque pensaron que era lo correcto, y se quedaron atrapados en el tutorial. 
No parece haber una forma obvia para que un principiante vuelva y marque el mensaje nuevamente una vez que se ha realizado la marca “incorrecta”, lo cual los confunde y frustra.
¿Quizás las marcas de “Otra cosa” podrían contarse como parte del tutorial para evitar este bloqueo?
6 Me gusta
4 publicaciones se dividieron en un nuevo tema: El tutorial de Discobot se queda atascado si se selecciona el tipo de bandera ‘algo más’
Discobot ya no debería bloquearse aquí cuando se selecciona “otra cosa”.
6 Me gusta