Kingshot Dual Login Guide: How to Run Main and Alt Accounts

To run your main account and alt farm account simultaneously in Kingshot, you must bind each account to separate platform credentials—such as distinct Google, Apple, or email logins—and open them on separate clients. Operating through a mobile phone and a PC client, or running two isolated desktop instances side by side, bypasses session kickouts and lets you manage live resource feeding, rally fills, and garrison defense in real time.

Account Binding and Profile Isolation

Kingshot allows multiple characters to exist under a single profile, but the game engine restricts each bound login to one active session at a time. If you launch a secondary character tied to your primary Google Play, Apple ID, or social login, the game immediately disconnects the first session with an authorization override error.

To set up simultaneous access, isolate your accounts before developing the alt base:

1. Open your primary base, tap your profile avatar, navigate to Account, and confirm your main game is permanently linked to your primary platform ID.
2. Launch Kingshot on a secondary device or fresh emulator client and select the option to start a new game rather than syncing existing data.
3. Complete the tutorial and bind the new base to an entirely separate email or platform credential.

Device and Client Configurations

The most reliable setup pairs your primary mobile device with a PC client or desktop Android emulator. Running your farm account on a PC preserves your phone's battery life and device memory while keeping your alt account active for gathering marches and production timers.

• Resource Allocation: Assign two virtual CPU cores and 2 to 3 GB of RAM to the secondary instance in your emulator settings. This provides enough headroom for gathering, construction, and rally deployment without burdening your computer.
• Dual Desktop Instances: If you run both accounts on a single PC, launch two separate emulator instances rather than cloning an active session. Assign each instance a distinct device profile ID in your emulator settings to prevent network handshake conflicts.
• Client Throttling: Drop the secondary client's graphics to low and cap the frame rate at 30 FPS. Because alt accounts primarily sit idle on gathering nodes or base menus, higher graphical settings consume hardware resources unnecessarily.

Real-Time Coordination and Safe Resource Transfers

Simultaneous logins eliminate the delay of logging out and reloading during time-sensitive battles. In contested territory or cross-server events, you can use your alt screen to feed reinforcements directly into your main base, scout enemy watchtowers, or deploy distraction marches to peripheral resource tiles without interrupting your main army commands.

When moving surplus food, wood, and iron from your alt to your main account, compare your available transfer methods:

If you plunder your own alt city via controlled attacks, keep both screens visible to prevent accidental troop losses:

1. On your alt account screen, march all stationed defense troops out of the city to alliance banners, distant resource nodes, or an ally's shielded base.
2. Confirm the alt city defense screen shows zero defending units so you avoid triggering defense hospital overflow and troop deaths.
3. Launch your main account's attack march against the evacuated alt base to harvest the unprotected resources.
4. Watch the attack resolve on both displays, verify zero defender casualties, and immediately recall your alt's armies back to the base.

Account Safety Rules

Keep all actions between instances strictly manual. While running two accounts across separate devices or desktop clients is standard practice in mobile strategy games, using third-party synchronization tools or multi-instance clickers that mirror mouse inputs simultaneously across multiple windows violates account security terms and can lead to operational flags. Manage each window independently to keep both accounts secure.