Warm a new database with shared history

With contribution and guidance enabled, a thin keyless ledger can import recent completed-sale observations for supported plain-item markets. Enough distinct sales and recent evidence are required. Shared asking prices and order offers do not become completed sales, owned stock or booked profit. This can reduce repeated startup reading; it does not guarantee immediate trading, market coverage or profit. Local collection continues when history is unavailable or insufficient. Fresh live prices, inventory, ownership and safety checks still decide every trade.

On the website, bot cards and the Swarm rank/statistics pair use two columns on desktop and one column on narrow screens. A missing rank now explains when no client is connected; routine rank updates retain the statistics card.

What is the Swarm?

Each bot sees only part of the market at a time. The Swarm collects observations from participating bots so another bot can use recent information when deciding which markets to investigate. Bots both contribute and query; this is a shared pool of observations.

Hive means your own connected bots. Swarm means participating bots across all users. One bot can join: you do not need two accounts, a local shared database or headless mode. Local Hive setup remains a separate feature.

“API” is the connection the mod uses to exchange data with the service. Ordinary users do not need to write code, host a server, create a Discord bot or manually obtain an API key to join through the dashboard.

Why join?

Shared information is a discovery aid, not a promise of higher profit or faster trading. Receiving data is not proof that a scan was skipped. Conservative reuse requires valid, fresh coverage; ordinary live reads remain part of trading.

Join step by step

Update to the latest client to see the Swarm tab. Older builds keep linking under About → Dashboard.

1. Use the latest GoNuts client. Download the current Minecraft 26.2 mod. A downloaded update takes effect after the game next closes and launches normally; do this at a safe time, not in the middle of a trade.
2. Sign in on the website. Open gonuts.at/dashboard/ and choose Discord sign-in. Use your own Discord account.
3. Choose Link client. The website creates a pairing code that expires after five minutes. Keep it private and use a fresh code for each bot.
4. Enter the code in the intended bot. Open GoNuts → Swarm. Paste the pairing code, choose a recognizable client label and press Link dashboard & join Swarm. The local web panel’s Dashboard linking page also supports linking a selected account.
5. Understand what linking includes. Linking is your opt-in to Swarm contribution and discovery. There is no second enrollment switch. Sharing observed public market data is required while using the hosted dashboard.
6. Verify the client card. Return to the website and check that the intended bot is online. Repeat with a new pairing code for each additional bot.

Check it is connected

In the mod, open Accounts → Swarm to see connection and contribution status, your estimated Hive rank and fresh anonymous Swarm totals. Linked bots can open the remote dashboard directly from this tab. Scroll for the benefits and sharing details.

If a re-paired bot shows Upload refused (HTTP 403), install the latest update and use Renew Swarm membership or Retry Swarm connection in the Swarm tab. This renews membership through the currently linked dashboard. If the dashboard link itself was revoked, generate a fresh code on the website and pair again. Do not delete your trading data or reset positions.

Each card shows that bot’s activity and Swarm status. Look for the Swarm badge and its contribution/guidance status. The mascot’s face follows that bot’s state; on supported builds its antenna shows reported send and receive activity independently of other cards.

Antenna animation means transport activity. It does not mean a batch was accepted, a scan was avoided or a trade made money. If status shows a problem, read its explanation rather than treating the animation as proof of success.

The count distinguishes your linked Hive bots from active bots across the entire Swarm. Active means a participating installation uploaded within the last ten minutes. It is not the number of people, all-time sign-ups or bots currently executing a trade. The Swarm count appears only after sign-in and linking a bot. Other users’ cards, names and identities are not shown.

What you contribute

Participating bots contribute supported observations of public markets and follow activity: observed item/variant information, prices, quantities, listings, orders, follow trades and payment notices. These observations can include public in-game actor names and payment parties when the client actually observed them. Unknown actors are not invented.

Your private dashboard account and installation access remain protected. Seeing the anonymous Swarm count does not grant access to another member’s bot or controls. Market participants appearing in public observations are different from disclosing who owns a Swarm installation.

Never post your pairing codes, local credentials or Discord tokens. You do not need to give another person access to your Discord account to join.

Supported linked clients also share an hourly snapshot of recognized numeric trading settings with diagnostic and booked performance metrics. Service administrators use these privately to investigate bugs, compare configurations and refine features and beginner defaults. These snapshots exclude text/list settings, webhook URLs, credentials, player names and local paths; they are not published to other Swarm members. The snapshot time records when settings were observed, not the exact time they changed. Unlinking stops future snapshots.

Current clients also send required private diagnostic history for up to 24 hours independently of Swarm participation. It contains typed mod states, action outcomes, faults and recognized numeric settings, excluding names, chat, credentials, home names, local paths and raw Minecraft logs. Reports can privately reference available history across restarts. Unlinking Swarm stops market participation, not this diagnostics-only channel. Coverage gaps remain explicit; unavailable evidence does not invalidate a report. Public automatic issue filing remains a separate opt-in.

