I agree that the empty board should be removed. The large blue area is due to putting too large a number of empty spaces (made blue rather than board spaces by the limit to number of rows): replacing the 384 at the beginning of the code string by 96 should work. For file labels that's a parameter in the diagram designer (and resulting image url string) and can easily be fixed, but it's worth saying something in the text: you want to skip x so that capture notation doesn't conflict.
Also, there's an odd pattern of blue strips between some rows and columns. Changing the scale parameter to 60 seems to fix it; other numbers give different patterns. Probably better is to use the default scale for the diagram designer, but then scale it down in the page.
But is there some motivation for this game? There are other games that just push together multiple boards & piece sets. Does this one stand out as better in some way? Why so much space behind the pieces?
I agree that the empty board should be removed. The large blue area is due to putting too large a number of empty spaces (made blue rather than board spaces by the limit to number of rows): replacing the
384at the beginning of thecodestring by96should work. For file labels that's a parameter in the diagram designer (and resulting image url string) and can easily be fixed, but it's worth saying something in the text: you want to skipxso that capture notation doesn't conflict.Also, there's an odd pattern of blue strips between some rows and columns. Changing the
scaleparameter to 60 seems to fix it; other numbers give different patterns. Probably better is to use the default scale for the diagram designer, but then scale it down in the page.But is there some motivation for this game? There are other games that just push together multiple boards & piece sets. Does this one stand out as better in some way? Why so much space behind the pieces?