{"action":"created","issue":{"url":"https://api.github.com/repos/pychess/pychess/issues/436","labels_url":"https://api.github.com/repos/pychess/pychess/issues/436/labels{/name}","comments_url":"https://api.github.com/repos/pychess/pychess/issues/436/comments","events_url":"https://api.github.com/repos/pychess/pychess/issues/436/events","html_url":"https://github.com/pychess/pychess/issues/436","id":56206411,"number":436,"title":"Variants patches","user":{"login":"pychess","id":10670522,"avatar_url":"https://avatars.githubusercontent.com/u/10670522?v=3","gravatar_id":"","url":"https://api.github.com/users/pychess","html_url":"https://github.com/pychess","followers_url":"https://api.github.com/users/pychess/followers","following_url":"https://api.github.com/users/pychess/following{/other_user}","gists_url":"https://api.github.com/users/pychess/gists{/gist_id}","starred_url":"https://api.github.com/users/pychess/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pychess/subscriptions","organizations_url":"https://api.github.com/users/pychess/orgs","repos_url":"https://api.github.com/users/pychess/repos","events_url":"https://api.github.com/users/pychess/events{/privacy}","received_events_url":"https://api.github.com/users/pychess/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/pychess/pychess/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":12,"created_at":"2015-02-02T08:02:50Z","updated_at":"2015-02-02T08:03:40Z","closed_at":null,"body":"Original [issue 436](https://code.google.com/p/pychess/issues/detail?id=436) created by @mattgatto:\n\nIn preparation for the new seek dialog I've been working on, and because\nissue #393 requires a data structure in it, I have a patch I'd like reviewed\nbefore I check it in.\n\nThe patch mainly does 4 things which are somewhat interdependent:\n\n1) adds all of the FICS variants we currently support (pawnspushed,\npawnspassed, random, and asymmetric random) to the pychess New Game dialog.\n(pychess/Variants/*)\n2) has some miscellaneous variant changes in the pychess/ic/managers/*\n3) removes castling from the \"Shuffle\" variant to align it with the general\nconsensus that \"Shuffle Chess\" aka wild/2, doesn't allow castling. This was\nalso discussed in revision 1082 . My basis for this reasoning is a) the\nFICS Shuffle variant aka wild/2 doesn't allow castling (\nhttp://www.freechess.org/Help/HelpFiles/wild.html ), b) ChessMaster's\nShuffle aka \"Pieces Shuffle\" doesn't allow castling (\nhttp://www.oyunbunlar.com/Readme/Simulasion/CHESSMASTER\\_11\\_ReadMe.txt ), c)\nICC's Shuffle which is wild/2 doesn't allow castling (\nhttp://www.chessclub.com/helpcenter/tips/wild.html ), d) xboard's Shuffle\naka nocastle doesn't allow castling (\nhttp://tim-mann.org/xboard/engine-intf.htmlcomment 8\\. ). So this seems to be the\ngeneral consensus except for the random guy on wikipedia who changed the\nwikipedia Shuffle Chess rules entry to \"castling only possible when king\nand rook are on their traditional starting squares\":\nhttp://en.wikipedia.org/w/index.php?title=Chess960&amp;diff=prev&amp;oldid=89873705\n. (pychess/Variants/shuffle.py)\n4) fixes an issue in spy and hint engine initialization when a variant has\ncecp\\_name=\"unknown\" and disables the Hint and Spy engine Menu entries when\nthe tab is switched to a game where the user configured Hint and/or Spy\nengines don't support the variant being played. (GameModel.py, ionest.py,\ngamenanny.py, Main.py)"},"comment":{"url":"https://api.github.com/repos/pychess/pychess/issues/comments/72418744","html_url":"https://github.com/pychess/pychess/issues/436#issuecomment-72418744","issue_url":"https://api.github.com/repos/pychess/pychess/issues/436","id":72418744,"user":{"login":"pychess","id":10670522,"avatar_url":"https://avatars.githubusercontent.com/u/10670522?v=3","gravatar_id":"","url":"https://api.github.com/users/pychess","html_url":"https://github.com/pychess","followers_url":"https://api.github.com/users/pychess/followers","following_url":"https://api.github.com/users/pychess/following{/other_user}","gists_url":"https://api.github.com/users/pychess/gists{/gist_id}","starred_url":"https://api.github.com/users/pychess/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pychess/subscriptions","organizations_url":"https://api.github.com/users/pychess/orgs","repos_url":"https://api.github.com/users/pychess/repos","events_url":"https://api.github.com/users/pychess/events{/privacy}","received_events_url":"https://api.github.com/users/pychess/received_events","type":"User","site_admin":false},"created_at":"2015-02-02T08:03:40Z","updated_at":"2015-02-02T08:03:40Z","body":"Comment [11.](https://code.google.com/p/pychess/issues/detail?id=436#c11) originally posted by @mattgatto:\n\nWon't the pychess engine have to be told during initialization that castling isn't\nallowed? Sounds good to me, I just don't know how to do it :)."}}