Community Rules & Enforcement Guidelines

CraftConfig.Studio is a professional workspace built around trust: clients share configuration files, payment details, and private information with us, and community members interact with each other daily. This document exists to make the standard of behavior we expect completely clear, and to explain how enforcement actually works, so that nobody is ever surprised by a decision.

Unlike a simple list of rules with a fixed penalty attached to each one, this document deliberately does not assign a specific sanction to each violation. Real situations are rarely identical: the same action can range from an honest mistake to a deliberate, repeated abuse depending on context, intent, history, and impact. For that reason, Article 2 and Article 3 below describe our enforcement philosophy in detail, and every rule category from Article 4 onward should be read together with them, not in isolation.

"Sufficient evidence" is deliberately not reduced to a fixed checklist, because what counts as sufficient depends on the nature of the case. In practice, staff typically rely on some combination of the following:

• 1 Message logs and screenshotsDirect screenshots or exported message history showing the behavior in question, ideally with visible timestamps and usernames.
• 2 Server and ticket logsDiscord's own audit log, ticket transcripts, and bot-recorded events, which CraftConfig.Studio retains for this purpose.
• 3 Payment and transaction recordsPayPal transaction IDs, order IDs, and Worker-side logs for anything related to payments, chargebacks, or promo codes.
• 4 Direct staff observationBehavior a staff member personally witnessed in real time within an official channel or ticket.
• 5 Corroborating reportsMultiple independent, consistent reports from unrelated members can support a case, though they are weighed carefully and are rarely treated as conclusive on their own.

A single unverifiable claim, a vague accusation with no supporting detail, or a report motivated by an unrelated personal conflict is not sufficient evidence on its own. When evidence is incomplete, staff will attempt to gather more before deciding, and may reach out to the parties involved for clarification. If sufficient evidence cannot reasonably be obtained, no sanction will be applied, even if staff privately suspect the report may be accurate.

This evidence requirement protects everyone: it protects the reported person from being punished on rumor, and it protects the reporting person by ensuring their report is taken seriously and investigated properly rather than dismissed.

Once sufficient evidence establishes that a violation occurred, CraftConfig.Studio staff have full discretion to decide which sanction, if any, is appropriate for that specific situation. This document intentionally does not lock a fixed penalty to each rule in Articles 4 through 16, because doing so would force staff to either under-react to a serious first-time offense or over-react to a trivial, well-intentioned mistake, simply to follow a rigid table.

Instead, staff choose from the following open menu of possible responses, selecting whichever combination best fits the specific case:

When deciding which of the above to apply, and for how long, staff weigh factors including, but not limited to:

• • Severity and real-world impactHow much harm the action caused or risked causing to another person, to CraftConfig.Studio, or to the community as a whole.
• • IntentWhether the action appears to have been a genuine mistake, a misunderstanding, or a deliberate, premeditated act.
• • HistoryWhether the person has prior warnings or sanctions on record, and how recently.
• • CooperationWhether the person acknowledged the issue and stopped once informed, or continued and escalated after being warned.
• • ContextWhere and how the action took place: a public channel, a private ticket, a direct message to another member, and so on.
• • Financial or security dimensionWhether the violation involved money, fraud, leaked files, or account security, which are generally treated with greater severity.

Because staff retain this discretion, two superficially similar cases can result in different outcomes if the underlying context differs, and a first-time, low-impact issue will typically be met with a lighter response than a repeated or high-impact one. Categories flagged as critical throughout this document (fraud, leaking, harassment of a serious nature, and similar) may warrant an immediate, severe sanction even on a first offense, once evidence confirms the violation.

• ✓Treat everyone with basic respectDisagreements are fine; personal disrespect is not.
• ✓Keep discussions mature and on-topicUse the channel that matches what you're discussing.
• ✓Communicate in English or SpanishOur primary support languages, so staff and members can follow along.
• ✓Assume good faith firstAsk for clarification before escalating a disagreement into conflict.

• ✕Passive-aggressive or condescending behaviorRepeatedly belittling members, mocking questions, or "backseat moderating".
• ✕Deliberately derailing conversationsRepeatedly steering a channel off-topic after being asked to stop.
• ✕Excessive negativity or drama-seekingDeliberately stirring conflict between members for entertainment.

Situations under this article are typically addressed with a notice or warning first, escalating only if the behavior continues after being pointed out. See Article 3 for the full range of possible responses.

This is treated as one of the most serious categories in this document.

• ✕Targeted insults or slursDirected at a person's identity, appearance, background, or ability.
• ✕Pile-on harassmentCoordinating with others to repeatedly target a single member.
• ✕Doxxing or threats to expose private informationSharing, or threatening to share, someone's real identity, location, or personal data without consent.
• ✕Threats of violence or sabotageIncluding threats to damage, hack, or disrupt someone's server or business.

Because of the severity of this category, once evidence confirms a violation, staff may apply an immediate, severe sanction (up to a permanent ban) even for a first offense, per the discretion described in Article 3.

• ✕Message floodingSending repetitive text, emoji spam, walls of code, or the same content across multiple messages in quick succession.
• ✕Cross-postingPosting the exact same question or request in multiple channels instead of waiting for a reply.
• ✕Excessive or unnecessary @mentionsRepeatedly pinging staff or other members without an urgent, valid reason.
• ✕Mass-mentioning everyone or rolesUsing @everyone, @here, or large role pings without staff authorization.

Genuine urgency (for example, a security concern or an active payment issue) is not penalized under this article; use good judgment and explain the urgency briefly when reaching out.

CraftConfig.Studio is a professional development workspace, not a general social server. The following are not permitted in any channel or ticket:

