Imported from legacy Flarum.
Original author: Ewic (Flarum #1695)
Title: Bloom events disable @go command
Description:
It might be a good idea to disable the @go command during Bloom events. This has already happened to me almost twice 
. I know this is mostly a user error, but unlike when the game crashes, you can still rejoin the event but when @go accidentally.
In my case, most of my @go commands are saved in my shortcut list, which makes it easy to accidentally use them during the event.
Why is this a good idea?
Disabling the @go command during the event would help prevent players from accidentally teleporting outside the event area. This would allow them to continue participating instead of losing their chance to rejoin
What risks or downsides does it have?
At the moment, I do not see any major risks or downsides to implementing this change.
Additional Info:
Since Bloom events can last 5+ hours, missing the opportunity to participate because of an accidental teleport can be very disappointing. Based on my experience, I try to join this event whenever possible because of the rewards. However, accidentally leaving the event area can be quite frustrating.