Archive Reference

Frequently Asked Questions

Answers to common questions about operating Guilty Spark across Discord automation, Individual Tracker workflows, and OBS overlay setup.

How can I support this project?

Guilty Spark is currently provided to the Halo community at no cost. If you want to support ongoing development and infrastructure, sponsorships are available through GitHub Sponsors or PayPal.

Where can I see the full feature and capability breakdown?

Use /capabilities for the latest mission map across Discord operations, live tracking, individual tracker workflows, and overlay output.

Where is the full command list for setup and account linking?

Use /discord-commands for slash command coverage, including /setup, /connect, and stats workflows.

Does Guilty Spark track ranked matches or only custom games?

Primary automation is optimized for custom game series, especially NeatQueue-linked workflows. You can still query a specific match using /stats match <match_id>.

Where is the full Live Tracker and Individual Tracker OBS setup guide?

Use the dedicated guide at /guides/obs-overlays for end-to-end setup flows, Browser Source recommendations, and troubleshooting notes for both overlay paths.

Can I customize which stats are displayed?

Yes. Server operators can tune Discord posting behavior via /setup, while tracker owners can tune overlay sections, ticker behavior, stat slot visibility, and style flags from tracker settings. The capabilities page summarizes these surfaces.

Is my data stored securely?

Guilty Spark stores operational data required for features such as account links, server setup, and tracker state. Sensitive tokens are handled server-side with strict controls. Webhook calls are protected with HMAC validation, and Halo privacy boundaries are respected.

Why aren't my matches showing up?

Check Halo privacy visibility, verify /connect is complete, and confirm the match composition fits the workflow you are querying. Recent matches can also lag in upstream APIs, so a short delay is normal.

Does the bot require special permissions?

Core permissions include View Channel, Send Messages, and Use External Emojis. For webhook-driven NeatQueue workflows, Manage Webhooks is required. Missing permissions can disable parts of the automation flow.