- Blind mode tutorial
lichess.org
Donate

Can't create game with specific side any more

@BeDecentForAChange said in #372:

Nope, intentional

The code brings the wrong players together. Oh, damn.

@BeDecentForAChange said in #372: > Nope, intentional The code brings the wrong players together. Oh, damn.

@Sofia-Mary said in #373:

The code brings the wrong players together. Oh, damn.

No, players were just using it wrong. Which is fixed now. owwwww

@Sofia-Mary said in #373: > The code brings the wrong players together. Oh, damn. No, players were just using it wrong. Which is fixed now. owwwww

Crazy, using the Smartphone App I still have the choice to choose the color. That makes no sense. Mistake or intentionally?

Crazy, using the Smartphone App I still have the choice to choose the color. That makes no sense. Mistake or intentionally?

@Schiffskoch said in #375:

Crazy, using the Smartphone App I still have the choice to choose the color. That makes no sense. Mistake or intentionally?

Yes, it's still available against bots/AI and inviting people

@Schiffskoch said in #375: > Crazy, using the Smartphone App I still have the choice to choose the color. That makes no sense. Mistake or intentionally? Yes, it's still available against bots/AI and inviting people

@BeDecentForAChange said in #374:

No, players were just using it wrong. Which is fixed now. owwwww

No, the code is wrong and the white players have been created to abusive persons to hide the wrong code.
Would the code be able to connect the right people, all would be fine. Everybody could play excessive white or black.

Ahhhh, and this is the only reason, why also the casual games are blocked for colour choosings, not to educate the peoples wrong behaviour, they could show in all possible games.

@BeDecentForAChange said in #374: > No, players were just using it wrong. Which is fixed now. owwwww No, the code is wrong and the white players have been created to abusive persons to hide the wrong code. Would the code be able to connect the right people, all would be fine. Everybody could play excessive white or black. Ahhhh, and this is the only reason, why also the casual games are blocked for colour choosings, not to educate the peoples wrong behaviour, they could show in all possible games.

@Sofia-Mary said in #377:

No, the code is wrong and the white players have been created to abusive persons to hide the wrong code.
Would the code be able to connect the right people, all would be fine. Everybody could play excessive white or black.

Nope, the code works as expected. That doesn't mean it does what you mean, it does what Lichess intends it do it. Works perfectly

Ahhhh, and this is the only reason, why also the casual games are blocked for colour choosings, not to educate the peoples wrong behaviour, they could show in all possible games.

The reason is stated in the commit message, it is because people abuse it to play white exclusively

@Sofia-Mary said in #377: > No, the code is wrong and the white players have been created to abusive persons to hide the wrong code. > Would the code be able to connect the right people, all would be fine. Everybody could play excessive white or black. Nope, the code works as expected. That doesn't mean it does what you mean, it does what Lichess intends it do it. Works perfectly > > Ahhhh, and this is the only reason, why also the casual games are blocked for colour choosings, not to educate the peoples wrong behaviour, they could show in all possible games. The reason is stated in the commit message, it is because people abuse it to play white exclusively

ok, you are refering to the "quick" pairings. I never use that but the Lobby pairings.

But the solution would be quite simple: you should not get paired against players who have want to have white (or black).
I think most players have random selected, so you are still left with a big player pool.
The Lobby-seeks can only be paired with quick-seeks if they have the same time control and a random colour. Which I am not even sure if lichess had done so in the past.

To be honest that is certainly not a lot of code to do. All the code is already there, it would be just one more case comand.
there are already "if" questions (if same time control, if within rating range, and one new case: "if random colour").
Or, keep the lobby and the quick pairings seperate. If you look into the lobby-seeks, most time controlls are different to the quick pairing, so I doubt there is much overlapping.

This isnt rocket science, and the cost is certainly not the same like the chess variant for horde chess, or the code involved for creating an own tournament.

ok, you are refering to the "quick" pairings. I never use that but the Lobby pairings. But the solution would be quite simple: you should not get paired against players who have want to have white (or black). I think most players have random selected, so you are still left with a big player pool. The Lobby-seeks can only be paired with quick-seeks if they have the same time control and a random colour. Which I am not even sure if lichess had done so in the past. To be honest that is certainly not a lot of code to do. All the code is already there, it would be just one more case comand. there are already "if" questions (if same time control, if within rating range, and one new case: "if random colour"). Or, keep the lobby and the quick pairings seperate. If you look into the lobby-seeks, most time controlls are different to the quick pairing, so I doubt there is much overlapping. This isnt rocket science, and the cost is certainly not the same like the chess variant for horde chess, or the code involved for creating an own tournament.

@BeDecentForAChange said in #378:

The reason is stated in the commit message, it is because people abuse it to play white exclusively

I do not care. Because of your code info the real reason comes out. Thank you.

@BeDecentForAChange said in #378: > The reason is stated in the commit message, it is because people abuse it to play white exclusively I do not care. Because of your code info the real reason comes out. Thank you.

@Munich said in #379:

ok, you are refering to the "quick" pairings. I never use that but the Lobby pairings.

But the solution would be quite simple: you should not get paired against players who have want to have white (or black).
I think most players have random selected, so you are still left with a big player pool.
The Lobby-seeks can only be paired with quick-seeks if they have the same time control and a random colour. Which I am not even sure if lichess had done so in the past.

Wrong, quick seeks are added to the lobby. And you are suggesting that they build a new lobby for color seekers?

To be honest that is certainly not a lot of code to do. All the code is already there, it would be just one more case comand.

You can make that PR! I would be impressed if you could do that within one case command, but please share the branch in which you do this

there are already "if" questions (if same time control, if within rating range, and one new case: "if random colour").
Or, keep the lobby and the quick pairings seperate. If you look into the lobby-seeks, most time controlls are different to the quick pairing, so I doubt there is much overlapping.

This isnt rocket science, and the cost is certainly not the same like the chess variant for horde chess, or the code involved for creating an own tournament.

@Munich said in #379: > ok, you are refering to the "quick" pairings. I never use that but the Lobby pairings. > > But the solution would be quite simple: you should not get paired against players who have want to have white (or black). > I think most players have random selected, so you are still left with a big player pool. > The Lobby-seeks can only be paired with quick-seeks if they have the same time control and a random colour. Which I am not even sure if lichess had done so in the past. Wrong, quick seeks are added to the lobby. And you are suggesting that they build a new lobby for color seekers? > > To be honest that is certainly not a lot of code to do. All the code is already there, it would be just one more case comand. You can make that PR! I would be impressed if you could do that within one case command, but please share the branch in which you do this > there are already "if" questions (if same time control, if within rating range, and one new case: "if random colour"). > Or, keep the lobby and the quick pairings seperate. If you look into the lobby-seeks, most time controlls are different to the quick pairing, so I doubt there is much overlapping. > > This isnt rocket science, and the cost is certainly not the same like the chess variant for horde chess, or the code involved for creating an own tournament.

@Sofia-Mary said in #380:

I do not care. Because of your code info the real reason comes out. Thank you.

Of course:) It's to stop abusers, which has now been achieved. Again, the code does what it should :)

@Sofia-Mary said in #380: > I do not care. Because of your code info the real reason comes out. Thank you. Of course:) It's to stop abusers, which has now been achieved. Again, the code does what it should :)

This topic has been archived and can no longer be replied to.