It’s really very annoying, and adversely impacting.
There are at least 4.
Contrary to the implication, they are not doing “nothing”.
The tournament code is Big. This means you can’t readily just go in and find an isolated bug and fix it - you have to spend time to get your head around “everything”.
Right now back end developers are in the middle of other Big things.
… we haven’t even had a chance to fix up “rank filters not working”, which I reckon is ahead of this.
Of course, it’d be great to have another backend developer. Someone who would not be scared of anything. The path to that is “front end contributions” to establish the working relationships.
How are we going with “voice-over-chat” prototype?
Sometimes I notice it in new automatch finder. But is not very important for me.
Does this issue is really causes more inconvenience to users?
May I argue that live tournament glitches are more annoying for people. You sign up for a live tournament. It is a continuous sequence of games. You cannot cancel a particular game. If something goes wrong like BUG: zombies after timeout tournament didn't lose games you cannot even quit. Even after timeout you a forced to another game.
In case of double simultaneous games if you are playing the wrong one you automatically get disqualified from the tournament by disconnection.
I believe that glitch in rank filters may cause some discomfort. But is it really big? If opponent rank is very important for you it is possible to cancel the game and restart search. If the filter was very narrow and you just want to play it may be even a possibility to find a good game faster. Is it really bad?
It was a feature suggestion. I do not offer to implement it myself. I am the end user here. An ordinary go player. I just want to rest and play go. I’m sorry. I cannot be architect or even simple coder everywhere.
Please do not prioritize my suggestion about extending chat content because it is easy to implement.
I think bugs such as filters and tournaments glitches are more important.
Please prioritize the broken stuff first. I think there is no point in starting to develop something new until the old one is unmaintainable. Especially when there are not enough human resources for development.
And please do not touch things that works perfectly while there is already something to fix.
I can be wrong. I sure I have a right to be wrong. I’m am an ordinary human.
I mentioned voice over chat because it sounded like you might have been interested in implementing that: you were certainly suggesting lots of implementation plans and considerations.
Not because we would prioritise it though It’s a nice front-end exercise.
It’s a bit of a question which needs attention first - for the smaller population of tournament users, for sure this is worse.
For the larger group of auto-match users, getting wrongly matched is probably worse.
A person stepped up and started work on it, but was unable to complete it within their own constraints (time, interest, whatever).
Moderation became a worse challenge, and deflected my own efforts in that direction instead.
We’re not quite back to “a manageable situation” yet, though things are greatly improved.
Under-the-hood emergencies happened, like mandatory updates to the payments systems inflicted on us by payment providers. Those have been anoek’s priority.
