but just think about it...

area scoring == (number of stones on the board) + (territory)
where (number of stones on the board) = (number of turns) - (prisoners (that were thrown back in the bowl))

territory scoring == (territory) - (prisoners)
where (prisoners) = (number of turns) - (number of stones on the board)

same thing.
so prisoners count. always.

I didn't mean that in the sense that there's no benefit to taking prisoners, I just meant that there's no reason to keep track of them or count them when you're counting all the stones on the board.

_________________
Thinking like a go player during a game of chess is like bringing a knife to a gun-fight. Thinking like a chess player during a game of go feels like getting knifed while you're holding a gun...

And if the pitcher manages to hit the batter, forcing him to first base, the runner will then try to steal his way home, in order to avoid the negative point. If he gets thrown out along the way, that also avoids the negative point, so he does not have to try very hard

Fascinating. I've been trying to use area-based half-counting to see if I have a way to 181 (adjust as necessary for komi) when I'm trying to figure out how far ahead or behind I am, with mixed success.

Last night I had White with 6.5 komi and figured I had to get to 178, as I was trying to count and take dame into account, it looked like I was only going to get to 177. Imagine my pleasant surprise when the server said that I won by 1.5.

Counting the stones on the board, I find there tend to be more rectangles that make counting easier: 3x6, 4x4, 2x10, or what have you. When there's a stone inside that territory, and you also have to take prisoners into account, and count both players' territory, I find it gets harder. (Also, I find it harder to keep track of the changing score that way.)

Come to think of it, every inning ends with 3 outs. So, the only way to get ahead is to get an opposing runner on base and then get him out before he scores. Perhaps this is easier if the pitcher injures the batter sufficiently to slow him down as he runs.

Weirder and weirder.

Ok, so the pitcher must first get two outs (and the offense wants this too, so he'll lob pitches over and the batter will swing wildly with no intention of making contact), then try to bean the next batter. The ball is dead until the pitcher gets the ball back and the ump calls "play". The baserunner will immediately steal second, and the pitcher will immediately try to throw a strike.

The friendly way to play is that the manager can now call "time!" to create a dead ball and freeze the batter at second. Since we're already trying to bean players, it's worth noting that an injury also causes a dead ball...

The pitcher receives the ball again, the ump calls "play", he pitches and the baserunner steals third. Again "time!" is called. Once more, this repeats, with the baserunner heading for home as the pitcher pitches. If the pitcher manages to pitch 3 strikes in a row, the inning is over with one man left on base. If he throws a ball at any point, the runner makes it home, and he needs to bean this batter and repeat the prrocess (although this batter got some free strikes first, so it'll be harder to accomplish).

I think I may have wandered off topic a little bit here...

And some people think that go has complicated rules!

_________________
The Adkins Principle:
At some point, doesn't thinking have to go on?
— Winona Adkins

Visualize whirled peas.

Everything with love. Stay safe.

Send in the designated crawler.

_________________
The Adkins Principle:
At some point, doesn't thinking have to go on?
— Winona Adkins

Visualize whirled peas.

Everything with love. Stay safe.

I like how only two responses to this post have actually been on topic...

_________________
Thinking like a go player during a game of chess is like bringing a knife to a gun-fight. Thinking like a chess player during a game of go feels like getting knifed while you're holding a gun...