But, I need two explanations as follows:
the 2nd one can only exclude inside of the box as the center cell is include breaking the 2-string kite formation. { a quick check is to set it as true }
- Code: Select all
- +---------------+---------+---------------+
 | . (1) . | . . . | . . . |
 | (1) (1) (1) | . . . | . (1) . |
 | . (1) . | . . . | . . . |
 +---------------+---------+---------------+
 | . . . | . . . | . . . |
 | . . . | . . . | . . . |
 | . . . | . . . | . . . |
 +---------------+---------+---------------+
 | . . . | . . . | -1 (1) -1 |
 | . (1) . | . . . | (1) (1) (1) |
 | . . . | . . . | -1 (1) -1 |
 +---------------+---------+---------------+
if it was missing then it works like this and be a grouped 2 string kite + ERi
- Code: Select all
- +----------------+------------+---------------+
 | . (1) . | . . . | . . . |
 | (1) (-1) (1) | -1 -1 -1 | -1 (1) -1 |
 | . (1) . | . . . | . . . |
 +----------------+------------+---------------+
 | . -1 . | . . . | . . . |
 | . -1 . | . . . | . . . |
 | . -1 . | . . . | . . . |
 +----------------+------------+---------------+
 | . -1 . | . . . | -1 (1) -1 |
 | . (1) . | . . . | (1) . (1) |
 | . -1 . | . . . | -1 (1) -1 |
 +----------------+------------+---------------+
- Code: Select all
- --------------+-------------+-----------
 / +Z / | . . . | . . .
 +Z +Z +Z | -Z . -Z | . . .
 / +Z / | . . . | . . .
 --------------+-------------+-----------
 . . . | . . -Z | . . .
 / +Z / | +Z / / | / / /
 . . . | . . -Z | . . .
 --------------+-------------+-----------
 . . . | -Z . . | . . .
 / +Z / | / / +Z | / / /
 . . . | -Z . . | . . .
 --------------+-------------+-----------
is it Skyscraper Transport move if r46c6 and r79c4 excluded by basic Skyscraper move and r2c46 may be excluded by Transport ERI?
or you can view it as a combined view of three moves: 2 empty rectangles <> R2C46, and a skyscraper <> r46c6 and r79c4
like i said earlier i can make these extensions go very far easily... and rather not list them all, take this one for example.
- Code: Select all
- +-----------+-----------+---------------+
 | . . . | . . . | . . . |
 | . (1) . | . (1) . | . . . |
 | . . . | . . . | . . . |
 +-----------+-----------+---------------+
 | . . . | . . . | . . . |
 | . . . | . (1) . | . (1) . |
 | . . . | . . . | . . . |
 +-----------+-----------+---------------+
 | . . . | . . . | . (1) . |
 | . -1 . | . -1 . | (1) (1) (1) |
 | . . . | . . . | . (1) . |
 +-----------+-----------+---------------+
is no different then this one. {in fact the above is a subset of it}
- Code: Select all
- +-----------+-----------+---------------+
 | . . . | . . . | . . . |
 | . (1) . | . (1) . | . (1) . |
 | . . . | . . . | . . . |
 +-----------+-----------+---------------+
 | . . . | . . . | . . . |
 | . (1) . | . (1) . | . (1) . |
 | . . . | . . . | . . . |
 +-----------+-----------+---------------+
 | . . . | . . . | . (1) . |
 | . -1 . | . -1 . | (1) (1) (1) |
 | . . . | . . . | . (1) . |
 +-----------+-----------+---------------+
it was doing stuff like this that lead me on the path to coding a fish-finder instead of writing small functions for each point and case as there is too many of them with sub-variations.




 I'd prefer something from a valid puzzle.
 I'd prefer something from a valid puzzle.