in JS sometimes generateCoords generate illegal moves (a self-capturing move, for example) and a test (for instance, "Rollback more than amount of moves raises an error") could fail with a correct solution.
I was lucky to observe it at least once
maybe that could be fixed (or, at least, it could be mentioned in description that test could have some unstable behaviour)
Just throw and the test cases are designed to handle such a case by asserting that there is an error thrown. Then it is gonna re-hit / re-invoke your method with another valid input to assert that all went well. :) Take it easy, Make it simple..
This is not kata invention. Colors and starting with Black is something related to the Real Go Game rules. You may find it useful to visit the wikipedia page of Go (game) or read about it from any recognized source or maybe watch some quick tutorial videos to grasp the idea.
The board is empty to begin with. Black plays first unless given a handicap of two or more stones, in which case White plays first. The players may choose any unoccupied intersection to play on except for those forbidden by the ko and suicide rules (see below).
However, I do believe this must not be missing in the description of course!!!
The desc just says it implicitly & partly/poorly "not completely with no regard to handicaps or when the game is replayed/rolledback or some other actions maybe" within the reset section:
reset
Resetting the board should clear all of the stones from it and set the turn to "black".
And yes that's it. Kindly consider revamping the DESC etirly please :) It'd pay off i think ^_^
These color games this kata is doing is just driving me insane, I can't actually understand which one is black and which one is white. It is so unclear. And another thing that appears to me to be strange is : Why is black making the first move? Shouldn't it be white?
There are practical reasons, why some Go software has rollbacks. It gives the player the possibility to analyse their game play on the computer, just like on a real Go board: Taking back a number of moves and try a different variation to see if the outcome is better than the original (main) variation of the game. Also you can save game records with the real game as main variation and show some side variations, including comments why this variation is better and that is worse. This is usually done by stronger Go players and is replayed by weaker Go players using Go software capable reading these game records. There is a notation protocol (the GTP protocol) , which most common Go software use to read and write Go game records.
This shouldn't be an issue. It is stated in the Kata's description in section "Placing stones on board":
"Note that the letter I is omitted from possible coordinates."
There are pracitcal reasons for it. In live tournament Go games the players may need to write down their game records to be able to recreate the game unaltered in case some issues came up at the end, for example while scoring the final game state. Beside graphical notation on preprinted empty go board sheets it is possible to record the game in simple text form (similar to chess). This is done by writing down who's turn it is and where that player's stone was placed, for example "Bh4 Wc3 Bd16" and so on. To avoid confusing i and j there is no i column in the Go board coordinates.
in JS sometimes generateCoords generate illegal moves (a self-capturing move, for example) and a test (for instance, "Rollback more than amount of moves raises an error") could fail with a correct solution.
I was lucky to observe it at least once
maybe that could be fixed (or, at least, it could be mentioned in description that test could have some unstable behaviour)
Man, it took me like 20 minutes on StackOverflow to come up with a stupidly over-complicated version of this....
I've translated it a week a go, but not yet approved. Dunno if that's helpful :)
Kindly LMK your feedbck and whether any help could be needed!
Cheers,
Just throw and the test cases are designed to handle such a case by asserting that there is an error thrown. Then it is gonna re-hit / re-invoke your method with another valid input to assert that all went well. :) Take it easy, Make it simple..
Go Translation
This is not kata invention. Colors and starting with Black is something related to the Real Go Game rules. You may find it useful to visit the wikipedia page of Go (game) or read about it from any recognized source or maybe watch some quick tutorial videos to grasp the idea.
Here: https://en.wikipedia.org/wiki/Go_(game) it says:
However, I do believe this must not be missing in the description of course!!!
The desc just says it implicitly & partly/poorly "not completely with no regard to handicaps or when the game is replayed/rolledback or some other actions maybe" within the reset section:
reset
HOW ON EARTH AM I SUPPOSED TO THROW AN ERROW AND CONTINUE THE DAMN CODE DUE TO KO RULE, HUH????
closing as this particular behavior is indeed mentionned
These color games this kata is doing is just driving me insane, I can't actually understand which one is black and which one is white. It is so unclear. And another thing that appears to me to be strange is : Why is black making the first move? Shouldn't it be white?
There are practical reasons, why some Go software has rollbacks. It gives the player the possibility to analyse their game play on the computer, just like on a real Go board: Taking back a number of moves and try a different variation to see if the outcome is better than the original (main) variation of the game. Also you can save game records with the real game as main variation and show some side variations, including comments why this variation is better and that is worse. This is usually done by stronger Go players and is replayed by weaker Go players using Go software capable reading these game records. There is a notation protocol (the GTP protocol) , which most common Go software use to read and write Go game records.
As explained above, not a kata issue.
This shouldn't be an issue. It is stated in the Kata's description in section "Placing stones on board":
"Note that the letter I is omitted from possible coordinates."
There are pracitcal reasons for it. In live tournament Go games the players may need to write down their game records to be able to recreate the game unaltered in case some issues came up at the end, for example while scoring the final game state. Beside graphical notation on preprinted empty go board sheets it is possible to record the game in simple text form (similar to chess). This is done by writing down who's turn it is and where that player's stone was placed, for example "Bh4 Wc3 Bd16" and so on. To avoid confusing i and j there is no i column in the Go board coordinates.
Be careful when specifying the alphabet for the columns, because the letter "i" is omitted in the tests :)
Loading more items...