QQ Platform Overview
QQ Platform Overview
Section titled “QQ Platform Overview”QQ is the only currently implemented platform profile. The plugin selects one QQ adapter at startup via LINGCHUAdapter (default: ~onebot.v11).
Protocol priority
Section titled “Protocol priority”| Priority | Protocol | Adapter ID | NoneBot package | Status |
|---|---|---|---|---|
| 1 (default) | OneBot V11 | ~onebot.v11 |
nonebot-adapter-onebot |
Active |
Only one QQ adapter is considered enabled at a time. Other adapters that NoneBot loads are treated as disabled and excluded from platform resolution, message storage, and API call recording.
Switching protocols
Section titled “Switching protocols”Set LINGCHUAdapter in .env. Only OneBot V11 is active in the startup flow:
DRIVER=~fastapi+~httpx+~websocketsONEBOT_ACCESS_TOKEN=your-tokenImplementation matrix
Section titled “Implementation matrix”Each protocol has a default handler set and optional implementation-specific extensions:
| Protocol | Implementation | Extension highlights |
|---|---|---|
| OneBot V11 | default |
Core group management commands |
| OneBot V11 | NapCat | Group announcement + group avatar |
Source layout
Section titled “Source layout”handle/qq/├── commands/ # Shared QQ command definitions (Alconna matchers)│ ├── triggers.py # Command trigger words (zh/en)│ ├── mute.py│ ├── member.py│ ├── block.py│ ├── announcement.py│ ├── remote.py # Remote management commands│ └── ...└── adapters/ └── onebot11/ ├── default/ # OneBot V11 default handlers └── napcat/ # NapCat extensionsNext steps
Section titled “Next steps”- Connect QQ via NapCat — NapCat Docker setup and NapCat-specific commands
- Connect QQ via SnowLuma — SnowLuma Docker setup
- QQ Commands — Full command reference including remote management
- OneBot V11 default implementation — Default handler reference