Maverick 4
(RS-rating: 1.9 - but I think that's too high, maybe a hard 1.5)

3x3:d:k
Have fun!
Cheers,
Nasenbaer

You're telling me! The first 11 moves in my WT (out of the 13 I've managed to find up to now) are all "45" tests(!), which is very unusual for me...Afmob wrote:That was a demanding Killer. The moves might be of rating 1.5 but it took me really long to find them...
Yes, the gap was certainly a bit on the short side! It will be interesting to see whether we get another Assassin on Friday. Things certainly don't look promising at the moment, with no sign of Ruud on the horizon. I'm wondering, if it's just a case of being particularly busy with the day job, why he didn't post any announcement to that effect. Very strange.Afmob wrote:By the way, I think we can rest the Mavericks for a while because 2 in one week is more than enough since the gap between M1 and M2 was one month even though there is no Assassin this week.
Afmob wrote:That was a demanding Killer. The moves might be of rating 1.5 but it took me really long to find them...
I'm still working at it, making some progress each session. So far 20(!) different "45" tests in 31 steps. Unusually for a Killer-X I haven't yet managed to use either diagonal.mhparker wrote:You're telling me! The first 11 moves in my WT (out of the 13 I've managed to find up to now) are all "45" tests(!), which is very unusual for me...
Sadly the diagonals are only there because of uniqueness this time, sorry for that.Andrew wrote:I'm still working at it, making some progress each session. So far 20(!) different "45" tests in 31 steps. Unusually for a Killer-X I haven't yet managed to use either diagonal.
As you wish. I only gave Maverick 4 to you because everybody seemed to hunger for a new challenge indicated by the amount of walkthroughs for Maverick 3.Afmob wrote:By the way, I think we can rest the Mavericks for a while because 2 in one week is more than enough since the gap between M1 and M2 was one month even though there is no Assassin this week.
Andrew wrote:I'm still working at it, making some progress each session. So far 20(!) different "45" tests in 31 steps. Unusually for a Killer-X I haven't yet managed to use either diagonal.
No need to apologise. Uniqueness is a good reason to make a Killer into a Killer-X.Nasenbaer wrote:Sadly the diagonals are only there because of uniqueness this time, sorry for that.
Now that I've finished the puzzle I must disagree with that. The diagonals were very helpful from step 42 onward.Nasenbaer wrote:Sadly the diagonals are only there because of uniqueness this time, sorry for that.
M4 Walkthrough
Prelims:
a) 21(3) at R2C1 = {489/579/678} (no 1..3)
b) 8(2) at R2C2 = {17/26/35} (no 4,8,9)
c) 5(2) at R2C8 = {14/23}
d) 20(3) at R5C8 = {389/479/569/578} (no 1,2)
e) 7(2) at R8C2 = {16/25/34} (no 7..9)
f) 19(3) at R8C3 = {289/379/469/478/568} (no 1)
g) 15(5) at R8C4 = {12345}, locked for N8
h) 15(2) at R8C8 = {69/78}
1. Innies R89: R8C159 = 22(3) = {589/679} (no 1..4)
1a. 9 locked for R8
1b. cleanup: no 6 in R9C9
2. Outies R1: R23C5 = 8(2) = {17/26/35} (no 4,8,9)
3. Outies R123: R4C19 = 9(2) = [45/54/63/72/81]
3a. -> no 9; no 6..8 in R4C9
4. I/O diff. N7: R7C3 = R6C1 + 2
4a. -> no 1,2 in R7C3; no 8,9 in R6C1
5. I/O diff. N9: R6C9 = R7C7 + 4
5a. -> no 6..9 in R7C7; no 1..4 in R6C9
6. I/O diff. N3: R23C7 = R4C9 + 12
6a. -> min R23C7 = 13
6b. -> no 1..3 in R23C7
7. I/O diff. C12: R49C2 = R1C3 + 11
7a. min. R1C3 = 1 -> min. R49C2 = 12
7b. -> no 1,2 in R49C2
7c. max. R49C2 = 17 -> max. R1C3 = 6
7d. -> no 7..9 in R1C3
8. I/O diff. C89: R49C8 = R1C7
8a. min. R49C8 = 3 -> min. R1C7 = 3
8b. -> no 1,2 in R1C7
8c. max. R1C7 = 9 -> max. R49C8 = 9
8d. -> no 9 in R49C8
9. Innies N6: R4C9+R6C79 = 9(3) = {126/135} (no 4,7..9)
(Note: not {234}, because none of these digits in R6C9)
9a. 1 locked for N6
9b. {5/6} must go in R6C9
9c. -> no 5,6 in R4C9+R6C7
9d. cleanup: R7C7 = {12} (step 5); no 4,5 in R4C1 (step 3)
10. 12(3) at R8C7 = {138/147/156/237/246/345} (no 9)
(Note: {129} blocked by R7C7)
11. 20(3) at R5C8 = {389/479/578} (no 6)
(Note: {569} blocked by R6C9)
12. Innies N69: R4C9+R67C7 = 5(1+2) = [131/212]
12a. -> no 3 in R4C9; no 2 in R6C7
12b. R4C9+R6C79 (step 9) = [216/135]
12c. cleanup: no 6 in R4C1 (step 3)
Afmob pointed out that I could have added that 1 is locked in R67C7 for C7 here.
13. 12(3) at R2C9 = {129/138/147/237} (no 5,6)
(Note: not {345}, because none of these digits in R4C9;
{156} blocked by R6C9; {246} blocked by h9(3)n6 (step 12b))
14. I/O diff. N5: R78C5 = R6C46
14a. min. R78C5 = 13 -> min. R6C46 = 13
14b. -> no 1..3 in R6C46
(Note: could stretch the logic here to also eliminate 4 from R6C46, but that's done in next step)
15. Outies N5789: R6C1379 = 13(4) = {1246/1345} (no 7..9)
(Note: not {1237}, because none of these digits in R6C9)
15a. 1,4 locked for R6
15b. 4 locked in R6C13 for N4
15b. possible permutations h13(4): [4216/1435/4135]
(Note: [2416] blocked by R7C3 (step 4); [3415/4315] blocked by h9(3)n6 (step 12b))
15b. -> R6C1 = {14}; R6C3 = {124}
15c. cleanup: R7C3 = {36} (step 4)
16. 17(4) at R6C1 = {1259/1349/1457} (no 6,8) = {(7/9)..}
(Note: not {2357}, because none of these digits in R6C1;
{1358/1367/2456} blocked by R7C3 (step 4);
{1268} blocked because it would force R7C3 to 3 and thus leave no combos for 7(2)n7;
{2348} blocked because it would force R7C3 to 6 and thus leave no combos for 7(2)n7)
16a. no 1 in R9C1 (CPE)
16b. cleanup: no 6 in R8C2
17.Hidden killer pair on {79} within N7 as follows:
17a. 17(4) at R6C1 must have exactly 1 of {79} within N7 (step 16)
17b. -> 19(3) at R8C3 (only other place for {79} in N7) must also have exactly 1 of {79}
17c. -> {379/568} combos both blocked
17d. Furthermore, 8 of N7 locked in 19(3) = {8..}
17e. -> 19(3) at R8C3 = {289/478} (no 3,5,6)
18. 6 in N7 locked in D/ -> not elsewhere in D/
18a. 6 in C9 locked in R678C9
18b. -> no 6 in R7C8
18c. 22(4) at R6C9 = {6..} = {1678/2569/3469/3568/4567} (no eliminations yet)
19. 21(3) at R2C1 = {489/678} (no 5)
(Note: {579} blocked by R8C1)
19a. 8 locked for C1
20. Grouped AIC removes combos {138/147} from 12(3) at R8C7:
(6)r9c78=(6)r9c1,(1)r8c2-(1)r7c12=(1)r7c789
This can be explained in verbose form as follows:
20a. Either R9C78 contains a 6 or...
20b. ...R9C78 does not contain a 6
20c. => R9C1 = 6 (strong link, R9); R8C2 = 1 (neutral link, 7(2))
20d. -> R7C12 does not contain a 1 (weak link, N7)
20e. => R7C789 contains a 1 (strong link, R7)
20f. -> no 1 in 12(3) at R8C7
20g. Thus, if 12(3) at R8C7 does not contain a 6, it cannot contain a 1
20h. -> {138/147} combos blocked
20i. -> 12(3) at R8C7 (step 10) = {156/237/246/345} (no 8)
21. Distribution of {13} across N79:
21a. 7(2) at R8C2 cannot contain both of {13}
21b. -> R7C123 (only other place for {13} in N7) must contain at least 1 of {13}
21c. 12(3) at R8C7 cannot contain both of {13}
21d. -> R7C789 (only other place for {13} in N9) must contain at least 1 of {13}
21e. from steps 21b and 21d, R7C123 and R7C789 must each contain exactly 1 of {13}
21f. -> 7(2) at R8C2 and 12(3) at R8C7 must also each contain exactly 1 of {13}
21g. -> 7(2) at R8C2 = {16/34} (no 2,5) = {(3/6)..}
21h. 12(3) at R8C7 (step 20i) = {(1/3)..} = {156/237/345} (no eliminations)
22. 7(2) at R8C2 (step 21g) and R7C3 form killer pair on {36}
22a. -> no 3 elsewhere in N7 and D/
22b. cleanup: no 2 in R3C8
23. Grouped Turbot Fish removes 1 from R7C89:
(1)r789c7=(1)r6c7-(1)r6c1=(1)r7c12
This can be explained in verbose form as follows:
23a. Either R789C7 contains a 1 or...
23b. ...R789C7 does not contain a 1
23c. => R6C7 = 1 (strong link, C7)
23d. -> R6C1 <> 1 (weak link, R6)
23e. => R7C12 = 1 (strong link, 17(4))
23f. Thus, either R789C7 or R7C12 (or both) must contain a 1
23g. -> no 1 in R7C89 (common peers)
24. 1 now unavailable to 22(4) at R6C9 (step 18c) = {2569/3469/3568/4567}
24a. Hidden killer pair on {89} blocks {4567} combo, as follows:
24b. Only places for {89} in N9 are 15(2) and 22(4), neither of which can contain both
24c. -> each of 15(2) at R8C8 and 22(4) at R6C9 must contain exactly 1 of {89}
24d. -> {4567} combo blocked
24e. -> 22(4) at R6C9 = {2569/3469/3568} (no 7) = {(2/3}..}
Afmob pointed out here that step 23 was not really necessary, because even without it, 22(4) at R6C9 = {1678/2569/3469/3568} = {(2/3/7)..} (within N9), thus also blocking the {237} combo for 12(3) in the next step and thus likewise breaking the puzzle.
25. 12(3) at R8C7 (step 21h) = {156/345} (no 2,7)
(Note: {237} blocked by 22(4) at R6C9 (step 24e))
25a. 5 locked for N9
26. 7 in N9 locked in 15(2) at R8C8 = {78} (no 6,9), locked for N9 and D\
26a. cleanup: no 1 in R3C2
27. 9 in R9 locked in R9C23 for N7
27a. 19(3) at R8C3 = {9..} = {289} (no 4,7) (last combo)
27b. 2 locked in R89C3 for C3 and N7
28. Hidden single (HS) in R9 at R9C9 = 7
28a. -> R8C38 = [28]
29. Naked pair (NP) at R6C13 = {14}, locked for R6 and N4
29a. -> R6C7 = 3
29b. -> R46C9 (step 12b) = [15]
29c. -> R7C7 = 1 (step 5); R4C1 = 8 (step 3, but also obtainable via cage split of N4 innies)
30. 6 in C9 locked in N9 -> not elsewhere in N9
30a. 12(3) at R8C7 = {345} (last combo)
30b. -> R9C8 = 3; R89C7 = {45}, locked for C7 and N9
30c. cleanup: no 2 in R2C8
31. HS in R9 at R9C1 = 6
31a. -> R8C2 = 1; R7C3 = 3
31b. -> R6C1 = 1 (step 4)
31c. -> R6C3 = 4
31d. cleanup: no 7 in R23C1 (step 19)
32. R23C8 = [41]
32a. -> R23C1 = [94]
33. 12(3) at R1C1 = [381/561]
33a. -> R1C1 = {35}; R1C2 = {68}; R1C3 = 1
33b. cleanup: no 7 in R3C2
Only singles and simple cage sums left now.
Good to see that you posted your walkthrough, Mike.Mike wrote:Afmob and Andrew will probably have a good laugh at this one, when they see what techniques I was resorting to! I suspect I've missed something important, but at least my approach should make for some interesting reading if nothing else! I hope so.
We'll all agree with that. I certainly wouldn't want the same walkthrough thrice. However I think it's acceptable to have two very similar walkthroughs if they show different logic or thought patterns to achieve the similar results.Afmob wrote:There is nothing wrong with different solving approaches. Better than reading the same wt thrice.