-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Master change #68
Comments
If the Master of a room leave, the player who get it is the one who enter earliest after room creation. It doesn't matter the slot in the room. |
It has always been like that. When the master leaves the room the next master will be the closest to the slot 2. |
At the moment it's that way implemented that the first found player in the room will get the master status, if master leaves👍 Getting this like original FT I think is useless and not minor, as it's s not effecting the gameplay or the way how FT is played. But if enough players want that original functionality we can do it, but as I said not necessery :) |
Actually, the original behavior was not that useless. If you were playing in a team, you could control that your partner becomes the room master when you needed to rejoin a room (e.g. going shopping or checking the lobby) |
Totally agreed. I believe it's not prioritary with the current state of the game but still it is worth to be fixed the correct way. |
Ah, I see, well then we gonna change that! :) |
Did we change that or do we have here still the old behaviour? 🤔 |
Still like Milov described. |
Just a very small minor bug I noticed. If the Master leaves and is not on slot 2 the player positioned in slot 2 should get Master (that's how it used to be in old FT iirc), when the Master is positioned in slot 2 then slot 3 should get Master. If there is nobody on slot 3 then slot 1 gets Master. If nobody is in slot 1 then slot 4 gets Master.
Currently if the Master leaves, slot 3 will get Priority in getting Master, after that comes slot 4, then slot 1 and finally slot 2.
The text was updated successfully, but these errors were encountered: