Community Group Rules

In one line

The AWMC x RankHub community groups are a place to talk about maimai DX and AWMC / RankHub services. To keep the conversation pleasant and the service running for the long term, please take two minutes to read the rules below.

These rules apply to all official groups listed below, and to any other group where the AWMC Bot is present. Joining a group means you have read and accepted this page.

These rules may change without notice

These rules may be adjusted at any time. Changes are not announced and are not notified individually; the current content of this page is authoritative. Staying in the group means you accept the latest version.

1. Groups and their purpose

Group	Number	Purpose	Join link
Group 1	1072033605	[Main] General chat and help	Join
Group 2	993795066	[Games] In-group mini-games	Join
Group 3	1094792527	[No Bot] Chat only, no bot features	Join
Group 4	1048450426	General chat, overflow	Join

Want to play games? Go to Group 2

To keep Group 1 pleasant for conversation, Group 1 does not host in-group mini-games (song guessing, guess-the-member, werewolf, polls, etc.). Join Group 2 (Games) to play.

Seats are limited: please join only the groups you actually need, and do not join several just to idle. Administrators may remove long-inactive placeholder members.

There is also a developer group 1067350296 for API integration and collaboration, see the Developer Center. These rules apply there as well.

No bots allowed in the groups — kicked on sight, no warning

No third-party bot may join any official group. This includes, but is not limited to:

• bots you self-host on frameworks or protocol backends such as OneBot / NapCat / SL (Shamrock, Lagrange, etc.);
• ready-made check-in, push notification, lottery, song-request or AI chat bots;
• any bot a member drags in "just to play around";
• alt accounts dressed up as bots, or bots renamed to look like a normal human member.

A bot found in a group is kicked immediately — no reminder, no grace period, no explanation. If you want to keep using one, host it in a private group instead.

The AWMC Bot itself, and official bots maintained by the admin team, are exempt.

How it is judged:

• What counts is whether it is an auto-replying bot account, not what it calls itself;
• Whoever invited the bot is responsible for clearing its leftovers (welcome messages, scheduled posts) after it is kicked; leaving them in place is treated as advertising;
• Inviting the same bot back repeatedly after it was kicked escalates against the inviter under section 6;
• A bot that only posts a few messages and then goes quiet still counts — "it hasn't spoken yet" is no excuse.

2. Respect each other

• Be civil. Insults, personal attacks, threats, discrimination, regional slurs, call-outs and doxxing are forbidden.
• Insults or verbal abuse directed at the bot, management team, project creators or persons in charge will result in a permanent account ban.
• Disagreement is normal — argue the point, not the person, and do not chase people around the group.
• Do not make jokes about someone's privacy, appearance or identity, and avoid humour that makes others uncomfortable.
• Impersonating staff, administrators, the Bot or other members is forbidden.

Display name requirements

Your group display name must be readable and usable as a name. The following are forbidden:

Type	Description
OPENID and similar identifiers	Platform-internal IDs, OPENID or Ref_ID values returned by the bot, tokens and other meaningless strings
Garbled or invisible characters	Garbled text, meaningless character dumps, blank names, zero-width characters and other names used to hide one's identity
Posing as the bot or staff	Names imitating the bot, administrators, the owner or the official team, including near-identical forms of identity-like names such as AWMC, Bot or 管理员
Impersonating others	Using someone else's name, avatar or identity markers in a way that causes confusion

Administrators may require you to change a non-compliant name; if it is still unchanged after a reminder, it is handled under section 6.

Cross-group call-outs and out-of-context reposting (permanent ban)

Do not take in-group chat records — messages from the owner, administrators, bot operators or members — and screenshot, forward or repost them out of context to other groups or platforms for the purpose of public accusation, opinion manipulation, provocation or retaliation.

Do not publicly insult, mock, single out or gang up on a member's words in other groups or platforms.

Anyone breaking this rule will be permanently banned as soon as it is discovered, with no separate warning. None of the following is a valid excuse: claiming it was a joke, claiming it was shared privately, or claiming the consequences were not foreseen.

