Nyxie is the custom-branded Sapphire bot used by TSHE. It connects the community's reporting, case-management, warning, appeal, verification, and safety workflows so staff can respond consistently and keep an auditable record of moderation activity.

Member-facing overview

Nyxie supports moderation decisions and community operations. Automated signals can surface possible problems, while staff remain responsible for reviewing context and applying server policy.

What Nyxie helps with

Area	Purpose
Reports	Collects member reports and routes them into a trackable staff workflow
Cases	Records moderation actions, reasons, evidence references, and status
Warnings	Tracks active warnings and supports the documented escalation ladder
Appeals	Connects cases to the formal appeal and response process
Tickets and modmail	Keeps private support conversations organized
Verification	Supports onboarding and access-control checks
AutoMod	Detects common spam, unsafe files, suspicious links, mass pings, and other configured risks
Server protection	Supports anti-raid, quarantine, channel-locking, and account-safety workflows

Browse the complete command reference for every slash command, prefix command, alias, usage form, and access requirement.

What members should expect

Clear notices. When an action requires a notification, Nyxie can deliver the reason and relevant case information.
Consistent records. Warnings, notes, reports, and cases are stored as part of a single moderation workflow.
Private handling. Reports, tickets, and appeals belong in their designated private systems rather than public channels.
Human accountability. Staff review moderation context and remain accountable for decisions made with Nyxie's tools.

Using Nyxie safely

Use commands only in channels where they are permitted.
Read every prompt before submitting a report, ticket, or appeal.
Provide accurate information and relevant evidence.
Never send passwords, authentication tokens, backup codes, or unrelated personal data.
Do not spam commands, repeatedly test filters, or attempt to discover bypasses.
Report unexpected behavior through the normal support process.

How does Nyxie's automated moderation work?

Nyxie can evaluate configured signals such as repeated messages, cross-channel spam, mass pings, suspicious invitations or links, unsafe file types, excessive media, and other content patterns. Signals may be logged, blocked, or sent for staff review depending on server policy.

Exact detection logic and operational thresholds are intentionally not published because doing so would make evasion easier.

Can Nyxie make mistakes?

Any automated system can misunderstand context. If you believe content was incorrectly blocked or an action was associated with the wrong account, preserve the relevant message link or screenshot and open a support ticket. Do not repeatedly repost the content to test the system.

What happens to moderation records?

Authorized staff can use Nyxie's case tools to review active actions and their supporting record. Access is permission-controlled. Public users cannot browse private cases, reports, tickets, or internal logs.

If you need help

A command failed: wait briefly, retry once, then open a support ticket with the command name and time.
A filter appears incorrect: do not attempt a bypass; provide the original context privately.
You need to report a member: use the official report or ticket flow and include evidence.
You disagree with an action: use the official appeal process rather than contacting staff in DMs.

About Nyxie

Nyxie is a custom-branded Sapphire bot. It was not created by f34rless.dev. Our Sapphire configuration is private and will not be provided or shared. Read more about Nyxie.