Account, saves, and safety
Keep your identity and progress connected to the right wallet.
Wallet identity
Your signed wallet establishes the account used for cloud saves. Your username and appearance belong to that account. Connecting a different wallet can open a different account; it does not merge inventories or reward records.
The sign-in message identifies the site and expires. Never provide a recovery phrase or private key to Bloomstead, a support conversation, or an external form.
How saves behave
Wallet actions are confirmed by the server. Inventory changes, production queues, quest claims, and phase-related records must be accepted before the client treats them as saved. Repeating a request is not meant to grant its result twice.
Refreshing a saved game returns to the accessible saved island. A new browser or a new domain may require signing in again, but the same wallet still identifies its cloud account. The landing page itself does not require a loading screen or sign-in.
Your registered playing wallet
Game access requires a valid Early Access entry with X and a signed EVM wallet. Entries stay bound to their playing address. Rejected entries cannot enter. An NFT bought on the secondary market does not replace registration. Existing browser-only saves remain preserved separately and are not converted into cloud progress or rewards.
Connection problems
- Wait for a pending action to finish before repeating it.
- If the save status reports a problem, retry synchronization rather than repeatedly clicking the same purchase or claim.
- Check the connected wallet before starting a new character.
- Use the retry screen if the server cannot restore your last confirmed save.
For a gameplay issue, keep the relevant UTC time, island, action, and error message. Do not include wallet secrets or sign a transaction merely to report a bug.
Site analytics
The website uses Vercel Web Analytics for aggregate site traffic. The integration does not send custom wallet addresses, usernames, inventory contents, or token balances as analytics events. URL query strings are removed before the configured page-view event is sent.