Parallel Fractional Go Game 6

Round 9

Game link

2 Likes

Reminder @Tschej

1 Like

Round 10

Game link

2 Likes

Reminder @Sadaharu

Round 11

@Jon_Ko black_magenta and @PRHG brown2_transparent collide at C10 and the stone is immediately captured.

Game link

4 Likes

So if @Jon_Ko keeps playing C10, which threatens to capture C11, and @PRHG keeps playing C10 to prevent capture, then the two are cancelling each others moves.

3 Likes

Reminder @Tschej

Round 12

4 Likes

@garlicsoup I believe that connecting the white groups at the top is important, and I am happy that we get the chance to do so. Shall we coordinate our moves to prevent that we collide?

1 Like

I’ll play H2.

1 Like

Thank you, then I will play somewhere else.

1 Like

Round 13

Game link

This time I’m not 100% sure what happened :sweat_smile: Though it seems plausible that @Jon_Ko black_magenta and @PRHG brown2_transparent played at C10 again. This implies that @Tschej brown1_transparent played at D5, which results in the capture of the brown chain. @JohnnieDarko white_green could have played C10 or D5 (though D5 seems more plausible to me).

2 Likes

I indeed played D5 and captured Tschej’s E5.

I don’t understand why my D5 stone is gone though, it is fully connected to my D6 stone so it couldn’t be captured. Well obviously it could, but not in my understanding of the rules :sweat_smile:

2 Likes

Tschej played D5, so the D5 stone would have been red, green, black and white. This means D5 would have been part of the red group comprised of D5 and E5. This red group had no liberties, and was thus removed from the board. At least this is my best explanation.

I think it doesn’t matter if your stone is part of a group that wouldn’t be captured, as long as it’s part of a group that does get captured then it gets captured.

3 Likes

Thanks! lightbulb moment here.

I expected that first my D5 would capture E5, (because captures are resolved first in go), and then Tschej’s D5 would combine with mine to form that four color stone.

But the order of things is then: stones are placed at the same time, and then captures are resolved. (I think).

3 Likes

Can confirm this, and your explanation is sound.

Your interpretation of normal go rules is interesting to me - the idea that captures are resolved first and then the stone is placed.
I’ve always thought of it in this order - first stone placement, then resolve captures of opponents stones, then check for self capture.

Yes, you can think of it as three steps:

1.) stones are placed at the same time
2.) old chains without liberties are removed
3.) new chains without liberties are removed

… where chains are called “new” if they contain a stone placed this round, otherwise “old”.

So if the stone placed at D5 was only white-green, then the capture would have occurred as you expect.

We can take black-greens capture at D9 as another example. After placing the stone, the black chain has no liberties, but since E9 is an old chain that gets removed in step 2., D9 survives.
This is where it works intuitively, in my opinion. Needless to say, there are many unintuitive examples as well :sweat_smile:

I believe the whole idea goes back to Diplomatic Go

Note that this mechanism is compatible with normal go rules - here all opponents chains are “old”, and self capture can only occur for the chain containing the newly placed stone, i.e. a “new” chain.

4 Likes

“Interesting” :smile: Yeah it’s a lazy shortcut of the rules, your reading makes more sense.

This clears it up. I read this before but forgot about it.

1 Like

I think it would be interesting to have something analogous to ko, where if two or more players play a single stone on the same space, and that one stone dies, but no other stones are captured because of it, then those players cannot play on that same space next turn.

3 Likes

@PRHG do you want to break the stalemate on D10? I can start removing liberties from @Jon_Ko s stone.

1 Like

Yeah sure, if you don’t feel the immediate need to play elsewhere

1 Like