This repository has been archived by the owner on Nov 13, 2022. It is now read-only.
Mixed players from different instances #179
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My problem was that I've had two different instances of erela.js running but somehow player-managers shared players of two different bots. (In the same guild) and when I asked bot A to connect, bot B which was already connected took the request.
I don't know how to prevent player sharing, but I fixed the problem of request handling, now it won't be able to take a player from the wrong player-manager.
I know that isn't maybe beautiful but It works and does the job
If someone knew how to fix the problem of shared players from 2 different managers/bots, it would be more helpful than that temporary fix