ER:LC integration
The starting point for Watchpost’s future game connection.
There are currently no Watchpost ER:LC commands. Joining the PRC API community does not itself connect the bot or confirm API approval.
Start with read-only information
The proposed first milestone is a server status feature. Before adding remote actions, establish a reliable connection, confirm which server is selected and clearly distinguish fresh information from stale or unavailable information.
Player lists and other features should be added only after checking the current official PRC API documentation and the permissions available to the project. This draft does not promise particular endpoints or access levels.
Connection requirements
- Only an authorized owner should configure a game server connection.
- Credentials must stay on the bot's server, never in this static website.
- Each Discord server must be isolated from other communities' settings and data.
- Failures should explain whether the connection is missing, unavailable or rejected without revealing credentials.
Build for failures
Follow the API's current rate-limit guidance, use bounded retries and stop retrying invalid credentials. Do not display an old player count as live data. Show when a successful result was fetched and mark stale results explicitly.
Ready means tested
Test connection removal, key replacement, service downtime and attempts to access another server's data. Add a working command to the live reference only after its permissions, response and failure cases have been verified. See the proposed command reference for the initial naming plan.