AI Knowledge

AI Knowledge is where you describe what your gamemodes are and how your server is set up, so the AI chat understands the product behind the numbers. With that context, the chat stops being a search bar and starts giving you real advice — "your Skyblock D7 retention is low because your tutorial doesn't explain islands; here's what to change", instead of just "your D7 is 14%".

You write it once. The chat reads it on every question.

Why it matters

Analyse already knows your stats. It does not know your product. Without that, the chat can answer "what" and "how many", but it can't answer "why" or "what should I change".

A few examples of what changes when you add Knowledge:

In other words: Knowledge turns the chat from "data lookup" into "actually-useful coach."

What to put in

Think of it like onboarding a new staff member. What would you tell them so they understand the server?

Your gamemodes. For each gamemode: what it is, how it plays, how players earn / progress, what the early-game loop is, what the end-game loop is, what's unique vs other servers in the same genre.

e.g. "Skyblock — players spawn on a small island, mine cobblestone from a generator, expand the island, and unlock new island types via the /islands menu. Tutorial is the first 14 minutes. Main monetization is rank packages (VIP, MVP, MVP+) and cosmetic crates."

How your store is set up. Package names, what each one unlocks, your pricing tiers, any time-limited offers, your refund policy, your discount strategy.

How players progress. Levels, ranks, currencies, quests, key milestones (first kill, first island, first prestige).

Your campaigns and creators. Who plays which gamemode, when sponsorships ran, what the creative was about. Stops the chat from confusing pewds-may-2024 with pewds-may-2026.

Your custom events. What each event means, what its properties contain, when it fires. Lets the chat reason about funnels and conversion accurately.

Your community and rules. The vibe, the moderation rules, what your players love, what they complain about. Useful for retention conversations.

Your goals. What you're trying to grow this quarter (revenue, players, ARPU, D7?). The chat will weigh its advice toward what matters to you.

The more you write, the better the advice. Servers that get the most out of AI Knowledge usually have one document per gamemode plus a few cross-cutting docs (store, brand, goals).

Three kinds of source

Every Knowledge document is one of three types. Pick whichever is easiest for you.

Notes

A clean, full-page editor (like Notion) where you write whatever you want. Markdown shortcuts work: ## for headings, - for lists, > for quotes, **bold**, etc.

Best for: gamemode descriptions, store strategy, goals — anything you'd type fresh.

Files

Drop a file in (PDF, DOCX, Markdown, or plain text). We extract the text and index it.

Best for: existing PDFs (rules pack, sponsor deck, brand guide), DOCX exports from Google Docs / Notion, Markdown files you already wrote.

Files up to a few MB. Images inside the PDF / DOCX aren't read — only text.

URLs

Paste a public URL. We fetch the page, pull out the readable text, and index it.

Best for: your existing wiki page, a docs page you published, your store's information page.

The page must be publicly accessible (no login required).

Where it lives

Knowledge documents are scoped — they belong to either a Server or a Network.

1. 1

   Open Server settings → Knowledge

   For docs that are specific to one gamemode (e.g. "How Skyblock works", "PvP arena rotation").

2. 2

   Open Network settings → Knowledge

   For docs that apply to every Server in the Network (e.g. "Brand guide", "Store strategy", "This quarter's goals", "How we name Campaigns").

When the chat is open on a Server inside a Network it searches both the Server's docs and the Network's docs. So shared context only needs to be written once at the Network level.

Adding a Knowledge document

1. 1

   Open Settings → Knowledge on a Server or Network

   You'll see a list of every document already added.

2. 2

   Click "Create knowledge"

   You go into a guided two-step flow.

3. 3

   Step 1 — pick a source

   Note, File, or URL. Click the card and click "Continue".

4. 4

   Step 2 — give it a title and add the content

   The title is just a label so you can recognise it later. The body is the real content (the editor / file picker / URL field).

5. 5

   Click "Create knowledge document"

   We extract the text, index it, and the chat starts using it on the next question.

Each document is processed in the background. You'll see a status next to it:

• Ready — the chat is using it
• Processing — we're extracting and indexing the text (refresh the page after a few seconds)
• Needs attention — something went wrong (usually an empty file or an unreachable URL); the document didn't get indexed

Editing and re-indexing

Click any document to open it. Updating the title is instant. Updating the content triggers a re-index — we throw the old version out of the search index and replace it with the new one. The chat picks up the new content on its next question.

Deleting a document

Click the trash icon on the document. We:

1. Remove every chunk from the search index
2. Delete the original file / extracted text from storage
3. Mark the document as deleted in our database

The chat will not see this document anymore.

Tips for great knowledge

• Describe the gamemode like you would to a new staff hire. What is it, how does it play, where do players get stuck, what makes money. The chat reads it the same way a new teammate would.
• One topic per document. "Skyblock — how it works" and "Skyblock — store packages" should be two notes, not one. Smaller docs make it easier for the chat to pull the right one.
• Lead with the punchline. First sentence of every section should answer the question. The chat retrieves the most relevant chunk; if the answer is buried at the bottom, it might not surface.
• Write down your goals. "We want to grow D7 this quarter" tells the chat what to weigh its advice toward.
• Use real names. Write pewds-may, not "the Pewds Campaign". Write quest_completed, not "the quest event". The chat matches on the exact words you'd use.
• Put shared context on the Network. Brand guide, store strategy, goals — Network level. Per-gamemode notes — Server level.
• Update when things change. Renamed a Campaign? Update the doc. Added a new gamemode? Add a doc. The chat is only as good as the latest version.
• Don't paste secrets. Knowledge docs are read by the AI on every related question. Don't put API keys or staff passwords in them.

What the chat does with it

When you ask a question, the chat searches your Knowledge docs (plus the Network's, if applicable), pulls the most relevant passages, and uses them as context alongside the live data it pulls from your Server. That combination — your numbers + your context — is what unlocks real advice instead of just stats.

You can also explicitly ask:

✅ "Look at my Skyblock retention this month, then check our Knowledge — what should I change first?"

Related

• AI chat — the chat that uses your Knowledge
• Networks — so shared Knowledge can cover every Server
• Custom events — pair event property docs in Knowledge with the events themselves