Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- ## Custom commands
- >>nosound
- - **If the bot's speaking light is active, but there is no sound, try these:**
- ```md
- 1. Is the bot's user volume turned up? (right click on the bot in discord, see the slider)
- 2. Is the bot muted or deafened? Are you deafened? Are you deaf?
- 3. Check Discord audio device settings and volume (cog icon next to your username in the bottom left, click "Voice and Video")
- 4. Check system audio device settings and volume
- 5. Ask another member to come into the voice channel to confirm that it's not just you
- ```- **If the track progress is stuck on 00:00 when you run `[p]now`:**```md
- 1. Try to run [p]disconnect and replay the song
- 2. Try to reload the audio cog with [p]reload audio
- 3. Try to restart your bot with [p]restart
- 4. Try to restart your host machine
- ```- **If all else fails copy the contents of your spring.log/lavalink.log file; post it on gist, pastebin, hastebin, etc** and send the link in <#387398816317440000>:```md
- - It can be found in: <datapath>/cogs/Audio/logs/
- -- Use [p]datapath to find out what your <datapath>
- ```
- >audiolag
- - **Laggy audio is most likely a problem with the connection between the host machine of your bot to the discord server** (or discord is wonking out)**, try these**:
- ```md
- 1. Wait
- 2. Try restarting your bot
- 3. Check to make sure it's not just a bad quality song (try a different song)
- 4. Try a different server region
- 5. Try hosting your bot elsewhere
- 6. If not everyone is experiencing the issue, it's a discord client issue.
- ```
- There is a known issue with the desktop discord client causing audio playback issues. If you listen from the discord web browser you should hear significant quality improvements.
- >ll
- The logs from Lavalink may be useful here:
- - **If all else fails copy the contents of your spring.log/lavalink.log file; post it on gist, pastebin, hastebin, etc** *and send the link here*
- ```md
- - They can be found in: <datapath>/cogs/Audio/logs/
- - Use [p]datapath to find out what your <datapath>
- ```
- >lldownload
- - **To manually download the jar:**
- ```md
- 1. Stop your bot
- 2. Go to https://github.com/Cog-Creators/Lavalink-Jars/releases/tag/3.2.1_823
- 3. Download the Lavalink.jar file
- ```- **If you are not running an external instance of Lavalink**:```md
- 1. Stop your bot by running [p]shutdown
- 2. Move Lavalink.jar to your <datapath> /cogs/Audio/ folder
- 3. Start your bot
- -- Use [p]datapath to find out what your <datapath>
- ```- ** If you are running an external instance of Lavalink:**```md
- 1. Stop all instances of Red running on host.
- 2. Stop the Lavalink process
- 3. Move Lavalink.jar to where your old Lavalink.jar is located
- 4. Start up the new Lavalink.jar with "java -jar Lavalink.jar"
- 5. Start up your bots
- ```
- >localtracks
- - **Red 3.2**
- ```md
- 1. Create a "localtracks" folder anywhere where Lavalink has permissions to access
- 2. Create/move/copy/symblink your album folders (Sub folders containing your tracks) to the folder created in step 1
- 3. Put ogg, mp3, or flac files in those folders:
- -- localtracks/<parent folder>/song.mp3
- -- localtracks/<parent folder>/<child folder>/song.mp3
- - Use [p]local commands and interact with the menu reactions to play songs
- - Use [p]play <parent folder>/song.mp3 for single songs
- - Use [p]local folder <parent folder>/<child folder> to play the whole folder
- -- Use [p]datapath to find out what your <datapath>
- Note: /* Localtracks needs to be on the same machine as your bot AND the Lavalink.jar*
- ```
- >multibots
- - **You will need to run an enternal instance of Lavalink**
- ```md
- 1. Stop all Red bots
- a) Start Bot 1
- b) Run command [p]llset external
- c) Stop Bot 1
- -- Repeat step 1.a through to 1.c for each additional bot
- 2. Open a command prompt/terminal window
- 3. Navigate to <datapath>/cogs/Audio (doesn't matter which bot as all your bots will now use this single instance of lavalink)
- 4. Run command "java -jar Lavalink.jar"
- 5. Leave this window open (you will need to do this every time you want to start Lavalink for your bots)
- 6. Once Lavalink says it has fully started, you can start your bots back up
- -- Use [p]datapath to find out what your <datapath>
- ```
- >redautorestart
- https://docs.discord.red/en/stable/autostart_systemd.html
- >llautorestart
- - **Lavalink** - *For external instances **only***
- Run *`sudo -e /etc/systemd/system/lavalink.service`* and put the following inside of it.
- ```md
- [Unit]
- Description=lavalink
- After=multi-user.target
- [Service]
- ExecStart= < Jar executable path > -jar < Lavalink path >/Lavalink.jar
- User=< username >
- Group=< username >
- Type=idle
- Restart=always
- RestartSec=15
- [Install]
- WantedBy=multi-user.target
- ```**Variables**```md
- < Jar executable path > -- You can find your Java path by running "which java"
- < Lavalink path > -- Parent folder where your Lavalink executable can be located (usually in <datapath>/cogs/Audio)
- < username > -- Username on host machine, often the output of: 'echo "$USER"'
- -- Use [p]datapath to find out what your <datapath>
- ```
- **Run the following:**
- - *`sudo systemctl start lavalink`* - This will start the service
- - *`sudo systemctl enable lavalink`* - This will allow the service to auto start after a reboot
- - *`sudo journalctl -u lavalink`* - This will allow you to read the logs for the service
- >spotify
- Audio V3+ supports playing spotify tracks by using the **YouTube Data API** and **Spotify API** and will be required to obtain authentication for those services if you wish to use this feature.
- **Please note the following:**
- `The following is not permitted for any reason whatsoever: copying, redistributing, reproducing, “ripping”, recording, transferring, performing or displaying to the public, broadcasting, or making available to the public any part of the Spotify Service or the Content... [and] “crawling” the Spotify Service or otherwise using any automated means (including bots, scrapers, and spiders) to collect information from Spotify`
- <https://www.spotify.com/us/legal/end-user-agreement/>
- **As such we will never support direct play from Spotify**.
- >audiocache
- **Red 3.2 support a local cache**, these allows you to reduce repeated API calls to the YouTube Data and Lavalink APIs.
- ```md
- 1. [p]audioset cache < level >
- - Will set the active cacheing
- - Run [p]help audioset cache to see what the supported values are.
- 2. [p]audioset cacheage < age in days >
- - Will tell the bot how many days a cache entry is valid for
- - If an entry is invalid, then the bot will call the API next time this track is requested.
- ```
- >playlists
- **Red 3.2 supports multiple types of playlists**, they are as follows:
- ```md
- < Global Playlist >
- - These playlists will be available in all servers the bot is in.
- - These can be managed by the Bot Owner only.
- < Server Playlist >
- - These playlists will only be available in the server they were created in.
- - These can be managed by the Bot Owner, Guild Owner, Mods, Admins, DJs and creator (if DJ role is disabled).
- < User Playlist >
- - These playlists will be available in all servers both the bot and the creator are in
- - These can be managed by the Bot Owner and Creator only
- ```**Argument Parsing**
- *Due to the complexity added by these, we had to implement an new format of arguments for all commands that touch bot playlists.*```md
- < New command format >
- - [p]playlist start playlist_name_OR_id [args]
- - Args are optional and if not used it will default to < Server Playlist > (same behaviour pre-3.2), they are the following:
- 1. --scope <scope>
- 2. --author [user]
- 3. --guild [guild]
- - <scope> can be one of following:
- 1. Global - to access < Global Playlist >
- 2. Server - to access < Server Playlist >
- 3. User - to access < User Playlist >
- - [user] can be the following:
- 1. User ID
- - [guild] can be the following:
- 1. Guild ID
- 2. Exact guild name
- ```**Usage**```md
- 1. [p]playlist start <playlist_name_OR_id> --scope Global
- - Will start a < Global Playlist >
- 2. [p]playlist start <playlist_name_OR_id> --scope Server --guild 133049272517001216
- - Will start a < Server Playlist > that exists in server 133049272517001216
- 3. [p]playlist start <playlist_name_OR_id> --scope User --author 208903205982044161
- - Will start a < User Playlist > that eas created by 208903205982044161
- 4. [p]playlist list --scope Server --guild 133049272517001216 --author 208903205982044161
- - Will list all < Server Playlist > created by user 208903205982044161 in server 133049272517001216
- ```
Advertisement
Add Comment
Please, Sign In to add comment