What happens if you go AFK in Kanto Tactics PvP?

Einoow’s version 32 notes give the sequence: a warning after 120 seconds, another at 150 seconds and a permanent departure at 180 seconds away or without interaction. Before that departure, no bot takes your place or changes your board, according to those notes.

The Guide says normal presence means keeping the tab visible and interacting from time to time. Watching an automatically resolving fight and abandoning the tab are therefore different situations. Pay attention to a warning when it appears rather than assuming the board will keep your place indefinitely.

The ordinary absence times come from the version 32 notes dated October 17. Version 34 adds the separate mass-outage protection below. If a later in-game message changes the rule, use that current message and check the developer’s changelog.

Version 34.1 separates a failed entry from abandoning an active match. Leaving a table you never managed to join does not count as quitting. If you still have not joined after 60 seconds, the game releases your seat without taking LP.

This is an entry timeout, not permission to go AFK for a minute after joining. First identify whether you reached the match or remained on its loading screen. If you were already playing and then disconnected, use the reconnection and outage rules below.

The same patch fixes a “Back to the table” screen that could load forever. For maintenance messages and room codes, see PvP entry help. These are published fixes, not a guarantee that every browser or network failure has been resolved.

Version 34 describes a server outage that drops many connections at once. That event does not count as leaving: affected players get 10 extra minutes to come back. If they do not return, they keep the points for their placement.

This is a server-outage exception, not a new ten-minute AFK allowance. Losing your own connection, hiding the tab or leaving the phone unattended does not by itself establish that the exception applies. Read the notice shown for your match instead of assuming every disconnect is protected.

The ordinary rule below still explains a completed departure. The outage rule explains why a protected interruption can allow extra return time and preserve points. If the lobby instead shows an update countdown, use PvP maintenance help. A patch announcement alone does not show that an outage is happening now.

Version 34.1 improves returning to your table after a connection drop and lets friend rooms carry on without surrendering. A recoverable disconnect is different from a completed departure.

For an ordinary absence, return before the departure threshold if you can. Once the game counts you as having left, the Guide says a Trainer completes the game in your place and you cannot rejoin that table. Reloading should not be treated as a way to undo a completed departure.

For example, seeing a warning is still different from being told you have left. Read the current state before deciding whether you are returning to an active match or waiting to start another. These are examples of how to interpret the documented states, not measured reconnection tests.

An ordinary departure earns no LP under the version 32 rule. The version 34 protected outage is different: it preserves placement points. A bot eventually finishing the match does not turn an abandoned game into a way to gain ranking points.

The Guide describes a first queue wait after leaving, with an exception when no other human players remain. It also says friend rooms have no queue wait. Follow the duration shown by the live lobby rather than assuming every departure has the same restriction.

The friend-room exception concerns the wait; the mass-outage protection above is a separate rule. It is not a statement that you can leave and later rejoin the same table after permanent departure. Keep those two consequences separate.

Friend rooms are unranked, and the host can fill open places with Trainers. If you want a casual group session, the friend-room setup explains that route. Do not use an abandoned ranked queue as a substitute.

Finish the match before taking a long break. Keep the game tab visible and remain available to interact during planning. On a phone, moving to another app may leave the game out of view; do not assume the autobattler keeps that session active for you.

If the lobby shows a server-update countdown instead of an absence restriction, follow PvP maintenance help. A server update and a leaving penalty are separate conditions.

For a persistent unexpected departure, record the approximate time, device, browser and visible warnings for the developer. Avoid publishing private account details. The goal is to identify what the client showed, not to promise that every interrupted match can be restored.