Your bot keeps control of execution

Shared observations do not replace current native price quotes, your own orders, inventory, available capacity, sizing, profit checks, spending caps or protective guards. An old shared price is not an executable offer. Missing or stale discovery data falls back to normal reads; a service outage does not itself stop ordinary trading.

The Swarm does not pool your money, sell another user’s inventory or share ownership of your orders. Your configured markets and limits still apply. Analyzer reviews local evidence separately; joining does not upload its settings report.

Your estimated Swarm rank

Your rank gives a rough idea of how your Hive stacks up against other currently contributing GoNuts users. It compares combined reported booked profit over the last 24 hours using available fresh client snapshots. Your bots are grouped into one Hive, and duplicate accounts count once. This is a comparison within GoNuts, not the entire Minecraft server.

With at least two Hives reporting usable profit, you can see #1 of 3 active Hives, for example. There is no 90% coverage requirement or 22-hour wait. If only your Hive has usable data, the dashboard says Waiting for another Hive. Connecting and contributing is all you need; rankings update automatically.

This is an estimate: a new client may have less history, and missing bot data can make a Hive total partial. Bankroll, number of bots and time spent trading affect the comparison. Ties share the same rank. Zero or negative reported profit is still valid. A percentile, if shown, means the percentage of other counted Hives with strictly lower reported profit.

There are six estimated standings: sale records per hour, profit per hour, profit over 24 hours, profit margin over 24 hours, revenue per hour and revenue over 24 hours. Each compares your Hive with active Hives reporting that measure, so the number compared can differ between rows. Missing revenue does not block profit or sale-record rankings. Margin requires positive booked revenue and uses profit and revenue from the same reporting bots.

Your overall Swarm score averages the available metric percentiles with equal weight on a scale from 0 to 100, then gives your Hive an overall position such as #1 of 20 Hives. It says how many of the six metrics are available. Missing metrics are left out, not counted as zero. This is a casual estimate: different Hives can have different amounts of history and available metrics. Ties share a position, and calculations use the full figures before rounding the display.

The ranking card also summarizes estimated collective profit and booked sales revenue for the last hour and 24 hours, using available reports from active contributors. Your share of Swarm profit is your Hive's reported profit divided by the reported Swarm total; profit margin is profit divided by sales revenue. They are different measures. Missing revenue from older builds stays unavailable or partial until clients update normally. Totals and sale-record counts are rounded for display (for example, 230.9M coins and 5.9K sale records); the calculations use the full reported values. Sale records are not necessarily unique trades.

You see your own result and the number of Hives compared, never other users' identities, bot cards or financial figures. Disconnected, unlinked, non-contributing or stale snapshots are excluded until current data becomes available.

Stats across the whole Swarm

The dashboard's Swarm stats section summarizes participating Hives and bots across GoNuts, even when there are too few Hives for a rank. It shows active participation, market coverage, retained sale, follow-trade, order and auction/listing observations, plus available collective booked profit, sale records and revenue for the last hour and 24 hours. Fresh financial reports are combined with duplicate accounts counted once. Missing reports remain unknown or partial.

Each counter tells you what it measures. Stored observations are the records retained now, with the retention window shown; an observed listing is not a completed sale. Accepted uploads and observations measure information contributed to the service. API requests and database SQL statements measure service activity from the stated starting date, not avoided scans or completed trades. Activity counters are periodically saved and preserved across normal service restarts; they are estimates rather than a reconstructed all-time history.

Figures use compact K/M/B notation with exact values on hover. These are anonymous collective totals, not other users' bot cards, identities or individual financial figures. Sign in with a linked, opted-in bot that is connected and actively contributing to see the dashboard's shared section.

Shared Staff Watch sightings

The dashboard sidebar shows recent Staff Watch sightings reported by participating bots across the Swarm: the public staff name, broad region and last reported sighting. A sighting is evidence from an existing detector in that bot's region, not proof that staff are still there or watching a particular player. Global staff-online entries and disappearing TAB entries alone are not shared as local sightings.

You must be signed in with a linked, opted-in bot that is connected and actively contributing to see the shared feed. Supported clients share only new qualified detections while participating; older clients do not upload their old history. Reports expire after 15 minutes. The feed shares no reporting user's identity, bot identity, coordinates or server address. Unknown regions remain unknown. An empty feed means no recent shared reports, not that staff are absent.

This shared sidebar does not change your bot's Staff Watch protection, region-hop settings or alert delivery.

Leave the Swarm

Use Unlink locally in that bot’s Dashboard screen. In the local web linking page, use Unlink selected account for the intended client. Remove its offline entry on the website too. Unlinking stops that installation’s Swarm participation; closing a browser tab or signing out of the website does not unlink a running bot.

Leaving stops future participation. It does not imply that already accepted historical public observations are erased, or that your real stock and trading ledger are cleared.

Common questions

For persistent problems, use GoNuts → About → Report bug, or Report bug in a working panel. Include the running build, relevant status and approximate time. Read the reporting guide.