Connection ErrorBad RequestThis page went staleSession ExpiredSign in requiredForbiddenNot FoundToo Many RequestsServer ErrorBad GatewayService UnavailableGateway TimeoutHTTP Version Not Supported
Session Expired
Your session has expired. Please log in to continue.
Sign in required
You need an account to do that. Sign in or create one — it only takes a minute.
This page went stale
Your security token was rejected, usually because the page sat open too long or you signed in elsewhere. Nothing was saved. Reload the page and try again.
Request Failed
We encountered an issue while processing your request.
Please check your internet connection and try again.
Yes, such rules should ideally be implemented programmatically. But until that happy moment arrives, let's have an informal ban. Just like with campaign heroes.
This isn't an experiment; it's a clearly necessary rule for mirror matches, which I simply forgot to include when writing the tournament regulations.
Regarding "accidentally buying a leveled hero and putting him in the lineup" – well, he bought it, and I won't penalize him for that. The main thing is not to take advantage of the benefits that leveling provides (i.e., not fighting neutrals, not fighting the opponent, not using transport spells, etc.), and to dismiss him as soon as the immediate need for him disappears. In other words, assess the situation and use common sense.
If the "5+ level" option seems too complicated, it can be adjusted. For example, in the event of both heroes dying, they could agree not to resurrect specifically those heroes. That is, this rule could be activated not by default at the start of the game, but after a key event.
I repeat – the goal is to avoid the game of "who can resurrect a leveled hero first," because I see this as an abuse of the game's mechanics. On regular templates, this isn't so critical, but on mirror matches, it spoils the idea behind the template.