It’s usual that the players on the same team don’t communicate in pair go right? Would it be expected that in team go the players would or wouldn’t communicate - maybe that can just be a setting? A shared demo board would be cool or some way of pinning it as yebellz said.
If it’s the case where you don’t communicate moves, should it show who’s to play next to all players or just say Team A/Team B? There’s the idea of a Pair Go tesuji, where you play a ko threat to avoid the stronger player making a move, or similarly to give the stronger player the choice or the next big move. This would be be easier to do I’d say if you could see whose turn was next. (It would be nice if spectators could see whos turn it was though for live games)
Would there be an extra rating for this team/rengo to play it ranked or would it somehow merge into the current ratings like with 9x9, 13x13 etc.
Not having Rengo and other trivial Go variants is probably the most disappointing aspect of OGS. I just can’t understand how the guys developing this server made such a nice work with AI analysis but can’t go ahead with even an extremely simple Go variant, like Rengo or One Color Go.
At this point, I wonder, how much money or other type of incentive would it take for the devs to get motivated?
Rengo is conceptually simple. But when everything on the backend is written for a game between two players, it gets harder. I think @anoek once estimated that coding rengo would take about 100 hours, plus bug fixing. That number has probably increased as new features have been added. That’s not to say rengo won’t happen; it’s only to show the scope of the request.
But when everything on the backend is written for a game between two players, it gets harder.
I agree completely. And I actually think this problem is more general than Rengo. I believe that, given the size of OGS at this moment, anything that slightly diverges from its main features will take a very big — absolute but not relative — amount of time to implement, even though they might be trivial to implement in a project from scratch. I guess this is just the nature of handling a project that became big.
But, on the other hand, I think it’s one of the features that would make the most difference for its user base… And I think that implementing Rengo would ease the path towards implementing other Go variants too, so these 100 hours might reduce other implementations to, say, 20 hours — I know… of course the devs know about this type of stuff…
And how about starting with One Color Go, which is just cosmetic, to see if the impact is worth the shot on other more complicated variants?
I think OGS is quite friendly to new people, Rengo should be priority. It’s such a important Go Variation and that much common, it’s a shame not having it. Also Rengo is super, to train your Go skills. You can combine different styles of playing and also different levels of knowledge.
It is a good lecture for the weaker player, to see the good moves from the better one and it’s also a lecture for the better player, who got to think, which plans can my partner understand.