Windows desktop client
Building automation and world scanning for Minecraft
Launcher turns a schematic into an ordered placement plan and turns what you have already found into a ranked list of where to look next. The heavy calculations run on our servers; the client sends the inputs and shows what comes back.
At a glance
What you are buying, in five lines.
- Platform
- Windows, 64-bit
- Access
- An active subscription or a redeemed license key
- Running sessions
- One seat per running launcher, from one seat upwards
- Calculations
- Run on our servers and returned to the client
- Update channel
- Stable
Capabilities
What it does
Four calculations. The launcher collects the inputs, the server runs the maths and returns a structured result you can act on in game.
Build planning
Hand it a schematic of up to 512 blocks and get back an ordered, support-aware placement plan.
- Steps are ordered layer by layer and marked place, scaffold or remove-scaffold.
- Every step says whether the block is grounded, braced, scaffolded or unsupported.
- Scaffolding is added only where your reach setting cannot cover a block, up to twelve blocks high.
- The summary counts placements, scaffold steps, unsupported blocks and an estimated tick cost.
Ore forecasting
Turn where you have and have not found a material into a ranked list of places worth digging.
- Takes up to 512 observations, each one a coordinate and whether the material was there.
- Returns candidate cells with a confidence and the number of observations behind each.
- Search radius, cell size, result count and the minimum confidence are all yours to set.
Seed prediction
Estimate where structures and ore are likely to sit across a range of chunks.
- Overworld villages, pillager outposts, desert temples and ruined portals; nether fortresses and bastions; end cities.
- Ore estimates carry a material, a coordinate, a vein size and a confidence.
- A request covers at most 1024 chunks, so a scan stays a predictable size.
- These are model estimates with a confidence attached, not a promise about what a chunk holds.
Chunk anomaly scanning
Find the chunks that do not behave like the rest of the ones you sampled.
- Scores up to 512 chunks on block updates, entity count, tile entities, light updates and load time.
- Each chunk gets a score per metric and a classification: normal, watch, elevated or critical.
- Score against a baseline you supply, or against the sample in the request.
How it works
From subscription to a running session
Five steps, and the rules that hold at each one.
Subscribe or redeem a license key
Billing happens in your account in the browser. Access is granted from the payment state we verify with the payment provider, never because a browser reached a success page.
Install the launcher and register the device
The launcher creates a key pair on that machine and registers it. That key is the device identity from then on, and it is taken from the cryptographic proof rather than from anything the client claims about itself.
Start a session
The launcher requests a single-use launch ticket, valid for one minute, and redeems it. Redeeming takes one seat and releases the key that decrypts the local agent for that release.
Run calculations
The launcher sends the inputs, the server computes, the launcher shows the result. Every call re-checks your entitlement at the moment it runs, so access that has lapsed stops working immediately.
Close the launcher
The seat goes back. A running launcher sends a heartbeat every 30 seconds; when the heartbeats stop, the seat frees itself about 90 seconds later. You can also release a session from your account.
Boundaries
The website and the launcher do different jobs
Signing in here manages the account. Running calculations and receiving keys needs the launcher on a device you have registered.
In the browser
What a signed-in browser session is allowed to do.
- Start a subscription and open the billing portal.
- Redeem a license key.
- See your entitlement, your seat count and the sessions using them.
- List and revoke registered devices and sign out everywhere.
- Read the current published release.
In the launcher
What only a registered device with a launcher credential can do.
- Register the device and hold a device-bound credential.
- Take a seat by redeeming a launch ticket.
- Receive the payload key for the installed release.
- Run the calculations and submit longer jobs.
- A browser cookie can do none of these, on any route, no matter how it is presented.
Straight answers
Worth knowing before you subscribe
The limits are part of the product. Here they are in plain terms.
- Platform
- Windows, 64-bit. There is no macOS or Linux build.
- Connection
- The calculations run on our servers, so the launcher needs a working connection while you use them.
- Your inputs
- Every result is computed from the data the launcher sends. A small or lopsided sample produces a forecast to match.
- Seats
- A seat is a concurrent session, not an install. With every seat in use, the next launch is refused until one frees up.
- Downloads
- The download page lists the current build with its SHA-256 so you can check the file before running it. It is a discovery listing, not signed release metadata.
- Ending a subscription
- Cancel from the billing portal in your account. Access runs to the end of the period we have on record, then stops.