Instead, I start a game of chess by correspondence against Xray.
Check out my last three canceled games.
I can not create a game for Togyz Kumalak by correspondence.
Hi Pokshtya,
Thanks for raising this issue. Unfortunately, I'm unable to replicate it. Could you please describe how you attempt to create the correspondence Togyz Kumalak game in more detail so that we can fix the potential issue. For example is this game created in the lobby (create a game), play with friend form, or via the challenge button?
Started from here
playstrategy.org/
Create a game >>>
Variant : Togyzkumalak
Time control : Correspondence
Days per turn: 3
Casual
Rating range - 1000 / + 1000
We have replicated this and again it seems to work
When you create the game, does it appear in the lobby/correspondence page as a Togyzkumalak game or a chess game?
If I set 'Casual' then I can create Togyzkumalak game but if I set 'Rated' then chess game against Xray appears 0_0
You can see I created an unrated Togyzkumalak game in the Lobby, but as soon as I select the Rated option, a chess game opens against Xray. That's weird.
lol now it works. I just changed the time limit from 3 days to 5.
This is unfortunately still going on, I think.
Last night I tried to post a correspondence challenge for Russian Checkers set to two days per move. What happened instead was that it instead automatically matched me up to a challenge already posted by queen-of-blunders for Lines of Action that just so happened to also have a two day per move limit. It wasn't quite what I was looking for, but both games do use 12 checkers per side.
On that note, I had earlier (2 or 3 days ago? I forget) joined a game Pokshtya posted for rated Togyz, but the game commenced as unrated. Again, I love the game either way, but it's not what I expected.
Thanks for raising this again, it does sound like a bug!
When you post a game, there is some code that looks for 'similar' games to match before posting the game and perhaps this is not working as expected.
We will investigate gain, with this helpful extra information
@Pokshtya @Evernia we have deployed a fix for this today. Thank you for raising this at the time :)