08.05.2026, 17:53
yeah moving it to the top of the cell works. now there's one solution. the standard rule for given borders in chaos constructions and similar region building puzzles is that a given border is a border between two different regions. if you want it to mean something else, like that a region can't be cut in half by a border but can take both cells as long as it takes other cells to move around the border and still be a continuous region... then you'd have to clearly specify that because that is not standard. since it only gave one issue here which is easily fixed by moving the border up as you suggested, i recommend going for the more standard border rule.
also on the solution code: i get why you did it this way, thats why im saying i dont mind you do as you want it, im not one of those easily annoyed solvers. but im just saying: dont be surprised at annoyed comments... and some of them absolutely will bother to fill in the solution code even though they hate how 'complicated' it is, just to complain in the comments about it.
i personally think there is no reason to put the digits in size order. doing it row by row is equally easy to explain, equally 'complicated' (a.k.a. not too complicated in my opinion...) to be bothered with filling in as a solver, and actually gives more information ensuring people actually did the puzzle right because then it still includes the order of the regions as well as their top digits - if sorted it no longer says anything about which region is which. but you do it the way you prefer.
an alternate way of including the region building in a code would be something like 'column 7, with a - for each region border, e.g. 123-4-5-678-9'
also on the solution code: i get why you did it this way, thats why im saying i dont mind you do as you want it, im not one of those easily annoyed solvers. but im just saying: dont be surprised at annoyed comments... and some of them absolutely will bother to fill in the solution code even though they hate how 'complicated' it is, just to complain in the comments about it.
i personally think there is no reason to put the digits in size order. doing it row by row is equally easy to explain, equally 'complicated' (a.k.a. not too complicated in my opinion...) to be bothered with filling in as a solver, and actually gives more information ensuring people actually did the puzzle right because then it still includes the order of the regions as well as their top digits - if sorted it no longer says anything about which region is which. but you do it the way you prefer.
an alternate way of including the region building in a code would be something like 'column 7, with a - for each region border, e.g. 123-4-5-678-9'
