Not if the script was only calling windows functions, and I would be dubious of those claim aka their either lying about why they were banned or lying about what that .bat called.

I’d love a ban for mine.
It literally calls PE, runs the shortcut to my direct log in and then calls PE again and I’ve caught many a ban because I like to test shit out. Never once for my .bat file. I’d love to read that “You were banned for using legitamate windows 10 tools”

Every step is a literal windows function or a battlenet one.


Edit: just realized I do in fact know someone who claimed they got banned for PE, one of the “loaders” a few seasons back described itself as only using that, when in fact it automated game joining which would 100% violate tos, but again whatever mechanism was used for auto join would have caught the ban, not PE

This post was edited by chickypoo on Apr 19 2026 10:48pm

it's cheating

Someone got banned for using an auto-joiner? As in, something like an autohotkey script which joins your main character's next game when you press a hotkey?

TLDR: As long as you interact with each instance in a non-automated way, you're fine.
The way used to load additional instances is irrelevant, and not subject to any explicit rule.
At the end, the multi-instances blocker has to be killed, and technically speaking, even Process Explorer is automation anyway.

This post was edited by xhul on Apr 20 2026 06:12am