In-group discussions should be resolved within the group. If you genuinely need to raise something with the admin team, submit it by private message with the full context; do not circulate cropped fragments.

3. Talk sensibly

• Helping others is encouraged, but nobody is obliged to answer.
• If a question gets no reply for a long time, check whether it is clearly written and gives enough background (platform, version, full error text, reproduction steps). The more specific the question, the easier it is to answer.
• Read the documentation and the command reference before asking; do not keep re-posting something the docs already answer.
• For bugs, account problems, wrong data or feature requests, post on the forum instead of @-mentioning the group owner or the admin team in the group.
• Avoid pushing unrelated topics for long stretches.

Having a problem? Post on the forum, do not @ the owner or admins

The group owner and the admin team are not a support desk. For bugs, account issues, wrong data or feature requests, check the documentation and the command reference first; if that does not help, ask on the forum:

👉 AWMC Bot board · bbs.wmc.pub/forums/awmc-bot.17

Include a clear description, the steps to reproduce, and the Ref_ID the bot returned. Repeatedly @-mentioning the owner, admins or bot operators to chase an answer, or pestering the admin team and members in private messages, counts as harassment: you will be reminded first, and muted for 1 day if it continues. Repeat offences escalate under section 6.

4. Forbidden content

The following are strictly forbidden; serious cases lead to immediate removal:

1. Unverified information — rumours, leaks, "I heard that...", unconfirmed screenshots and hearsay;
2. Repost-for-lottery, vote-begging, like-for-like chains — any invitation, vote, boost, bargain or group-buy link;
3. Cracking, modifying or cheating in maimai DX — including modded cabinets, private servers, account theft, boosting, and buying or sharing accounts;
4. Any detail that could affect the operation of the maimai DX China servers;
5. Advertising and promotion of any kind — third-party products, services, communities, sites, streams, commissions and traffic farming. What may be shared is limited to content from mainstream social platforms and AWMC / RankHub services;
6. Other services and bots of the same kind — do not bring up other score-lookup bots, status sites, group-management tools or similar services in the group, in any form: recommending them, comparing them, reviewing them, recruiting for them or driving traffic to them. The group is for using and troubleshooting AWMC / RankHub itself;
7. DM solicitation — advertising, group invites or sales sent to members in private messages count as advertising;
8. Other people's account credentials — SGWCMAID, official QR links, score-fetcher tokens and the like may not be requested, forwarded or displayed;
9. Cross-group call-outs and out-of-context reposting — screenshotting in-group chat records (including messages from the owner, admins and members) and reposting them out of context to other groups or platforms; publicly insulting, mocking or ganging up on members in other groups;
10. Anything illegal, pornographic, gambling-related, violent, politically sensitive, harmful to minors, or otherwise against the platform's rules.

Where rule 6 draws the line

Rule 6 targets other services and bots of the same kind; it is not a ban on every external name. Parts of the AWMC Bot's own functionality — such as 水鱼 / 落雪 uploads, TapTap cloud saves, arcade data sources and the like — are normal usage topics and may be asked about and answered freely.

A note on "sensitive details"

Please do not discuss or spread any non-public detail about the maimai DX servers, interfaces or operations. This is not topic censorship — it protects the service everyone here is using. Once such content spreads, everyone pays the price.

5. Message order

• No spam: repeating the same message, flooding with meaningless stickers or images, voice spam, or mass @-mentions.
• Quote only the necessary part of a message; do not repeat long quotes.
• Use bot commands appropriately, and avoid flooding with long commands (full help pages, batch queries). Abusing the bot API to scrape data or hog resources is forbidden.
• Send questions and discussion in separate short messages; keep one topic per message.

6. Enforcement

Administrators act according to severity and repeat count. The usual ladder:

