A helping hand

Support, plainly.

Little Loam is in alpha and still in development. For installation trouble, bugs, account questions, or privacy requests, write to josh@bluescripts.net.

Join the Little Loam Discord for community discussion and gameplay feedback. Keep account details and privacy requests out of public channels; use email for those.

Our alpha progress policy

We do not plan to wipe alpha progress. Your farm, account and friendships will carry forward through normal updates and launch.

Alpha means the game is unfinished: features and balance can change, bugs can occur, and online services can be interrupted. The progress policy is about carrying your account forward, not removing ordinary gameplay consequences. A party defeat in the Deep can cost ore and gems; it does not reset your farm or account.

Accounts and password recovery

Password recovery is unavailable during alpha. There is no password-reset email flow. Keep your email-and-password sign-in details safe; support cannot promise to restore access to a forgotten password. Email-and-password registration does not verify your email address. A website mailing-list subscription is separate from your game account and cannot recover it.

If sign-in fails, tell us your handle, platform, game version, and the error you see. Never send your password, session token, or sign-in codes. Do not post account details in a public bug report. Signing out ends that session; it does not delete your account or saved progress.

Installing the Windows alpha safely

Use the downloads section for the published installer, version, system requirements, and SHA-256 checksum. Download links are shown only after the public release feed has been checked. If the feed cannot be verified, the page hides the links rather than guessing which build is current.

The Windows installer is unsigned. Windows may warn about an unknown publisher. Only continue if you trust the source and the build. Do not disable Windows security to install Little Loam. A matching SHA-256 checksum checks file integrity, not publisher identity.

If installation or updating fails, include the displayed version and build number, Windows version, and exact warning or error. Do not uninstall the game or delete its saved data as a first troubleshooting step when progress is at risk; contact support first.

Reporting a bug

A useful report explains what you expected, what happened instead, and the steps that led there. Include your game version and platform. For a Deep problem, include the set and floor and whether you were solo or in a party. A screenshot can help; remove personal or sign-in information before sending it.

Your data and privacy requests

Read the website and game privacy policy for information about accounts, saved progress, friends, first-party game activity, and the separate website mailing list and analytics. Email josh@bluescripts.net to ask about access to or deletion of your information. These requests are handled through support; there is no automated account-deletion flow on this page.