GKSPHONE V2
Migration
Move an existing LB-Phone database into GKSPHONE V2 with the migratephone console command.
Move your players' existing phone data into GKSPHONE V2. Currently supported from LB-Phone only — other phone systems are planned.
Run this once, on a fresh GKSPHONE database, before your server goes live with the new phone. It only adds rows; it never clears them.
What transfers
| Phone | Numbers, settings, eSIM, contacts, call history |
| Content | Photos, notes, advertisement posts |
| Messages | Conversations, group chats, members |
| Squawk (Twitter) | Accounts, posts, retweets, likes, followers |
| SnapGram (Instagram) | Accounts, posts, comments, likes, follows, DMs |
| DarkChat | Accounts, rooms, members, messages |
Before you run it
Two conditions are checked, and the command refuses to start unless both hold — so there is no way to run it by accident:
- No players online. It counts connected players and stops if there are any.
- A clean GKSPHONE database. It stops if
gksphone_settingsalready has rows, assuming the migration has run before.
Your LB-Phone tables are only read, never modified, so keep them until you have checked the result.
Running it
From the server console — not in game, and not from an admin menu:
migratephoneLeave the server alone until it finishes. It prints a per-category summary when it is done:
=== GKSPHONE DATA TRANSFER COMPLETED ===
=== TRANSFER SUMMARY ===
=== TOTAL TIME: 34 SECONDS ===
=== PHONE RECORDS: 812 RECORDS ===
=== DARKCHAT CHANNELS: 17 RECORDS ===
=== INSTAGRAM POSTS: 1204 RECORDS ===
...If it stops immediately
| Console message | Why |
|---|---|
... PLAYERS ONLINE ON SERVER! | Someone is connected. Restart the server and run it before anyone joins. |
DATA EXISTS IN GKSPHONE_SETTINGS TABLE! | The phone has already been used. Drop the gksphone_* tables and let Installation recreate them if you need to run it again. |
LB Phone Transfer is already running. | It is still working. Wait for the summary. |