MIA
🎶 Moonlink.js - Imagine a Music Application
Join the 🎶 Moonlink.js - Imagine a Music Application server to ask questions!
JoinMIA
🎶 Moonlink.js - Imagine a Music Application
Join the community to ask questions about 🎶 Moonlink.js - Imagine a Music Application and get answers from other members.
Join[Closed]: ip nodelink (obs: opened in wrong posting channel)
How do I connect ips?
In nodelink
For each, for example, 100 bots...
Can I add my application to applications_using_moonlink.md?
This is my bot: HStudio
Description A music bot for your Discord server. Play your favorite songs from YouTube or Spotify, and it supports multiple languages.
Invite Invite Link
Repository Github...
Type of player.current should be MoonlinkTrack
Unless there is some design decision I do not know as to why it is set to
Record<string, any>More events
I need an event that is triggered when settings change like, when loop mode changes, when the player is paused etc.
Is that doable @1Lucas1.apk?...
Add Crypto to #sponsor
Add Crypto to #sponsor to allow users that dont have a credit card to still support the project
Modify player.queue.add() method to give more functionality
Hey, I love that this library has a queue functionality built in. I wanted to suggest a potential optional variable to the
player.queue.add() method that could make it a lot better.
Simply adding an optional position: number variable would allow adding tracks to the top of the queue, to the middle of the queue, to any part of the queue as to the developer's discretion. In the end, the method would look like add(data: MoonlinkTrack, position?: number): void;. If there is no position specified, just add it to the back of the queue like we currently have it. If the position specified is out of bounds of the queue size, just add it like normal as if the variable wasn't specified.
Another addition could be making it so that data could be either MoonlinkTrack | MoonlinkTrack[] meaning a developer can add multiple tracks at once without having to write their own script that re-runs the add method. It's not really that important but could be nice to have. And please do correct me if this functionality already exists....Add event for playerCreation
Hello, I would kindly appreciate an implementation of an event called playerCreate, which gets emitted everytime a player gets created.
It takes MoonlinkPlayer as an argument...
Rename all the events to its proper functionality
I would like to recommend the renaming of some events...
- debug: Emits debug messages for debugging purposes. Takes any number of arguments.
- nodeClose: Fired when a connection to a Lavalink node is closed. Takes the node object, code, and reason as arguments.
- nodeCreate: Fired when a connection to a Lavalink node is successfully created. Takes the node object as an argument....
Remove playerResume event
There is really NO need for this event. The player gets resumed / paused by userInput etc. NO NEED TO HAVE THIS EVENT IN THE FIRST PLACE
Allow player.destroy() to take a boolean as parameter
Hello, I would love to have the option to call something like this:
player.destroy(false) and have the player destroyed, but the bot does not disconnect from the voice channel..
To achieve that I modified the destroy() method in the "MoonlinkPlayers.ts" file to this exact one here:
```js
public async destroy(disconnect: boolean = true): Promise<boolean> {...Adjust player type in MoonlinkManager
Hey there, I'm taking a look at the new typescript changes. They're pretty decent so far, good enough for what I need. However, the property
players under MoonlinkManager is just listed as type object which means it's missing all of its Map properties as well as the create property.
I suggest you change its type from get players(): object to get players(): Map<string, MoonlinkPlayer> & { create(data: any) }; This should allow it to pick up on Map properties as well as the custom create function. I would recommend specifying what data looks like overall in the project so we don't get errors of wrong data types inputted but overall I think this should be fine as a bandaid fix.
Additionally, it would be nice to use the types from the discord-api-types library (https://github.com/discordjs/discord-api-types) for types such as VoiceServer and VoiceState rather than creating custom ones but that's just an extra suggestion. I'm suggesting this because it's the most widely used library for typings in discord....I have a question
Is this package useful for detritus-client (it also interacts with discord)? Because there are several packages that don't work for me