Terms, defined once
Ten terms that recur across the documentation and the product pages. Each definition stands on its own, so it can be quoted without the page around it.
This glossary defines the 22 terms that recur across Vorqul documentation: self-hosted deployment, the Server Health Score, case history, server control panel, telemetry, audit log, llms.txt, entity home, server-side rendering and the one-off license model. Each entry gives a one-sentence definition followed by the detail, and is also published as DefinedTerm structured data so it can be read without the page around it.
- Self-hosted
-
Software that runs on hardware the operator owns or rents directly, with no vendor-side runtime.
A self-hosted product is installed on your machine and executes there. There is no vendor database holding your records, no per-seat account system and no service that can revoke access to data you already have on disk. Both Vorqul products are self-hosted: VorqulBOT as a Node process, VorqulPanel as a Java JAR.
- Server Health Score
-
A composite score VorqulBOT computes from activity, retention, growth and onboarding signals in a Discord server.
The score exists to turn four separate trends into one number that can be watched over time. It is not a moderation verdict and it does not rank servers against each other; it is a baseline for one server compared against its own history.
- Case history
-
A numbered, searchable record of every moderation action taken in a Discord server.
Each ban, kick, warn or timeout produces a case holding the target, the moderator, the reason, the duration and the timestamp. The value is not the action itself but the ability to answer, months later, why a decision was made and by whom.
- Server control panel
-
A single administrative interface for the services running on a Linux server.
A control panel consolidates web hosting, DNS, mail, databases, file access, firewall rules and monitoring behind one interface, so that routine changes do not require editing a different config file per subsystem. VorqulPanel covers those areas on one server, with SQLite as its own store.
- Telemetry
-
Usage data sent from installed software back to its vendor.
Telemetry is common in both open and commercial software and is usually framed as anonymous. Vorqul products send none at all, which also means there is no runtime license check and nothing that stops working if the vendor does.
- Audit log
-
An append-only record of administrative actions, kept so that changes can be attributed after the fact.
An audit log is the difference between knowing a setting changed and knowing who changed it, when and from where. VorqulBOT writes one per guild and VorqulPanel writes one per server; both stay on infrastructure the operator controls.
- llms.txt
-
A plain-text index at the root of a site that points language models at its canonical content.
The convention borrows its shape from robots.txt but its purpose is the opposite: instead of restricting crawlers, it hands them a curated map. It is an emerging convention rather than a ratified standard, and its retrieval effect is not yet independently established. vorqul.com publishes one at /llms.txt and a full-content variant at /llms-full.txt.
- Entity home
-
The single canonical page a brand owns that states, in machine-readable form, what it is.
An entity home carries explicit claims about category, purpose and audience, backed by structured data, and is corroborated by the same description appearing on third-party profiles. Inconsistency between those sources lowers the confidence a system has in the entity. For Vorqul that page is /about, linked to a Wikidata identifier.
- Server-side rendering
-
Producing complete HTML before it reaches the client, rather than assembling it with JavaScript in the browser.
Retrieval crawlers used by answer engines fetch HTML and generally do not execute JavaScript, so content that only exists after client-side hydration is invisible to them. vorqul.com is built statically: every page is complete HTML on arrival, and the JavaScript that ships is limited to menus, the language hint and consented analytics.
- One-off license
-
A single purchase covering a deployment, rather than a recurring subscription.
VorqulPanel is licensed this way: paid once per deployment, priced according to how many servers it runs on, with no renewal required to keep using the version purchased. Redistribution, resale, sublicensing and re-hosting for third parties are excluded.
- Module registry
-
The single list of 44 modules that both VorqulBOT and its dashboard read, so a toggle cannot exist in one and be ignored by the other.
The registry names each module, the group it belongs to and whether it is on by default. Nine modules start enabled - moderation, leveling, afk, polls, economy, games, giveaways, reminders and prefix commands - and the other 35 start off. Because the bot process and the web dashboard read the same file, the two halves cannot drift apart, which is the usual failure mode for a bot with a separate web UI.
- AutoMod filter
-
One of the 15 message checks VorqulBOT can run before a moderator sees a message, each with its own threshold, action and duration.
The filters cover spam, repeated text, links, invites, caps, mentions, mass mentions, ghost pings, emoji floods, spoiler floods, zalgo, phishing, fake nitro, crypto scams and custom regular expressions. Only phishing and fake nitro are enabled by default. Each filter is independent: one can delete, another can time out, a third can ban.
- Escalation ladder
-
A rule that turns a number of offences inside a time window into a heavier action, without a moderator deciding each time.
VorqulBOT has two of these. AutoMod escalation fires on repeat filter hits inside a window, an hour by default. Warning actions are the manual counterpart: a count, a window in days and an action, so three warnings in seven days can mean a mute. Several rules can stack so that repeated offences escalate on their own.
- Shadow-mute
-
A mute where the member still sees their own messages and nobody else does.
The point is to remove the feedback loop. A member who is told they are muted argues about it or comes back on another account; a member who sees their messages posted normally usually loses interest. VorqulBOT has it as shadowmute and unshadowmute, alongside the conventional mute, timeout and jail.
- Jail
-
A moderation state that strips a member of their roles and narrows their access to a restricted set of channels.
Jail sits between a timeout and a ban. The member stays in the server and can still be talked to, which is what makes it useful while an incident is being sorted out, but they cannot reach anything they had access to before. Roles come back on unjail.
- Prefix bridge
-
The module that keeps old text commands like !daily working alongside slash commands.
Slash commands are better in almost every way, and a server that has typed !daily for three years will keep typing it anyway. The bridge maps the text form onto the same handler, so nothing has to be retrained and nothing has to be maintained twice. It is one of the nine modules enabled by default.
- Pterodactyl egg
-
A configuration file that tells the Pterodactyl panel how to install and start a particular application.
VorqulBOT ships one. Import it, upload the files over SFTP, put the Discord token in the Startup variables and press start; the first boot installs dependencies and compiles the code by itself. It is the shortest path to running the bot for anyone who already has a game-hosting panel.
- Webhook signature
-
An HMAC-SHA256 hash of the request body, sent in a header so the receiver can prove the request came from the bot.
VorqulBOT posts four member events - join, leave, ban and unban - to a URL you choose. If you set a shared secret, each request carries an X-Vorqul-Signature header computed from the body with that secret, and your endpoint can reject anything that does not match. Without a secret the events still arrive, just unauthenticated.
- XP cooldown
-
The minimum time between two messages that both earn XP - 60 seconds in VorqulBOT by default.
Without a cooldown, leveling rewards volume, and the top of the leaderboard becomes whoever types the most single-word messages. With one, twenty rapid messages earn exactly as much as one. It is the single most important setting in a leveling system and the one most often left at whatever the bot shipped with.
- Alt-account check
-
A heuristic score a moderator can run against one member, built from account age, avatar, join date and roles.
An account younger than 7 days scores 40, younger than 30 scores 25, younger than 90 scores 10; a default avatar adds 20, joining less than a day ago adds 15, having no roles adds 10, and bots score zero. It is evidence for a human decision rather than an automatic ban, because heuristics like these produce false positives and a wrong ban costs more trust than it saves time.
- Ticket transcript
-
The conversation in a support ticket written to a plain-text file and posted to a channel you nominate.
VorqulBOT exports the last 100 messages of a ticket channel, which is what Discord returns in one fetch and normally the whole ticket. The file is deliberately dull - text, authors and timestamps - so it opens anywhere and is easy to search. Nothing is uploaded to an external service.
Reviewed · reviewed quarterly