Discord Player
Discord Player is a powerful framework for JavaScript and TypeScript, built on top of @discord.js/voice library.
It provides easy set of customizable tools to develop Discord Music bots.
![discordBadge](https://img.shields.io/discord/558328638911545423?style=for-the-badge&color=7289da)
Installation
$ npm install --save discord-player
$ npm install --save @discordjs/opus
$ npm install --save opusscript
Install streaming library (if you want to play from youtube)
$ npm install --save ytdl-core
$ npm install --save play-dl
Install FFmpeg or Avconv
Features
- Simple & easy to use 🤘
- Beginner friendly 😱
- A LOT OF AUDIO FILTERS (discord-player has total of around 64 built-in filter presets which can be extended even more!) 🎸
- Lavalink compatible 15 band equalizer 🎚️
- Digital biquad filters support
- Digital Signal Processing utilities
- Lightweight ☁️
- Custom extractors support 🌌
- Multiple sources support ✌
- Play in multiple servers at the same time 🚗
- Does not inject anything to discord.js or your discord.js client 💉
- Allows you to have full control over what is going to be streamed 👑
Getting Started
First of all, you will need to register slash commands:
const { REST } = require('@discordjs/rest');
const { Routes, ApplicationCommandOptionType } = require('discord.js');
const commands = [
{
name: 'play',
description: 'Plays a song!',
options: [
{
name: 'query',
type: ApplicationCommandOptionType.String,
description: 'The song you want to play',
required: true
}
]
}
];
const rest = new REST({ version: '10' }).setToken('BOT_TOKEN');
(async () => {
try {
console.log('Started refreshing application [/] commands.');
await rest.put(Routes.applicationGuildCommands(CLIENT_ID, GUILD_ID), { body: commands });
console.log('Successfully reloaded application [/] commands.');
} catch (error) {
console.error(error);
}
})();
Now you can implement your bot's logic:
const { Client } = require('discord.js');
const client = new Discord.Client({
intents: ['Guilds', 'GuildVoiceStates']
});
const { Player } = require('discord-player');
const player = new Player(client);
player.events.on('playerStart', (queue, track) => queue.metadata.channel.send(`🎶 | Now playing **${track.title}**!`));
player.events.on('playerFinish', (queue, track) => queue.metadata.channel.send(`🎶 | Now playing **${track.title}**!`));
client.once('ready', () => {
console.log("I'm ready !");
});
client.on('interactionCreate', async (interaction) => {
if (!interaction.isChatInputCommand()) return;
if (interaction.commandName === 'play') {
const voiceChannel = interaction.member.voice.channelId;
if (!voiceChannel) return await interaction.reply({ content: 'You are not in a voice channel!', ephemeral: true });
if (interaction.guild.members.me.voice.channelId && voiceChannel !== interaction.guild.members.me.voice.channelId)
return await interaction.reply({ content: 'You are not in my voice channel!', ephemeral: true });
await interaction.deferReply({ ephemeral: true });
const query = interaction.options.getString('query');
try {
const res = await player.play(voiceChannel, query, {
nodeOptions: {
metadata: {
channel: interaction.channel
}
}
});
return await interaction.followUp({ content: `⏱️ | Loading track **${res.track.title}**!` });
} catch(e) {
return await interaction.followUp({ content: `Could not play: ${e.message}`, ephemeral: true });
}
}
});
client.login('BOT_TOKEN');
Accessing player instance
Polluting client like this could be a bad idea:
client.player = player;
discord-player provides singleton support to avoid this type of pollution:
- const player = new Player(client);
+ const player = Player.singleton(client);
Player.singleton()
creates a single instance of player which is shared in the future. You can simply do Player.singleton()
to access player instance whenever
you want without polluting client.
Supported sources
By default, discord-player does not support anything (including search operation and streaming). Luckily, discord-player supports the following sources with the help of @discord-player/extractor which comes pre-installed with discord-player:
- Local file (You must set the search engine to
QueryType.FILE
in order to play local files, backed by attachment extractor
) - Raw attachments (backed by
attachment extractor
) - Spotify (backed by
ysa extractor
) - Apple Music (backed by
ysa extractor
) - YouTube (backed by
ysa extractor
) - Vimeo (backed by
vimeo extractor
) - Reverbnation (backed by
reverbnation extractor
) - SoundCloud (backed by
soundcloud extractor
)
If you dont want to stream from certain extractors, you can block them by passing blockStreamFrom: [id, id, ...]
to player instantiation options.
Disabling youtube streaming completely would be as easy as:
import { Player } from 'discord-player';
import { YouTubeExtractor } from '@discord-player/extractor';
const player = new Player(client, {
blockStreamFrom: [
YouTubeExtractor.identifier
],
blockExtractors: [
YouTubeExtractor.identifier
]
});
Likewise, You can also force a specific extractor to resolve your search query. This is useful in some cases where you don't want to use other sources.
You can do so by using ext:<EXTRACTOR_IDENTIFIER>
in searchEngine
value. Example:
import { SoundCloudExtractor } from '@discord-player/extractor';
const result = await player.search(query, {
searchEngine: SoundCloudExtractor.identifier
});
Adding more sources
Discord Player provides an Extractor API that enables you to use your custom stream extractor with it. Some packages have been made by the community to add new features using this API.
Audio Filters
Discord Player supports various audio filters. There are 4 types of audio filters in discord-player.
FFmpeg
The most common and powerful method is FFmpeg. It supports a lot of audio filters. To set ffmpeg filter, you can do:
await queue.filters.ffmpeg.toggle(['bassboost', 'nightcore']);
Note that there can be a delay between filters transition in this method.
Equalizer
This equalizer is very similar to Lavalink's 15 Band Equalizer. To use this, you can do:
queue.filters.equalizer.setEQ([
{ band: 0, gain: 0.25 },
{ band: 1, gain: 0.25 },
{ band: 2, gain: 0.25 }
]);
There is no delay between filter transition when using equalizer.
Biquad
This filter provides digital biquad filterer to the player. To use this, you can do:
import { BiquadFilterType } from 'discord-player';
queue.filters.biquad.setFilter(BiquadFilterType.LowPass);
There is no delay between filter transition when using biquad filters.
Mini Audio Filters
This is another type of audio filters provider. It currently supports Tremolo
and 8D
filters only. To use this, you can do:
queue.filters.filters.setFilters(['8D']);
There is no delay between filters transition using this filter.
Example bots made with Discord Player
These bots are made by the community, they can help you build your own!
Use youtube cookies
Using youtube cookies helps you to prevent frequent ratelimits.
const player = new Player(client, {
ytdlOptions: {
requestOptions: {
headers: {
cookie: 'YOUR_YOUTUBE_COOKIE'
}
}
}
});
Note: The above option is also passed to ytdl-core
but not play-dl
. Follow this instruction for play-dl config.
Use custom proxies
const HttpsProxyAgent = require('https-proxy-agent');
const proxy = 'http://user:pass@111.111.111.111:8080';
const agent = HttpsProxyAgent(proxy);
const player = new Player(client, {
ytdlOptions: {
requestOptions: { agent }
}
});
You may also create a simple proxy server and forward requests through it.
See https://github.com/http-party/node-http-proxy for more info.
Stream Hooks
onBeforeCreateStream
Discord Player by default uses registered extractors to stream audio. If you need to override what needs to be streamed, you can use this hook.
const fs = require('fs');
const queue = player.nodes.create(..., {
...,
async onBeforeCreateStream(track, source, _queue) {
if (track.title === 'some title') {
return fs.createReadStream('./playThisInstead.mp3');
}
}
});
<GuildQueue>.onBeforeCreateStream
is called before actually downloading the stream. It is a different concept from extractors, where you are just downloading
streams. source
here will be a track source. Streams from onBeforeCreateStream
are then piped to FFmpeg
and sent to onAfterCreateStream
hook.
onAfterCreateStream
This hook can be used to post-process pcm stream. This is the final step before creating audio resource. Example:
const queue = player.nodes.create(..., {
...,
async onAfterCreateStream(pcmStream, queue) {
const encoder = new OpusEncoder();
return {
stream: encoder.encode(pcmStream),
type: StreamType.Opus
};
}
});