Situation	Action
Minor, first offence (off-topic spam, mildly uncivil)	Verbal reminder, message recall
Non-compliant display name (OPENID, garbled, posing as bot or others)	Asked to rename; removal if unchanged after the reminder
Third-party bot joining a group (self-hosted OneBot / NapCat / SL bots, check-in or push bots)	Kicked on sight (removal), no separate warning
Harassing the admin team (chasing answers with @-mentions, unwanted DMs)	Mute for 1 day
Normal violation (spam, unverified reposts, mild advertising)	Warning, recorded
Bringing up other services or bots of the same kind (including recommending or driving traffic)	Reminder and message recall; repeat or clear traffic-driving goes to the next tier
Repeat or clear violation (advertising, lottery chains, sharing credentials)	Mute for 10 minutes to 24 hours
Serious violation (abuse, cracking/cheating content, operation-affecting details, API abuse)	Removal from the group (kick)
Insults or verbal abuse directed at the bot, management team, project creators or persons in charge	Permanent account ban
Reposting in-group messages out of context / publicly insulting members in other groups	Immediate permanent ban, no warning
Extreme or persistent (doxxing, fraud, organised abuse, harassment after removal)	Removal and permanent ban, plus a platform report if needed

Notes:

• Obvious violations — advertising, cracking/cheating, doxxing, sharing credentials — may be muted or removed without prior warning;
• Non-compliant display names (OPENID, garbled text, posing as the bot or staff, impersonating others) are handled with a chance to fix it first: rename on request, and removal follows refusal or a repeat offence. Using a fake identity for scams or solicitation is treated as a serious violation directly;
• Third-party bots get no grace period: kicked on sight, whether or not it has said anything and whoever invited it. Inviting the same bot back after a kick escalates against the inviter as a repeat violation;
• Out-of-context call-outs and cross-group insults are zero tolerance: breaking them leads to an immediate permanent ban, applying to every AWMC group the person is in;
• Harassment (repeatedly @-mentioning the owner or admins, unwanted DMs, continuing after a reminder) is muted for 1 day by default — "I was just asking questions" is not an exemption; ask on the forum instead;
• Bringing up other services and bots of the same kind (rule 6): a passing mention is handled with a reminder and message recall; recommending, comparing, recruiting or driving traffic, or continuing after a reminder, leads to a mute of 10 minutes to 24 hours; clear promotion of another service is treated as advertising;
• Mute length and whether to remove are at the administrator's discretion; repeated small violations escalate;
• Records are kept, and repeat violations across several groups count as the same person.

Cross-service consequences

Violations in the groups are not limited to group-level action. For serious or repeated violations, the AWMC team may restrict or ban the account across all AWMC services, including but not limited to:

Service	Possible effect
AWMC Bot	Restriction or ban of score lookup, upload, group features and account commands
AWMC API	Key revocation, quota restriction or access ban
AWMC KOA	Restriction or ban of the related features and permissions
Events and competitions	Disqualification, voided results or revoked prizes

The scope and duration of cross-service action are decided by the AWMC team based on the severity of the violation. See the Terms of Service & Privacy Policy for the account restriction rules.

7. Responsibility and appeals

• Everything you post must comply with the terms of service and community guidelines of the platform you are using. The group is not responsible for any ban or restriction resulting from a platform rules violation.
• Data and risks arising from use of the AWMC Bot are handled under the Terms of Service & Privacy Policy.
• If you disagree with a decision, message an administrator privately. Administrators will review it; a mistaken action will be reversed with an apology. A normal appeal is not harassment — just state the facts clearly and do not spam.
• "No harassment" here means unwanted, repeated pestering that continues after a reminder; it does not cover ordinary questions or appeals.
• Permanent bans may also be appealed once: message an administrator with the full context, and a confirmed mistake will be reversed. This does not change the "no prior warning" principle.
• These rules may be adjusted at any time and changes are not announced; the current content of this page is authoritative, and staying in the group means accepting the latest version.

8. Come and play

• Add the AWMC Bot: click to add, then bind your account to look up scores, queue cards and play guessing games.
• New here? Start with Getting Started; the full command list is in the Command Reference.
• Group owners and admins can send 群管理 to open the group console.
• If the bot misbehaves, keep the Ref_ID it returns — administrators can use it to look up the request chain.