The current version 0.1.6 contains the first try at alternate board shapes. The display errors will be gone in 0.1.7 - the CVS already has the corrected code.
PerlGo can be programmed to use almost any conceivable board shape - it is 'only' a question of re-defining the intersections and designing a display-module.
A distant future version may even have a board definition module and editor, but this is a long time from now.
Another idea would be 3d-Go, which, although possible, will be very difficult to render. A 9x9x9-Cube would consist of 729 intersections. To play a game at this level of complexityl, you would need to be able to see a great number of stones at any given time. As of the moment, 19x19 boards in 2D are already somewhat small on average displays - this cannot improve if the number of stones is increased by several times.
Alas, perhaps with holographic displays we will be able to make the move towards 3d-Go :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The current version 0.1.6 contains the first try at alternate board shapes. The display errors will be gone in 0.1.7 - the CVS already has the corrected code.
PerlGo can be programmed to use almost any conceivable board shape - it is 'only' a question of re-defining the intersections and designing a display-module.
A distant future version may even have a board definition module and editor, but this is a long time from now.
Another idea would be 3d-Go, which, although possible, will be very difficult to render. A 9x9x9-Cube would consist of 729 intersections. To play a game at this level of complexityl, you would need to be able to see a great number of stones at any given time. As of the moment, 19x19 boards in 2D are already somewhat small on average displays - this cannot improve if the number of stones is increased by several times.
Alas, perhaps with holographic displays we will be able to make the move towards 3d-Go :)