Skip to the dashboard

Last County — player dashboard

Dashboard

This is the shape of the player dashboard, drawn with nothing in it. Every value slot on the page is empty because there is nothing behind it yet: no account system, no payment path, no points ledger, and no save system in the game at all. Each panel says which of those it is waiting on.

Account

Needs an account system
  • Signed in as Nobody — there are no accounts
  • Wallet Not connected

    Connecting happens on the sign-in page, not here. This page makes no wallet calls of any kind and never will: it does not ask you to connect, sign, approve or confirm anything.

  • Member since — no value

Needs An account system: somewhere for an identity to live, and a server to keep it. A wallet connection alone is not a sign-in — a real one needs a signed login message, verified server-side, and neither the signing step nor the server exists. Connecting a wallet to a static page proves nothing to anyone and is remembered by nobody.

Get set up

0 of 4 available

  1. Get the game Not available

    Last County is in development for Windows on Unreal Engine 5.8. There is no packaged build to download yet, so there is nothing to install.

    The main page carries the download slot and it is empty for the same reason.

  2. Connect a wallet Not available

    Connect-only, on the sign-in page: it would read your wallet address and nothing else, and it would never ask you to sign a message, approve a transaction or type a seed phrase.

    Connecting grants nothing — no allocation, no item, no access.

  3. Link the wallet in the game Disabled in the build

    In-game wallet linking is an optional linked proof of control, not a login provider, an inventory authority or a currency ledger. It is switched off: its configured and compiled origin pins are empty and no trusted account-session provider is installed.

  4. Play a match Nothing is recorded

    Matches are local. Kills, credits and match XP live inside one match in one process and are gone when it ends; nothing is written down, so nothing can appear here afterwards.

Needs A packaged Windows build, a sign-in page, origin pins for the in-game link, and a match-history store — in that order. Every step above is blocked on a system rather than on a decision.

Balance

Needs a payment path

Account balance

— no value

No ledger exists to hold one.

Bonus funds

— no value

No promotion, no grant, no expiry date.

Match credits

— no value

In-match only. Deleted when the match ends.

Nothing here can be cashed out, and nothing is for sale on this page. The one credit that exists in the build is an elimination reward inside a single match: it is server-authoritative, it disappears with the match, and the code that awards it deliberately has no purchase, withdrawal or cash-out path in it. That is a design decision in the game, not a feature waiting on a switch.

Needs An account ledger, a payment path, and the legal and compliance work that has to come before either. None of the three exists, and the project's own tooling has a test that fails if trading or custody code appears.

Match record

Needs a match-history store

Matches recorded

0 zero

A true zero. The game has no save system at all.

Kills

— no value

Counted during a match, on the HUD. Not kept after it.

Headshots

— no value

The build flags the last kill as a headshot. It does not count them.

Season

— no value

Seasons are not a concept in Last County.

Statistic Today What it would take
Kills — Real and live: the counter exists in the character class and the HUD prints it. It needs somewhere to be written down when the match ends.
Headshots — A counter. Headshots are detected by bone name and the kill card prints the tag, but only the last kill carries a flag — nothing tallies them.
Deaths — A deaths counter. There is not one anywhere in the source: dying fires an event and nothing adds it up.
K / D — Cannot be computed. It needs the deaths counter above, and then a store to divide across matches.
Survivals and wins — Placement tracking. No placement, win, victory or last-survivor result is recorded by the build.
Games played — Something that counts matches. Nothing does.
Earnings — An account ledger and a payment path. Match credits are closed-loop and cannot leave the match, so there is nothing to carry into a career total.

Scroll the table sideways for the last column.

Needs A save system first — the build has none, so nothing survives the process — then a match-history store, then a deaths counter and a headshot counter for the two rows that have no source at all today.

Points

Needs a points ledger

Points

— no value

There is no points system.

Account XP

— no value

Match XP exists and is deleted with the match.

Needs A points ledger: an account to attach a balance to, a rule for what earns points, and a place to spend them. None of the three is designed, let alone built. Points are not a currency here and there is no exchange rate to anything.

Collection multiplier

Needs an item registry

Current multiplier

— no value

No multiplier exists to be at.

Item types held

— no value

Nothing is held by an account.

No collection multiplier is designed for Last County. This panel is the shape one would take, kept deliberately empty: no ladder of tiers is printed here, because writing tiers down is how a mechanic that nobody has decided on becomes a promise somebody made.

Needs Items that an account can own, a registry that says what types exist, ownership records, and a rule that reads them. The game has in-match loot and no account-owned anything.

Operatives and items

Needs account-owned items
  • Operatives owned — no value

    The survivors in the build are Epic Games’ Manny and Quinn mannequins, standing in until the real characters land. They are placeholders in a game build, not items in a collection, and they are not owned by anybody.

  • Weapons and gear — no value

    Weapons, armour, helmets and backpacks are real and tuned in the build. They are found in the match and lost with it: loot containers, a death bag and a crafting screen, none of it attached to an account.

Needs An inventory that outlives a match, which means an account, a server that owns the record, and a rule for how anything gets into it.

Account settings

Needs an account to attach to
  • Solana wallet Not linked
  • Connections None
  • Email and password Not used

    There is no email login and no password on this site, by decision rather than by omission. Nothing here will ever ask you for one, and there is no field on any page of it that accepts a credential.

Needs An account system, and before that a real sign-in: a signed login message with a nonce, a domain and an expiry, checked by a server. This site is a static page with no server, so today there is nothing on the other side of a setting to save it to.

What each panel is waiting on

Nothing on this page is live

The same list, gathered in one place. Everything in the middle column is missing; the right column is the order in which it would have to arrive.

Panel What it is waiting on Depends on
Account An account system and a signed sign-in A server. There is not one.
Get set up A packaged Windows build Nothing has been packaged yet, and the checklist that has to be met before a public release is unmet.
Balance An account ledger and a payment path An account system, and compliance work before any of it.
Match record A save system, then a match-history store An account system.
Points A points ledger and a rule that earns them A match-history store.
Collection multiplier An item registry and ownership records An account system.
Operatives and items An inventory that outlives a match An account system and a server that owns the record.
Account settings Something to save a setting to An account system.

Scroll the table sideways for the last column.

Read this as A specification, not a screenshot. Seven of the eight panels resolve to the same missing thing — an account system with a server behind it — and the eighth is waiting on a build. That is the honest state of the product today, and it is why this page shows you empty slots instead of filling them in.

Deposit SOL

Send SOL to the address below and it is credited to this account. The address is yours alone and does not change — sending to it twice is fine.

Not yet assigned

Deposited
— SOL
Confirmed transfers
—

Solana only. Sending any other chain’s tokens to this address loses them permanently, and nobody can reverse it. Send a small amount first if you have not used this address before.

What happens to it, and what cannot happen yet

Deposits are recorded as an append-only ledger, so a balance is the sum of confirmed transfers rather than a number a script edits. The same transfer cannot be credited twice: the transaction signature is unique in the database, so a watcher that restarts or runs twice inserts nothing.

There are no withdrawals. Paying money out needs a signing key that can move real funds, an approval step, a limit, a fraud hold, and a legal entity that is answerable when it goes wrong — none of which exist yet. Shipping deposits without withdrawals is a one-way door, so until that is resolved nothing here can spend.

What a paid mode needs before it opens is listed in the terms and the documentation.