How mihaelaaa-23/pad-student-id-please works
Student ID, Please is a Discord-server moderation game organized as microservices. A shift brings players together to review generated applicants: they check credentials, hidden university records, and current server rules; a moderator then decides Accept, Reject, Flag, or Ban. The session service coordinates the shift, and its result feeds player progression. The README documents the service boundaries and integrations, but service implementations were not sampled, so edges reflect only those documented relationships.
Main entry points: server-moderation-session-service Session Service · applicant-service Applicant Service · moderation-service Moderation Service · credential-service Credential Service
Components 18
Shift Coordination
- Session Service
services/server-moderation-session-service - Session Store
db/session-service/init.sql
Applicant Evidence
- Applicant Service
services/applicant-service - Applicant Store
db/applicant-service/init.js - Credential Service
services/credential-service - Credential Store
db/credential-service/init.js - University Records
services/university-record-service - Records Store
db/university-record-service/init.sql - Server Rules
services/server-rules-service - Rules Store
db/server-rules-service/init.js
Moderation & Communication
- Moderation Service
services/moderation-service - Decision Store
db/moderation-service/init.sql - Discord DMs Service
services/discord-dms-service - DM Store
db/discord-dms-service/init.js
Player Progression
- Player Service
services/player-service - Player Store
db/player-service/init.sql
Other components
- Players
- Applicants
Connections 26
- Players → Session Service: join shifts
- Session Service → Players: publishes results
- Player Service → Session Service: coordinates joining
- Session Service → Applicant Service: requests applicants
- Session Service → Credential Service: requests credentials
- Session Service → Server Rules: requests rule checks
- Session Service → University Records: requests records
- Applicants → Applicant Service: profile input
- Applicant Service → Credential Service: propagates shared data
- Applicant Service → University Records: propagates shared data
- Credential Service → Applicant Service: initializes shared data
- Credential Service → University Records: propagates shared data
- Moderation Service → Applicant Service: gathers profile
- Moderation Service → Credential Service: gathers credentials
- Moderation Service → Server Rules: gathers rule results
- Moderation Service → University Records: gathers records
- Moderation Service → Discord DMs Service: posts verdicts
- Session Service → Player Service: sends shift results
- Applicant Service → Applicant Store: reads/writes profiles
- Credential Service → Credential Store: reads/writes credentials
- University Records → Records Store: reads/writes records
- Server Rules → Rules Store: reads/writes rules
- Session Service → Session Store: reads/writes shifts
- Moderation Service → Decision Store: records decisions
- Discord DMs Service → DM Store: reads/writes messages
- Player Service → Player Store: reads/writes progression