IcePhox includes a full virtual economy, long-term progression systems, casino-style game features, giveaways, moderation and admin panels, support workflows, and Runtime and Automation systems. Some extras, such as Special Event Tools and certain owner diagnostics, only appear in supported setups or owner-managed environments.

IcePhox is publicly visible and has a public invite path, but it is not a one-size-fits-all bot where every feature appears everywhere. What you can use depends on server permissions, setup, enabled systems, and whether a feature is intentionally owner-only or server-specific.

No. IcePhox uses virtual in-bot currency and progression systems, not real-money gambling. Purchases such as Patreon or custom orders are support options for the project, not wagers tied to casino outcomes.

IcePhox is built and maintained by FirePhox, also shown publicly as FirePh0x. That includes the bot systems, public docs, website updates, and the ongoing feature work users see in the changelog and support materials.

The Ice Guide starts with the FAQ page: /icephox/faq.html. All frequently asked questions are posted there. If your question is not answered yet, DM FirePhox / FirePh0x and it will be added and answered as soon as possible.

Start by using the current public setup path correctly: make sure IcePhox is installed in the server, the bot can see the channel you are using, and the server has the permissions needed for commands and interactions. If the feature you are trying to use depends on a specific trigger phrase, runtime route, or owner-managed setup, use the exact supported flow for that environment rather than an old screenshot or cached message. If Ice still does not respond after that, treat it as a setup or runtime issue and report the exact server context and steps through support.

The exact permissions depend on which systems your server wants to use, but slash commands, message visibility, embeds, attachments, and interaction access are the common baseline. The simplest route is an admin-level invite, then narrowing permissions later if you want tighter control by channel or role.

The usual causes are missing Discord permissions, a feature being limited to certain roles or channels, a server-specific setup requirement, or the feature being intentionally owner/admin-only. If the bot was just added, also give Discord a moment to finish command propagation before treating it as a broken install.

First, confirm the bot joined successfully and responds to slash commands. Then check the FAQ for the setup and games sections, verify which features are actually visible in your server, and use the support page if something important is missing or misconfigured.

Start with the support page for the current public help route. If your server exposes them, /support is the in-bot path to support and /report is the fastest way to submit a bug with context instead of just sending a vague complaint.

Discord command propagation can take a little time. If commands are missing, re-open Discord, confirm the bot still has required permissions in that server, and test again after a short wait before assuming the install failed.

Most interaction failures are stale button or menu clicks on an older message state. Re-open the relevant command/panel and use the newest message controls. If the same flow fails repeatedly, report the exact steps through support.

They are different layers of the same growth model. Progression handles your regular climb, prestige adds reset-and-scale style advancement, mastery supports deeper long-term investment, and the vault acts as one of the systems that turns steady growth into stronger account value over time.

Yes. IcePhox stores the balance, progression, and runtime data it needs to keep systems working between sessions. The privacy policy covers the public-facing version of that: economy records, command and interaction data, and the basic identifiers required to run the bot correctly.

Yes. IcePhox is designed to keep logs and system state that help prevent abuse, investigate bad behavior, and protect the economy from obvious exploit paths. It is not meant to be a trust-everything sandbox where suspicious activity is ignored.

No. The economy is a major pillar, but IcePhox also includes giveaways, interactive panels, moderation and admin tooling, support flows, runtime features, and game systems. It is closer to a Discord ecosystem than a single-purpose wallet bot.

Progress handling is server and admin-policy dependent. Do not assume automatic transfers between servers or manual resets for every case. If you need a special review, open a support request with your exact server and account context.

Yes, systems can be tuned as features evolve. IcePhox is actively refined, so reward pacing, progression weight, and balance logic may be adjusted to keep long-term progression healthy and reduce abuse paths.

Poker Night is IcePhox's character-driven poker experience. It is built to feel more like a themed table than a plain text minigame, with custom table presentation, personality-driven flavor, and supported media elements that can make rounds feel more alive when those features are enabled.

Special Event Tools is an owner-scoped IcePhox feature with a dedicated activity/viewer surface. The current public feature set includes a read-only activity viewer and an owner-only /eventtools launcher in the supported environment.

Yes. Giveaways and event-style tools are part of the public IcePhox surface. The bot is meant to support community activity and server engagement, not just one isolated economy or casino loop.

Game systems are designed around fair gameplay logic for virtual-currency features, not scripted guaranteed wins. Outcomes can vary by mode and context, and balancing may be adjusted over time as systems evolve.

Audio features depend on runtime availability, permission settings, and server setup. If game logic works but audio does not, verify bot channel access and channel permissions first, then send a support report with server context.

Lifetime perks are one-time purchase options instead of recurring support tiers. Custom orders are the manual side of the project, where the work depends on scope and review rather than being an instant self-serve unlock.

Choose the lowest tier that covers what you actually want. Start with the entry tier if you just want to support the project, move up if you want stronger perk bundles or profile extras, and use the top tier only if you specifically want the most complete package shown on the perks page.

Not always. Some support perks are straightforward, but anything that needs manual review, syncing, design work, or owner setup should be treated as a human fulfillment flow rather than an instant automated delivery.

Yes. Delivery time depends on what you bought. Manual reviews, custom builds, special setup, or sync corrections can all take longer than a simple tier unlock, so do not assume every purchase is immediate.

No. IcePhox does not store raw payment details. Billing is handled by the payment platform you used, such as Patreon or PayPal, while IcePhox only deals with the support and perk side of the transaction.

Yes, tier and support status can change over time. Use the same provider where you subscribed for billing-level changes, then use support if you need help with perk state syncing or delivery verification.

Include the command or feature you used, where it happened, what you expected, what actually happened, and any exact error text, screenshots, or reproduction steps. A useful bug report makes it possible to fix the problem without first spending half the time guessing what went wrong.

If a feature mentions owner panels, diagnostics, special runtime setup, or server-managed infrastructure, assume it may be restricted. The website describes the product surface, but live availability still depends on the server, the permissions in that server, and whether the feature was meant for public use in the first place.

Use the docs navigation for the Terms of Service and Privacy Policy pages. Those pages are the public source for what the project collects, how data is used, what is not collected, and where to go with policy questions.

Use the privacy policy page first so the published rules are clear, then go through the support path if you need an actual answer or review. If /support is available in your environment, use that; otherwise use the public support page.

IcePhox stores the runtime and account data it needs to keep the bot working correctly. That includes things like balance and progression state, command and interaction records, and the basic identifiers needed to power support, moderation, economy, and system features. It does not treat the FAQ or support pages as a license to collect everything; the public Privacy Policy is the source of truth for what is collected, how it is used, and what is not stored.

Yes. IcePhox is still actively updated, and the public changelog and docs continue to move with it. If you want the clearest signal, look at the current FAQ, perks, support pages, and changelog rather than assuming an older screenshot still reflects the live project.