01 / FEATURE
Discord-native controls
Slash commands for play, pause, resume, skip, stop, queue and volume.
ARCHIVE / DISCORD BOT
A BOT THAT LISTENS
ECHO
A voice room with a soundtrack.
A TypeScript Discord music-bot experiment with slash commands, multi-server queues, and a Lavalink audio backend.
CASE FILE — 15
- STATUS
- IN TESTING
- YEAR
- 2026
- TYPE
- Discord Bot
ART DIRECTION / ECHOSTYLIZED CONCEPT MOCKUP
01
THE STARTING POINT
The idea behind it.
Build a Discord music-bot experiment with familiar commands and independent queues per server.
THE CHALLENGE
Connecting Discord voice, Lavalink, streaming sources, and playback events introduces failure modes outside the UI layer.
THE APPROACH
Use TypeScript and discord.js for interactions, Lavalink for audio transport, and embedded now-playing controls for Discord-native UX.
02
WHAT WENT INTO IT
Built with intention.
02 / FEATURE
Shared queues
Guild-specific queues keep listening sessions separated across servers.
03 / FEATURE
Interactive player
Now-playing embeds provide basic playback controls without leaving Discord.
04 / FEATURE
Voice infrastructure
A Lavalink audio backend with DAVE-capable versions, plus ongoing troubleshooting of external media sources.
03
STATE OF THE BUILD
Where it stands.
CURRENT STATUS / IN TESTING
Bot commands and Lavalink connectivity were exercised during development, but YouTube audio access is currently blocked by external client/HTTP errors. Not production-ready.
Currently in testing: YouTube searches may work while the stream itself is denied. No public bot invite is advertised.
04
THE NEXT ITERATION
Never really finished.
01
Verify a permitted audio source end to end
02
Improve playback error feedback
03
Consider saved playlists and admin tools