Difference between revisions of "Template VI1/Intrusion on the 3rd row"
m (back link to previous page) |
m (No time to fix but at least this is now flagged as incorrect.) |
||
| Line 1: | Line 1: | ||
| − | This article deals with a special case in [[defending against intrusions in template VI1]], namely the intrusion on the 3rd that is not eliminated by [[sub-templates threat]]s. | + | This article deals with a special case in [[defending against intrusions in template VI1]], namely the intrusion on the 3rd that is not eliminated by [[sub-templates threat]]s. NOTE THAT THIS PAGE IS NOT CORRECT; THE SUGGESTED MOVE FOR RED IS A LOSING MOVE AND BLUE CAN RESPOND BY PLAYING ON THE SECOND ROW DIRECTLY UNDER THE TWO STONES; THIS BREAKS THE CONNECTION. |
== Basic situation == | == Basic situation == | ||
Revision as of 23:54, 23 April 2016
This article deals with a special case in defending against intrusions in template VI1, namely the intrusion on the 3rd that is not eliminated by sub-templates threats. NOTE THAT THIS PAGE IS NOT CORRECT; THE SUGGESTED MOVE FOR RED IS A LOSING MOVE AND BLUE CAN RESPOND BY PLAYING ON THE SECOND ROW DIRECTLY UNDER THE TWO STONES; THIS BREAKS THE CONNECTION.
Contents
Basic situation
Red should go here:
WARNING: Unrecognized token: [[#Third-row_followup:_i4|Pi4]]WARNING: Unrecognized token: [[#Third-row_followup:_j3_(stub)|Pj3]]
The Red 1 hex is connected to the bottom, and threatens to connect to the top through either one of the "+" hexes. Thus these are the only important incursions. An incursion to the right of the number 1 hex is important only in connection with the two indicated here, and will be seen in the treatement below transposed into the sequel.
Third-row followup: i4
Figuring out the Must-play region
Red threatens to play at "+" points above, with these templates:
We need only consider the intersection of these templates.