• ✕NSFW or sexual contentImages, text, or links of a sexual or explicit nature, in any form.
• ✕Gore or graphic violenceShocking or disturbing imagery shared for shock value.
• ✕Offensive memes or shock contentContent designed primarily to offend or provoke.
• ✕Divisive political or religious debateKeep shared media and discussion related to Minecraft, development, or clean casual conversation.

To avoid confusion and false expectations among members, official pricing is managed exclusively by CraftConfig.Studio. The following are not permitted:

• ✕Quoting or guessing prices on behalf of the studioOnly official channels and staff communicate current rates.
• ✕Spreading outdated or incorrect pricingSharing a price you saw previously as if it still applies, without checking.
• ✕Claiming false discounts or promotionsTelling other members a discount exists when it does not.

If you're unsure of current pricing, always check the official plans page or ask staff directly rather than relying on what another member says.

• ✕Unjustified chargebacks or disputesDisputing a payment for a service that was actually delivered as agreed, without first contacting us to resolve the issue.
• ✕Forged proof of paymentEditing screenshots, faking transaction IDs, or presenting a payment that never actually cleared.
• ✕Fabricated or stolen promo codesUsing a discount code that was never issued, or was issued to someone else and not shared legitimately.
• ✕Requesting payment outside official channelsAttempting to pay, or asking someone else to pay, through an unverified method not listed in our Usage Policy.

Because this category involves real financial harm, once transaction evidence confirms a violation, staff may apply the most severe sanctions available, including a permanent ban, a permanent service blacklist, and a report to PayPal or other relevant authorities with the supporting evidence, per Article 3.

Full details of the trial program are in our Usage Policy, Article 4. In summary, the following are not permitted:

• ✕Requesting more than one trialThe trial is limited to one (1) sample per person, ever.
• ✕Using alternate accounts to claim additional trialsSee Article 15 on account integrity.
• ✕Pressuring staff for extra unpaid workBeyond the scope of the sample originally agreed.

This category is governed as a binding clause in Article 7 of our Terms of Service. The following are not permitted:

• ✕Reselling delivered workSelling, sublicensing, or redistributing a menu, configuration, or translation to another server or party.
• ✕Publicly leaking filesSharing raw configuration files or in-progress work on marketplaces, repositories, forums, or other Discord servers.
• ✕Passing off work as your ownRebranding delivered work and presenting it as independently created.

Given the direct financial and reputational harm this category causes, it is generally treated as critical, per Article 3.

• ✕Self-promotion in public channelsAdvertising your own server, service, or product outside of any channel explicitly designated for it.
• ✕Unsolicited DM advertisingSending promotional messages to members who did not ask for them; this is treated with particular severity given how invasive it is.
• ✕Sharing unofficial links as if they were oursOnly links listed in our official directory are verified; see Article 16.

Tickets are private workspaces for orders, payments, and support. The following are not permitted:

• ✕Opening empty or joke ticketsCreating tickets with no real request, wasting staff time.
• ✕Trolling within a ticketRefusing to engage seriously once a staff member responds.
• ✕Refusing to complete the required entry formServer version, plugins, and budget must be provided for a request to be processed.
• ✕Reopening a closed ticket to bypass a decisionRepeatedly creating new tickets to re-litigate an already-answered issue.

• ✕Ignoring direct staff instructionsPublicly arguing with a moderation decision instead of raising it privately or through Article 18 (Review & Appeals).
• ✕Impersonating staffUsing a similar username, avatar, or claimed role to make others believe you represent CraftConfig.Studio.
• ✕Falsely claiming authorityTelling other members you can approve discounts, sanctions, or exceptions you have no authority to grant.

Impersonation directly undermines trust in the entire community and is generally treated as critical.

• ✕Creating alternate accounts to bypass a limitSuch as claiming a second free trial, or rejoining under a new account to bypass a sanction.
• ✕Evading an active ban or timeoutRejoining the server through any means while a sanction is in effect.
• ✕Sharing account access to circumvent a sanctionAsking another member to act on your behalf while you are restricted.

Evidence connecting an alternate account to a sanctioned member (matching payment details, writing style, IP overlap reported by Discord's own systems, and similar) is generally treated as sufficient grounds for review under Article 2.

• ✕Sharing malicious or suspicious linksAnything designed to phish, scam, or compromise another member's account.
• ✕Sharing an unofficial link and presenting it as oursOnly the links listed in our official directory channel are verified.

If you encounter a suspicious link or a user claiming to represent CraftConfig.Studio outside of an official ticket, do not click it: report it immediately per Article 17 below.

If you believe a rule in this document has been broken, please open a ticket in our Discord server rather than confronting the person publicly. To help staff reach a decision as quickly and fairly as possible, include as much of the following as you can:

• 1What happenedA clear, factual description, without assumptions about intent.
• 2When and whereThe channel, ticket, or context, and an approximate time.
• 3EvidenceScreenshots, message links, or transaction details, per Article 2.
• 4Who was involvedUsernames of anyone directly involved, including witnesses if relevant.

Reports made in good faith, even if they ultimately do not result in a sanction due to insufficient evidence, will never themselves be treated as a violation.

If you believe a sanction was applied incorrectly, in error, or without sufficient evidence, you may open a ticket requesting a review. Explain calmly why you believe the decision should be reconsidered, and include any evidence supporting your position. Staff will re-examine the original evidence and your response before confirming or reversing the decision.

Appeals are handled with the same evidence-first standard described in Article 2: a sanction will not be reversed simply because it is disputed, but it will be reconsidered in good faith if new information changes the picture.