> 2533274795123910;4651:
> > 2533274795039299;4649:
> > Was just banned for the first time for idling in BTB thanks to their poor user design. After a game ends, if you navigate to a different app, like Netflix, make sure you manually push B and back out, otherwise they’ll ban you. It’s very poor user design, and I guess the BanHammer is a way for them to try to “justify” it by blindly grouping you with all other banned players (justification by simplification, common logical fallacy). I also can’t see the duration of my ban because I missclicked when the banhammer modal was show. All I could see was “banhammer” before the model was dismissed. Another case of poor user design. So that’s Negative 2 on the user design and negative 1 on the logic. Somebody needs to look in the mirror and accept their poor design, and it’s not bungie.
> >
> > I would not be surprised if this developer starts banning people when their batteries die.
>
> Should a mechanic be implemented where an action happens each time a player moves to another app, for every situation that can happen in the game?
>
> Sure, it sucks that Halo 5 does not register when you jump from Halo 5 to another app when you’ve finished a match and didn’t put in the proper inputs to leave the search que. It’s however also convenient if I want to quickly check something without leaving the search que.
>
> Do you mean the Banhammer screen? Not model?
> If it’s your first ban it shouldn’t be long.
>
> You know, your Xbox informs you when the batteries of the controller is low on energy. It’s also your responsability to see to them being charged. So yes, they will ban you for dead batteries if you can’t get your controller going after the Idle-time limit.
No one said moving to another app has to be handled in every situation. If anyone is suggesting that from my text, then they are taking part in a textbook strawman fallacy. It only needs to be handled in a very specific case. Player is in the lobby, searching for a match, maybe even by themselves; it’s literally one if statement in the callback for when the app backgrounds to exit from the match making search.
I meant to type banhammer “modal”, as in the term modal: a layer of UI that is displayed over the base UI that can be dismissed: essentially the first message that appears right when you’ve been banned. I miss clicked when it appeared and only could see it briefly. The ban was short, but it was not an ideal use case to have to look/post on a forum to attempt to find the duration left due to a simple miss click. Especially since it was my first halo 5 ban ever, it left me initially confused.
Good information to know about the batteries, from the other design, it’s not surprising. But since it’s not an environmental friendly policy, I’ll run my batteries dry and be sure to keep extras near and ready.
As for closing the app the instead of backing out through B. I’m not sure, that may work too, but maybe not either. Better back out with B to be on the safe side.
I still stand by my initial analysis, poor design. Fallacious justifications aside, it requires manually action when none should be required. Banning for that is why I consider it poor.