Platforms
Platforms
Lingchu Bot organizes platform support around three layers: platform, protocol, and implementation. This separation keeps each layer's behavior, capabilities, and configuration concerns isolated instead of mixing them into a single page.
Layer model
| Layer | Purpose | Examples |
|---|---|---|
| Platform | The chat network the bot connects to | |
| Protocol | The wire/API standard the adapter implements | OneBot V11 |
| Implementation | A concrete server that speaks the protocol | NapCat, default |
A platform profile (in platforms/registry.py) declares the known protocols and their priority. Each protocol maps to a NoneBot adapter package. Within a protocol, one or more implementations may extend the default handler set with implementation-specific APIs.
Available platforms
| Platform | Protocols | Status |
|---|---|---|
| OneBot V11 | Implemented |
For protocol-side runtime setup, see Framework Integrations.
Adding new platforms
Platform profiles for Telegram, Discord, and others are candidates for future work. See Adapter Guide for the contribution workflow.
How commands are scoped
Command handlers live under handle/<platform>/adapters/<protocol>/<implementation>/. The menu system filters visible commands by the active platform, protocol, and implementation at runtime, so implementation-specific extension APIs (for example, group announcements on NapCat) are hidden unless the current runtime is known to support them.
See QQ Platform for protocol- and implementation-specific command references.
Last updated on