HoneyGate Docs
Pricing Add to Discord

How HoneyGate works for owners

The big picture for running your server: the "rules give roles" model, and where to start.

This is the starting point for the owner/staff guides. If you've just added HoneyGate, do First-time setup first, then come back here.

The core idea: rules that hand out roles

Most of HoneyGate follows one simple pattern:

When [something is true] → give this role.

You set a rule once. HoneyGate then enforces it for everyone, automatically, for as long as you leave it on. A few examples:

Almost everything here grants roles, so the single most important setup step is your role hierarchy. Drag the HoneyGate role above any role you want it to manage. If you only read one troubleshooting page, make it Bot permissions & role hierarchy.

  1. Welcome messages greet new members.
  2. Self-assign roles let members pick their own roles.
  3. Points & XP rewards activity.
  4. Leveling & role rewards (Free) turns that XP into levels and unlocks roles.
  5. From there, add what you need: quests, giveaways, a shop, tickets, moderation, and the rest.

Once you're set up, Recommended setup walks you through a sensible starting configuration.

Gating by token or NFT (optional, for crypto communities)

If your community is built around a token or an NFT collection, HoneyGate can check a member's wallet and grant roles based on what they hold. You build a gate:

One-time setup: crypto gating reads the Solana chain through a free Helius API key you paste into Web3 settings — the same key that powers the other crypto tools. Add it once. Without it, token and NFT gates stay dormant, and they never remove a role they couldn't check.

  1. Make sure wallet verification is on. Members link a wallet with /verify.
  2. Create a gate. Choose the condition (a token with a minimum amount, an NFT collection, or a specific NFT trait), say how many they need to hold, then pick the role to grant.
  3. (Pro) Combine conditions with AND/OR logic, or gate on individual NFT traits.

Every gate on the Gates page shows the rule it enforces in full — "≥ 500 of $BONK", "≥ 3 NFTs from Pixel ZomBabiez" — so you can see at a glance what each role actually costs. The number on screen is always the number being enforced. NFT and trait rules count whole NFTs, so a part-number is rounded up (2.5 becomes 3) and the smallest you can ask for is 1; token amounts keep their decimals, because half a token is a real amount. If what you type isn't what gets saved, the confirmation message says so and gives you both numbers — it never just says "saved".

To change a threshold later, open the gate and edit the number in place; you don't remove the condition and add it back, which would leave the gate briefly asking for the wrong amount.

Supported wallet-change notifications request a priority check. Routine checks run daily to reduce Helius usage. New verifications and manual requests also receive priority. A missed notification may be caught by the next daily check. The free plan includes up to two token gates and two NFT gates. Pro adds combo and trait gating, raises token gates to 10, and lets you add unlimited NFT gates. If the blockchain provider is unavailable or limits requests, HoneyGate pauses the affected checks and retries later. It preserves existing roles during an unreliable check and does not grant new roles using outdated balance evidence. Temporary provider limits retry automatically with gradually longer pauses and respect the provider's retry instructions. The portal shows when a check is waiting for the holdings provider. Waiting does not add wallet failure penalties. The platform owner can also set a server spending limit without Helius account details. It caps estimated data-request spending over a rolling 24 hours, reserves one quarter for priority checks, and spreads routine work through hourly limits. Checks wait for capacity and resume automatically. Existing roles are preserved; the Gates page shows the limit and the member page explains spending-related waits. This does not disable any gate or guarantee a provider bill: external usage and webhook deliveries or edits can still consume credits outside request admission. A 429 warning alone does not confirm that the provider's credits are exhausted.

Large NFT checks run in small batches and save progress between runs. A paused check continues from its saved place when that information is still usable. Member requests and wallet-change events check the member's linked wallets directly, then reuse the result across this server's role rules. They do not wait for every gated collection to be scanned. Checks already in progress resume before untouched checks in the same queue lane; other servers still get turns. The Holdings checks page distinguishes a check continuing in batches from a failed check waiting to retry. Roles update only after the full check completes. Your operator receives one warning for a provider incident while checks continue to retry automatically. Recovery waits for completed holdings refreshes at least fifteen minutes apart without another recorded rejection. Individual successful pages cannot announce recovery, and other stale assets keep their own warnings.

Collection holder snapshots belong to your server and use its own Helius key. Other servers gating the same collection cannot replace your snapshot or change its check time. Background work uses shared collection scans only when completed measurements show a saving and the scan is small enough. Members within your server reuse those complete snapshots to avoid repeat lookups.

None of this is required. If you're not a crypto community, skip the whole section.

Free vs Pro

Some features below are marked Pro. See Free vs Pro for the full split. You never pay for anything you haven't turned on.