Little Go Cheats

Little Go Hack 1.7.1 + Redeem Codes

Developer: Patrick Näf Moser
Category: Games
Price: Free
Version: 1.7.1
ID: ch.herzbube.littlego

Screenshots

Game screenshot Little Go mod apkGame screenshot Little Go apkGame screenshot Little Go hack

Description

Little Go is a free and open source iOS application that lets you play the game of Go on the iPhone or iPad. You can play against another human (on the same device), or against the computer. The computer player is powered by the open source software library Fuego (http://fuego.sf.net/). The minimum requirement for running this version of Little Go is iOS 9.0.

Features:
- Board sizes between 7x7 and 19x19 (start a new game to change the board size)
- Let the computer player suggest a move or immediately play the move for you
- Calculate the score at any time during the game (area scoring is the default, territory scoring can be selected at the start of a new game)
- Adjust the computer's playing strength and resign behaviour by selecting from a number of presets, or by fine-tuning advanced settings
- Play even games, or games with 2-9 handicap stones (fixed stone placement)
- Select from 5 pre-defined rulesets when you start a new game, or adjust game rules to your preference (komi, ko rule, area/territory scoring system, number of passes to end game, resume play by alternating/non-alternating play, four passes end game)
- Place arbitrary black and white stones for initial board setup before a game starts
- View board positions for moves played earlier during the game (no support for game variations, though)
- Discard moves (aka "undo")
- Display move numbers and coordinate labels
- Zoom & scroll board
- Create and edit board and move annotations (e.g. good/bad move, good position for black/white, etc.) and add textual notes to a position
- Mark intersections on the board with symbols, markers and labels, and draw arrows or lines on the board
- Display player influence (aka territory statistics) for an estimate who owns an area
- Computer vs. computer game for entertainment
- Save & load games to/from the archive
- Use iTunes file sharing to transfer saved games to/from your iOS device
- Import/export game files from/to other apps on your device (e.g. Mail, DropBox)
- In-app user manual (text-only)
- Submit bug report email from inside the app (yes, this *is* a feature :-))
- For the technically inclined: Watch what happens behind the scenes when Little Go and Fuego talk to each other over the Go Text Protocol (GTP)

Your contribution in any form (coding, UI design, testing, bug reports, creating an app video preview, website design) is welcome - please contact me or visit the support website to find out more.

A note about the project state: Several years of development have gone into Little Go since its inception in January 2011. The app now has a feature set that is, I believe, quite nice :-) for a free program. My main focus therefore lies on fixing any remaining bugs (of which I am sure there are plenty) and keeping the app running under future versions of iOS.

Little Go is released under the Apache License 2.0 (http://www.apache.org/licenses/LICENSE-2.0).

Version history

1.7.1
2022-09-23
This is the Little Go bugfix release 1.7.1. It contains two fixes for bugs that caused the app to crash (#397 and #398).

The previous release was the Little Go feature release 1.7.0. An overview of the changes follows, for more details read the in-game Changelog.

Features
--------
- The app now supports reading and writing of all SGF node annotation and move annotation properties (#339). The app also displays these properties' values and lets you edit them. This means that you can now add a valuation to a move (e.g. good/bad move) and/or to the entire board position (e.g. good position for black/white), designate a board position to be a "hotspot" (e.g. it contains a game-deciding move), annotate a board position with an estimated score, and finally you can add textual notes to a board position. Annotation data is displayed by, and can be edited via, an all-new annotation view.
- The app now supports reading and writing of all SGF markup properties (#349). Except for the DD property (dim parts of the board), the app also displays these properties' values and lets you edit them. This means that you can now mark intersections on the board with 5 different symbols (circle, square, triangle, "X" mark, "selected" symbol), place single-character letter markers or single-digit number markers, place a free-form label text, and finally you can draw arrows or plain lines on the board. The app has an all-new markup editing mode for this (accessible via menu icon) that includes drag & drop support to move around existing markup.
- In the Settings screen there are now a number of user preferences that affect how markup is drawn and that let you tweak some aspects of the markup editing process.

Improvements and changes
------------------------
- The general user interface (UI) of Little Go now looks and behaves the same on all device types (#371). This unification of UI layouts became necessary because the effort to support different layouts proved to be too much. Also the unification provided the opportunity to get rid of many behind-the-scenes hacks. The main changes are: 1) Smaller iPhone devices which only support the Portrait orientation UI layout, now display board positions and the navigation buttons differently than before. 2) Larger iPhone devices now display a tab bar when in Landscape orientation (alas, reducing the size of the board). 3) iPad devices now always show board positions when in Portrait orientation, and when in Landscape orientation they display board positions and navigation buttons differently than before.
- Changed the icon of the "More Game Actions" button (#377). The previous icon was a "curved arrow" symbol, which seemed to confuse many users so that they couldn't find important actions, such as "New game". The new icon is the established "hamburger menu" icon, which should now more clearly indicate that the button pops up a menu with actions to select from.
- Button boxes and the board position list now support Dark mode by switching to a dark background color (#378 and #379). Thanks to Peter Waldispühl for reporting this.
- For more improvements/changes see the Changelog.

Bugfixes
--------
- Board position zero (representing the start of the game) sometimes did not display handicap and komi. This is now fixed (#374).
- Various speculative fixes for potential app crashes. See the Changelog for details.

Regressions
-----------
- A bug was introduced in version 1.6.0 that would cause Ko detection to fail after the app was suspended and was forced to restart by the operating system (a relatively common occurrence). This is now fixed (#372). Because Little Go has struggled with Ko detection many times in the past, this regression was particularly painful.

Technical changes
-----------------
- See Changelog.
1.7.0
2022-09-18
This is the Little Go feature release 1.7.0. An overview of the changes follows, for more details read the in-game Changelog.


Features
--------
- The app now supports reading and writing of all SGF node annotation and move annotation properties (#339). The app also displays these properties' values and lets you edit them. This means that you can now add a valuation to a move (e.g. good/bad move) and/or to the entire board position (e.g. good position for black/white), designate a board position to be a "hotspot" (e.g. it contains a game-deciding move), annotate a board position with an estimated score, and finally you can add textual notes to a board position. Annotation data is displayed by, and can be edited via, an all-new annotation view.
- The app now supports reading and writing of all SGF markup properties (#349). Except for the DD property (dim parts of the board), the app also displays these properties' values and lets you edit them. This means that you can now mark intersections on the board with 5 different symbols (circle, square, triangle, "X" mark, "selected" symbol), place single-character letter markers or single-digit number markers, place a free-form label text, and finally you can draw arrows or plain lines on the board. The app has an all-new markup editing mode for this (accessible via menu icon) that includes drag & drop support to move around existing markup.
- In the Settings screen there are now a number of user preferences that affect how markup is drawn and that let you tweak some aspects of the markup editing process.

Improvements and changes
------------------------
- The general user interface (UI) of Little Go now looks and behaves the same on all device types (#371). This unification of UI layouts became necessary because the effort to support different layouts proved to be too much. Also the unification provided the opportunity to get rid of many behind-the-scenes hacks. The main changes are: 1) Smaller iPhone devices which only support the Portrait orientation UI layout, now display board positions and the navigation buttons differently than before. 2) Larger iPhone devices now display a tab bar when in Landscape orientation (alas, reducing the size of the board). 3) iPad devices now always show board positions when in Portrait orientation, and when in Landscape orientation they display board positions and navigation buttons differently than before.
- Changed the icon of the "More Game Actions" button (#377). The previous icon was a "curved arrow" symbol, which seemed to confuse many users so that they couldn't find important actions, such as "New game". The new icon is the established "hamburger menu" icon, which should now more clearly indicate that the button pops up a menu with actions to select from.
- Button boxes and the board position list now support Dark mode by switching to a dark background color (#378 and #379). Thanks to Peter Waldispühl for reporting this.
- For more improvements/changes see the Changelog.

Bugfixes
--------
- Board position zero (representing the start of the game) sometimes did not display handicap and komi. This is now fixed (#374).
- Various speculative fixes for potential app crashes. See the Changelog for details.

Regressions
-----------
- A bug was introduced in version 1.6.0 that would cause Ko detection to fail after the app was suspended and was forced to restart by the operating system (a relatively common occurrence). This is now fixed (#372). Because Little Go has struggled with Ko detection many times in the past, this regression was particularly painful.

Technical changes
-----------------
- See Changelog.
1.6.0
2021-02-27
This is the Little Go feature release 1.6.0. An overview of the changes follows, for more details read the in-game Changelog


Features
--------
- Added an SGF parser (#112). Among other things you can now see if an SGF file in the archive contains more than just one game (#338). A number of user preferences give you some control over how SGF files are processed (#337).
- Added a new user preference "Discard my last move" to the "Board position" settings screen (#99).
- Added a new entry to the "More game actions" menu that lets you play a rematch without showing the "New game" screen first (#313).
- Added a new user preference that lets you choose what kind of computer assistance you would like to receive. With this you can now tell the computer to only make a suggestion how to play instead of immediately making a move on your behalf (#28).

Improvements and changes
------------------------
- The buttons that let the user navigate between board positions have now more space between them (#346), making it less likely that the user taps the wrong button. Thanks to Dan Hassin for both reporting the issue and implementing the fix.
- Improved error handling when loading a game from the archive.
- When a game is saved to the archive the current player names are now written to the SGF data (#237).
- The user interface has been adapted to newer iOS devices with a sensor notch, rounded corners and/or a Home indicator instead of a Home button (#336).
- The app now supports Dark Mode (#345). A new, darker wooden background for the board still needs to be found (#360).
- When Little Go is newly installed from the App Store the default computer player is now weaker (#358). This should give more users a positive first app experience. Users who want a challenge can still increase the difficulty by switching to a stronger computer player. A side effect of this change is that the default computer player no longer uses the "Pondering" setting, which means that the iOS device's battery should now be used up a lot less.
- Added another predefined computer player that has "Pondering" disabled. Users who already have the app installed need to select "Reset to defaults" in the "Players" settings screen to see the new player.
- The app's user interface no longer exposes GTP engine profiles as a separate entity, instead the user interface now only displays players (#211).

Bugfixes
--------
- The app no longer crashes when a game with many moves (500 or more) is archived or unarchived (#357).
- The app no longer crashes when a game is loaded while an ended game with non-alternating dispute resolution is present (#361).
- Speculative fix for a potential app crash when an SGF file is imported (#362).
- The information which player resigned is no longer lost when the user switches to an earlier board position (#341).
- On iPhone devices with larger displays, when the device is rotated while the activity indicator is displayed in the status view the activity indicator is now still displayed after the rotation (#343).

Regressions
-----------
- All iPhones: When board setup mode was added in version 1.5.0 a bug was introduced that made it possible for board position lists to show erroneous information when moves were discarded and then replayed, or when games were restarted with different characteristics. This bug has now been fixed (#359).
- iPhone devices with smaller displays: When iOS 13 or newer was installed on these devices the current board position view stopped responding to taps. This bug has now been fixed (#344).

Technical changes
-----------------
- See Changelog
1.5.1
2019-03-24
This is the Little Go bugfix release 1.5.1. It contains a fix for a bug that causes the app to crash during launch on iOS 9.x and below (#332). Thanks to Li Chen Ke and Dennis for reporting the issue.

The previous release was the Little Go feature release 1.5.0. It contains the following changes:

Features
--------
- Added a board setup mode (#276). When you start a new game, instead of beginning to play you can now switch to board setup mode. In this mode you can place black or white stones in any order and combination to set up the initial board before you begin to play moves. In addition to placing stones, you can select the side which is to play the first move. Read the "Board setup" section in the in-game manual for a detailed feature description.

Bugfixes
--------
- Fix for a memory leak in UnarchiveGameCommand (#331)

Technical changes
-----------------
- Added an initial set of a few automated UI tests (#134)
1.5.0
2019-03-21
This is the Little Go feature release 1.5.0. It contains the following changes:

Features
--------
- Added a board setup mode (#276). When you start a new game, instead of beginning to play you can now switch to board setup mode. In this mode you can place black or white stones in any order and combination to set up the initial board before you begin to play moves. In addition to placing stones, you can select the side which is to play the first move. Read the "Board setup" section in the in-game manual for a detailed feature description.

Bugfixes
--------
- Fix for a memory leak in UnarchiveGameCommand (#331)

Technical changes
-----------------
- Added an initial set of a few automated UI tests (#134)
1.4.1
2019-01-17
This is the Little Go bugfix release 1.4.1. It contains an important fix for a bug in Fuego that could cause Fuego to play a stone during the opening game on an intersection that was already occupied by a handicap or setup stone (#328). In addition, Little Go's error handling is now capable of dealing with such a situation so that user's are not stuck in a seemingly endless "computer is thinking" loop. Thanks to Mark Spurlock for reporting the issue and to Rob Wildschut for diagnosing the problem.

The previous release was the Little Go maintenance and bugfix release 1.4.0. It contains the following changes:

Known bugs
----------
- On iPhone Plus devices as well as on iPhone XS Max, when the user navigates to the first or last board position most of the time the new current board position is not displayed with a special background color as it should (#326).

Features
--------
- Added support for loading and saving .sgf files that contain stone and/or player setup nodes (#323). This kind of .sgf files is frequently used for sharing board positions that teach how to play best in certain game situations, or that are puzzles to be solved. View the in-app Changelog for additional notes.

Improvements and changes
------------------------
- The "New game" screen now displays a recommendation to use the area scoring system.
- The "Game info" screen now shows stone and player setup information.
- When the app is started for the first time after the update, two new GTP commands "list_setup" and "list_setup_player" are added to the user's list of GTP commands (Diagnostics > GTP commands).
- The way how an archived game can be shared was re-implemented. This may result in users now seeing different sharing options.
- The Changelog is now available in-app

========
Bugfixes
========
- When playing with area scoring, the Fuego computer player now correctly includes handicap compensation in its score calculation (#319). Before this fix, the Fuego computer player was calculating scores without handicap compensation, which would lead to it resigning (when playing as white) even though it had actually won the game. Or it might not resign (when playing as black) even though it had actually lost the game. This serious bug was reported by dtsudo - thanks a lot!
- The app now synchronizes komi with Fuego when board positions are changed (#324). Up until now the app never synchronized komi. View the in-app Changelog for details how this omission might have affected gameplay.
- A bug in the board drawing routines was fixed which caused the app to occasionally crash (#308).

===========
Regressions
===========
- White player influence is now shown correctly with white squares (#317). White player influence was erroneously shown with black squares since the release of version 1.1.0. Thanks for reporting this bug go to ecru86.
- Users that do not have automatic crash reporting enabled are now asked whether they want to submit a crash report (#321). The alert that asks for permission was accidentally disabled since the release of version 1.3.0. Because the alert was disabled, no crash reports were submitted at all unless the user had automatic crash reporting enabled.

=================
Technical changes
=================
- The project has been upgraded to the iOS 12.1 SDK (#314) and Xcode 10.1 (#315)
- Started migration from Twitter Fabric to Google Firebase (#320). A best effort has been made to disable all other Google services and to only keep Crashlytics enabled. Notably, Firebase Analytics data collection has been explicitly disabled!
- View the in-app Changelog to read about other technical changes
1.4.0
2019-01-15
Version 1.4.0 is a maintenance and bugfix release. It contains the following changes:

Known bugs
----------
- On iPhone Plus devices as well as on iPhone XS Max, when the user navigates to the first or last board position most of the time the new current board position is not displayed with a special background color as it should (#326).

Features
--------
- Added support for loading and saving .sgf files that contain stone and/or player setup nodes (#323). This kind of .sgf files is frequently used for sharing board positions that teach how to play best in certain game situations, or that are puzzles to be solved. View the in-app Changelog for additional notes.

Improvements and changes
------------------------
- The "New game" screen now displays a recommendation to use the area scoring system.
- The "Game info" screen now shows stone and player setup information.
- When the app is started for the first time after the update, two new GTP commands "list_setup" and "list_setup_player" are added to the user's list of GTP commands (Diagnostics > GTP commands).
- The way how an archived game can be shared was re-implemented. This may result in users now seeing different sharing options.
- The Changelog is now available in-app

========
Bugfixes
========
- When playing with area scoring, the Fuego computer player now correctly includes handicap compensation in its score calculation (#319). Before this fix, the Fuego computer player was calculating scores without handicap compensation, which would lead to it resigning (when playing as white) even though it had actually won the game. Or it might not resign (when playing as black) even though it had actually lost the game. This serious bug was reported by dtsudo - thanks a lot!
- The app now synchronizes komi with Fuego when board positions are changed (#324). Up until now the app never synchronized komi. View the in-app Changelog for details how this omission might have affected gameplay.
- A bug in the board drawing routines was fixed which caused the app to occasionally crash (#308).

===========
Regressions
===========
- White player influence is now shown correctly with white squares (#317). White player influence was erroneously shown with black squares since the release of version 1.1.0. Thanks for reporting this bug go to ecru86.
- Users that do not have automatic crash reporting enabled are now asked whether they want to submit a crash report (#321). The alert that asks for permission was accidentally disabled since the release of version 1.3.0. Because the alert was disabled, no crash reports were submitted at all unless the user had automatic crash reporting enabled.

=================
Technical changes
=================
- The project has been upgraded to the iOS 12.1 SDK (#314) and Xcode 10.1 (#315)
- Started migration from Twitter Fabric to Google Firebase (#320). A best effort has been made to disable all other Google services and to only keep Crashlytics enabled. Notably, Firebase Analytics data collection has been explicitly disabled!
- View the in-app Changelog to read about other technical changes
1.3.1
2017-01-19
Version 1.3.1 is a bugfix release that contains only one change, an important fix for a long-standing bug that sometimes caused ko detection to fail when an old board position was viewed (#307).

This was the root cause for the dreaded alert message "Your move was rejected by Fuego", which must have popped up on quite a few people's devices, but which I had never been able to reproduce despite the bug reports that were kindly sent to me by some of the most patient users. Yesterday, however, I received a report that finally gave me a reproducible case which allowed me to pinpoint and fix the coding error. Many thanks to everybody who sent bug reports, but especially to Manuel Braun for submitting the crucial last bug report.
1.3.0
2016-09-14
Version 1.3.0 is mostly a technical release, with one very important bugfix. The release contains the following changes:

Features
--------
- iPad Pro is now supported with its native screen resolution (#297)

Improvements and changes
------------------------
- When the game is resumed to settle a life & death dispute, a "Resume Play" alert is displayed if the game rules allow resumption with non-alternating play. Previously the alert buttons were sometimes displayed in the order Black/White and someteimes in the order White/Black, depending on whose player's turn it was. Now the alert buttons are always displayed in the order Black/White (#300)

Bugfixes
--------
- Ko detection now works correctly if an old board position is viewed (#289). Many thanks to Denis Martynov for bringing this to my attention. I promised to release the bugfix "as soon as possible, probably next weekend". This was in June 2015 - over a year ago :-(
- The status view now displays the correct text after the user discards all moves at the beginning of a game (#301)
- iPhone n Plus devices: The "Game Info" and "More Game Actions" buttons are now correctly enabled after rotating the device to landscape (#299)

Technical changes
-----------------
- The project has been upgraded to the iOS 9.3 SDK (#298) and Xcode 7.3.1
- Support for iOS 7 has been dropped, the minimum required version is now iOS 8.1 (#260). The only device that is no longer supported is the iPhone 4.
- The project now uses CocoaPods for most 3rdparty libraries (#291)
- The 3rd party crash reporting library QuincyKit was replaced by a new library called Crashlytics (#293)
1.2.0
2015-06-23
Version 1.2.0 is a feature release that contains the following changes:

Features
--------
- iPhone 6/6+ are now supported with their native screen resolution (#263)
- iPhone 6+ has a redesigned user interface that makes better use of the available screen estate (#253). iPhone 6+ also supports holding the device in landscape.
- When starting a new game, it is now possible to select from several predefined rulesets, which allows setting many game rules at once with a single tap (#274). This makes the "New game" screen less cluttered and more user friendly. Rule enthusiasts can still adjust each individual game rule by calling up an "Advanced settings" screen.
- Gameplay mechanics at the end of the game have been significantly revised:
- It is now generally possible to resume play after two pass moves without having to discard ("undo") the second pass move
- 3 new game rules were added that govern gameplay mechanics at the end of the game. These rules allow to play games under AGA or IGS rules (#221, #223), but also under Japanese and Chinese rules where non-alternating play is possible to resume a game after it has ended after two pass moves (#275).
- As a consequence of these new gameplay mechanics at the end of the game, a much wider array of .sgf files can now be loaded from the archive (e.g. files with games that were played on IGS). Thanks to Norbert Langermann for the suggestion that triggered the development of this feature.
- One more thing: When placing a stone a magnifying glass is now displayed that shows the area of the board that currently under the user's 'fingertip (#271). This feature replaces the old "stone distance from fingertip" feature, which confused and was hated by many users.

Improvements and changes
------------------------
- Disable Fuego pondering in human vs. human games (#281). This saves *a lot* of otherwise wasted battery power. Thanks to Ben Jackson for the suggestion. Unfortunately, a nasty piece of code was required to upgrade existing user preferences, which may result in unnecessary player and profile backup copies cluttering the upgraded preferences. Users will get an alert if this happens so that they can clean up their preferences.
- A couple of buttons have gotten new icons (#269). Thanks to David Helfand for the suggestion.
- Other minor improvements (#265, #268, #277)

Bugfixes
--------
- The app now correctly synchronizes handicap stones with Fuego when board positions are changed (#279). This is the most important bugfix of this release because it fixes another source for the infamous "The computer played an illegal move" and "Your move was rejected by Fuego" alerts. Many thanks to Laurent Guanzini for providing step-by-step instructions that helped me with diagnosing the problem!
- The app no longer crashes when a game is loaded from the archive that contains a board that is larger than 19x19 (#283). The game still cannot be loaded, but an error message is displayed instead of crashing.
- The app no longer crashes when the last game in the archive is deleted (#286)
- It is now possible to place a stone when viewing an old board position, even if the game has already ended (#278). It is thus possible to resume play at an earlier board position than the last.
- The user interface no longer rotates while a stone is being placed (#272)
- The status view now correctly displays "_color_ passed" when a computer vs. computer game is paused (#266)
- If the user attempts to make an illegal move, the status view now displays the intersection of the move (#261)
- The device statusbar at the top of the screen no longer disappears when some screens are displayed (#256)
- iPad only: The board is now rotated correctly even if it is not visible at the time that the device orientation changes (#255)
- A number of other bugs were fixed that may have caused crashes (#192, #284)
- Other minor bugfixes (#209, #257, #258, #262, #273)
1.1.2
2014-10-03
Version 1.1.2 is a bugfix release that contains the following changes:

Bugfixes
--------
- Interactive UI elements are now disabled while a stone-placing gesture is in progress (#243). This closes a loop hole that may have been the source for a number of crashes in the past (e.g. the crash described in #244)
- Stones no longer temporarily disappear from view while dragging a new stone (#245). Thanks to stfiend for reporting this bug.
- Fixed a potential crash if the computer player starts playing immediately after a game is loaded from the archive (#247).

Regressions
-----------
- It is now possible again to make a move when viewing an old board position while the game has already ended (#246). This will resume the game, discard all board positions beyond the one that the user is currently viewing, and then play the desired move.
1.1.1
2014-08-16
Version 1.1.1 is a bugfix release that contains an urgent fix for a crash that sometimes occurs while a stone is dragged around the board (#242).


The previous version 1.1.0 was a technical release that contains the following changes:

Improvements and changes
------------------------
- The app's user interface has been updated to the iOS 7 look & feel (#204)
- The "maximum zoom" user preference has been removed (#217)
- iPad: The "Game Actions" menu is now displayed in a popover (#232)
- The name of the "iPhone 4S" demo profile has been changed to "Strong" (#210)
- The "long press" gesture for placing a stone now has a slightly longer delay (#241). This should make it less likely that the user places a stone when instead she wanted to scroll.

Bugfixes
--------
- Drawing for Retina displays has been fixed (#205). Many thanks to Eric O. Lebigot for reporting the issue and giving me the necessary KITB to investigate the problem.
- The app no longer crashes when the "Score" segment is visible on the "Game Info" screen and player/profile information is edited (#225)
- The app no longer crashes when a player is viewed on the "Game" segment of the "Game Info" screen and the game ends (#226)
- The app no longer crashes when a saved game is renamed and the new name contains illegal characters (#235)
- iPad: The list of board positions now shows the correct move after discard & play (#233)
- iPhone: Potential app crash eliminated if user taps an entry in the list of board positions (#229)
- Handicap compensation is now shown in the "Game info" screen even if scoring mode is not enabled (#220)
- The "Minimum number of games" setting in the resign behaviour advanced settings screen is no longer editable if the "Auto-select" setting is turned on (#207)
- When the board is zoomed in or out, the internally managed zoom scale can no longer become lower/higher than the intended minimum/maximum (#139)

Regressions
-----------
- The "Load" button on the Archive tab is now disabled again while the computer is thinking (#227). This was broken when document interaction was introduced in 0.11.0.

Technical changes
-----------------
- Memory usage during zooming has been greatly reduced (#212, #214, #215)
- Memory usage for wooden background image has been reduced (#216)
- The project has been upgraded to the iOS 7 SDK (#204) and Xcode Xcode 5.1.1
- Support for iOS 6 has been dropped, the minimum required version is now iOS 7.0. Devices that are no longer supported are the iPhone 3GS and the iPod Touch 4th generation.
- The user interface now uses Auto Layout instead of manually calculated frames (#206)
- Unit tests were migrated from SenTestingKit/OCUnit to XCTest (#222)
- No longer use any .xib files, the entire UI is now set up programmatically
1.1.0
2014-08-14
Version 1.1.0 is a technical release that contains the following changes:

Improvements and changes
------------------------
- The app's user interface has been updated to the iOS 7 look & feel (#204)
- The "maximum zoom" user preference has been removed (#217)
- iPad: The "Game Actions" menu is now displayed in a popover (#232)
- The name of the "iPhone 4S" demo profile has been changed to "Strong" (#210)
- The "long press" gesture for placing a stone now has a slightly longer delay (#241). This should make it less likely that the user places a stone when instead she wanted to scroll.

Bugfixes
--------
- Drawing for Retina displays has been fixed (#205). Many thanks to Eric O. Lebigot for reporting the issue and giving me the necessary KITB to investigate the problem.
- The app no longer crashes when the "Score" segment is visible on the "Game Info" screen and player/profile information is edited (#225)
- The app no longer crashes when a player is viewed on the "Game" segment of the "Game Info" screen and the game ends (#226)
- The app no longer crashes when a saved game is renamed and the new name contains illegal characters (#235)
- iPad: The list of board positions now shows the correct move after discard & play (#233)
- iPhone: Potential app crash eliminated if user taps an entry in the list of board positions (#229)
- Handicap compensation is now shown in the "Game info" screen even if scoring mode is not enabled (#220)
- The "Minimum number of games" setting in the resign behaviour advanced settings screen is no longer editable if the "Auto-select" setting is turned on (#207)
- When the board is zoomed in or out, the internally managed zoom scale can no longer become lower/higher than the intended minimum/maximum (#139)

Regressions
-----------
- The "Load" button on the Archive tab is now disabled again while the computer is thinking (#227). This was broken when document interaction was introduced in 0.11.0.

Technical changes
-----------------
- Memory usage during zooming has been greatly reduced (#212, #214, #215)
- Memory usage for wooden background image has been reduced (#216)
- The project has been upgraded to the iOS 7 SDK (#204) and Xcode Xcode 5.1.1
- Support for iOS 6 has been dropped, the minimum required version is now iOS 7.0. Devices that are no longer supported are the iPhone 3GS and the iPod Touch 4th generation.
- The user interface now uses Auto Layout instead of manually calculated frames (#206)
- Unit tests were migrated from SenTestingKit/OCUnit to XCTest (#222)
- No longer use any .xib files, the entire UI is now set up programmatically
1.0.0
2014-01-09
Version 1.0.0 is a feature release that contains the following changes:

Features
--------
- When a new game is started, it is now possible to select one of several ko rules. Simple ko remains the default, new choices are positional and situational superko (#169).
- When a new game is started, it is now possible to select whether area or territory scoring should be in effect (#30). Area scoring is the default because the computer player (Fuego) does not properly support territory scoring.
- During scoring it is now possible to mark stones in seki (#190). Tap the "Actions" button to find the menu entry that lets you switch from "mark dead stones" to "mark stones in seki".
- It is now possible to display player influence, aka territory statistics, for an estimate who owns an area (#18). The feature can be enabled under "Settings > Display > Display player influence".

Other improvements and changes
------------------------------
- Some of the sections on the "Settings" tab have been re-organized (#132)
- Attempting to play an illegal move now displays the reason why the move is illegal (#182). Examples are suicide, ko or superko.
- When a new game is started and a handicap is selected, komi is adjusted automatically to 0.5 (#189)
- The computer player's strength has improved because a new version of Fuego has been integrated into Little Go. It is not possible to quantify the improvement against human opponents, but if the new and the old versions of Fuego play against each other, the new version wins 80% - 90% of the games.
- Use pattern-based additive knowledge on devices with more than 512 MB memory (#187).

Bugfixes
--------
- iOS 7: The app no longer crashes on startup after a game has been imported from an external app such as Mail or DropBox (#184)
- The app no longer crashes when game is loaded while "Game Info" screen is displayed (#191)
- The app no longer hangs after launch if it was previously suspended/killed during scoring (#203)
- The maximum zoom scale has been reduced to 2.0 for iPad devices, and to 2.5 for iPhone devices (#202). The previous maximum zoom scale 3.0 was too high, causing crashes on most devices.
- The next stone marker "A" is no longer displayed after all moves have been discarded (#200)
- The "Start of the game" board position table view cell no longer has a wrong background color (#199)
- The "Delete all games" button on the "Archive" tab is no longer affected by edit mode (#185)
- A sliding gesture no longer puts the entire "Players & Profiles" screen into edit mode (#175)
- A number of memory leaks were fixed (#188 and other, smaller fixes)

Technical changes
-----------------
- The project has been upgraded to Xcode 5.0 (#183)
- Support for iOS 5 has been dropped, the minimum required version is now iOS 6.1 (#198). Devices that are no longer supported are iPad 1st generation and iPod Touch 3rd generation.
- The 3rd party software build process has been completely rewritten (#92)
- All 3rd party software have been upgraded to newest versions (Fuego trunk r1728, Boost 1.55.0, MBProgressHUD 0.8, Cocoa Lumberjack 1.7.0, ZipKit 1.0.2, QuincyKit 2.1.9)
0.12.0
2013-09-11
Version 0.12.0 is a feature release that contains the following changes:

Features
-------
- It is now possible to configure the computer player with a threshold how quickly it will resign a game (#133). For instance, it is now possible to tell the computer player to never resign so that the game can be played out to the very end. This also allows beginners to play with a large handicap on a small board (up until now the computer player would always resign immediately when faced with an overwhelming handicap). The resignation behaviour setting can be found towards the bottom on the "edit profile" screen.
- When an old board position is viewed, the intersection where the next stone will be placed is now marked with the letter "A" (#101). This can be disabled in the "Board position" settings.
- Changes to the active profile are now immediately applied to the GTP engine (#123). For instance, it is now possible to change the playing strength or the resign behaviour of the computer player without starting a new game.
- At the bottom of the "Archive" tab there is now a button to delete all archived games in one fell swoop (#55)
- The tab order can now be customized (#57)
- Players & profiles can now be reset to their factory defaults (#54), in case some severe misconfiguration occurred
- Players & profiles can now be edited directly from the Game Info screen (#122)

Other improvements and changes
----------------------------
- Loading a game from the archive is now about 10% faster (#166)
- The user interface for changing the dangerous "Max. memory" profile setting is now vastly improved (#153). The maximum value that can be selected for the setting is now limited to a fraction of the device's physical memory, and the amount of physical memory that the device has is also displayed.
- When a computer player is edited, there is now a button that allows to directly edit the profile that the player is using (#71)
- When a profile is edited, the players that are using the profile are now listed at the bottom of the screen (#70)
- The button to reset predefined GTP commands is now clearly marked with a "red warning" style (#56)
- The "About" screen now displays the build date/time (#161)

Bugfixes
-------
- The GTP engine is configured to no longer recognize positional superko (#171). This is a temporary solution to bring the GTP engine's rules into sync with Little Go's rules. Little Go currently does not recognize superko, so this sync'ing fixes the problem that Little Go lets the user make a superko move which is then rejected by the GTP engine. Many thanks to Brid Griffin for emailing me a bug report that helped me with diagnosing this problem! Note that Little Go will officially support superko in 1.0.
- On the iPad, the board size is now correct after the device is rotated while the board is zoomed (#162)
- Dragging a stone outside the zoomed in board section no longer places the stone (#143)
- The computer player now resigns even if the profile setting "Max. games" is set to a value < 5000 (#154)
- Undo resign is no longer possible when viewing an old board position. This fixes the problem that undo resign when viewing an old board position corrupts the backup .sgf (#158).
- If the game has ended but an old board position is viewed, the status view now shows information related to the board position instead of end-of-game information (#107)
- Scoring mode is no longer activated automatically when a player resigns. The effect is that the status now reads "x has resigned" instead of the inappropriate "y wins by ..." (#4). If a score is desired it must be requested by manually activating scoring mode.
- The user can no longer place a stone on behalf of the computer player (#160)
- The board position can no longer be changed while Fuego is searching for an initial set of dead stones during scoring (#163)
- A number of potential app crashes have been eliminated (#130, #172, #173)
0.11.1
2013-05-22
Version 0.11.1 is a bugfix release that contains the following changes:

- Board position can no longer be changed while other commands are executed (#156). This hard-to-find bug caused numerous crashes (e.g. those described by issues #128 and #129) and other problems, such as the infamous "The computer played an illegal move." alert. Many thanks to Logan Bouia and Carole Wolf for emailing me bug reports that helped me with diagnosing the problem.
- The entire game is now saved when an old board position is viewed (#150)
- The app should no longer crash after receiving a memory warning on iOS 5 while the "Game info", "New game" or "Save game" screens are displayed (#157). Thanks to the anonymous iPad 1 user who patiently reminded me that the issue needs fixing by sending the occasional crash report.
- Fix for a memory leak in TableViewSliderCell (#155)
0.11.0
2013-04-24
Version 0.11.0 is a feature release that contains the following changes:

New features:
- Display coordinate labels (needs to be turned on under "Settings > Play view > Display coordinates")
- Display move numbers (needs to be turned on under "Settings > Play view > Display move numbers")
- Zoom and scroll the board. All standard zoom gestures are supported. Because zooming costs memory, it is recommended for users of the following older devices to limit the maximum zoom scale (under "Settings > Play view > Maximum zoom"): iPhone 3GS, iPad 1st generation, and iPod Touch 3rd/4th generation. You should set the slider to a middle position.
- Import/export game files from/to other apps on your device (e.g. Mail, DropBox)

Other improvements and changes:
- The application now launches much faster, except for the first time after upgrading from a previous version
- Status text and activity indicator are now displayed in the navigation bar at the top of the screen
- When a new game is started, the "discard old game" question is not displayed anymore if there have been no changes since the game was saved the last time
- Loading a game from the archive is now about 10% faster
- Drawing of Go board now makes better use of the available space. This is especially noticeable for the large 19x19 board on a small iPhone screen
- The "stone distance from fingertip" user preference now behaves more predictably: Previously a "clever" algorithm tried to figure out the "best" distance by taking into account various parameters such as board size and screen size. The new algorithm now simply scales a fixed maximum distance according to the value of the slider.

Bugfixes:
- No longer crash when a computer vs. computer game is restored during app launch and that game has already ended (#127). Thanks to Serge Grossenbacher for reporting this bug.
- No longer draw in secondary thread during app launch (#117). This eliminates another potential source of crashes.
- iPad only: Screen should no longer be flickering wildly after loading some games from the archive (#126).
- It is now possible to save games with a name that consists of 1 or 2 characters (#125).
- Resigning is no longer possible when viewing an old board position. This fixes the problem that resigning when viewing an old board position corrupts the backup .sgf (#115).
- During scoring, the activity indicator is now only displayed for finding the initial set of dead stones (#121).

Known bugs:
- App may crash when board position is changed (possibly forward going only) (#128)
- App crashes when user plays an illegal move while viewing an old board position (#129)
- App crashes during launch after a player has been deleted (#130)
0.10.0
2013-03-06
Version 0.10.0 is a feature release that contains the following changes:

Improve graphic design:
- Add wooden background
- Add artwork for black/white/cross-hair stones (instead of just drawing filled circles)
- New layout on iPad
- New icon for "continue" button in computer vs. computer games, to distinguish it from the new "forward" button

New features:
- View board positions for moves played earlier during the game
- Replace "undo" with "discard move"
- A game that has ended can now be resumed in two ways: 1) Discard the most recent move if two pass moves were played by mistake; 2) Select "Undo resign" from the game actions menu after accidentally resigning the game.
- Redesign of "New game" and "Game info" screens
- 3 new user preferences: 1) Settings > Play view > Stone distance from fingertip; 2) Setting > Board position > Discard future moves alert; 3) Settings > Scoring > Score when game ends
- Add support for collecting logging data. Turn this on under Diagnostics > Collect logging data. Logging data is automatically included when a bug report is submitted.
- Do not trigger the computer player when a computer vs. computer game is restored on app launch
- Add placeholder message to "Archive" tab if there are no saved games
- Various other small GUI updates and fixes

Bugfixes:
- App no longer crashes if a computer vs. computer game is paused and the computer passes or resigns
- Diagnostics > Bug report section is no longer disabled when computer player resigns
- Fix various memory leaks

Known bugs:
- The resigned state of a game is lost when a game is saved or loaded; this is not new in this release, it's just been added to the list of known bugs

Technical changes:
- Drop support for iOS 4.3, the minimum required version is now iOS 5.0
- Add iOS 6 compatibility
- Add iPhone 5 support
0.9.2
2013-01-04
Version 0.9.2 is a bugfix release that contains the following changes:

- Fix for crash if Play tab is not visible and low memory conditions occur (issue #86)
- Fix for crash if an error occurs while loading an archived game, e.g. because the game contains an illegal move (issue #88)
- Fix for crash when Little Go thinks that a move made by the computer player is illegal. Note that the root cause of the problem has not yet been identified, but at least the app no longer crashes when the condition occurs. Instead you will be asked to submit a bug report (please do!), the game in progress is automatically saved to the archive and a new game is started to bring the app back into a stable state. This temporary solution will remain in place until I can track down and fix the actual bug (issue #90).
- Fix for memory leak that occurs when the Game Info view has been selected on the Play tab, but the Play tab is not visible and low memory conditions occur (issue #87)
- Fix for memory leak when a bug report is sent (issue #91)
- Fix for GUI update errors on Play tab after an error occurs while loading a game (issue #89)

If you are interested in technical details about a specific issue, please visit GitHub: https://github.com/herzbube/littlego/issues.
0.9.1
2012-12-15
Version 0.9.1 is a bugfix release that contains only one change: The fix for an embarassing bug in the Ko detection logic. Thanks go to Valery Prikhodko and Horace Ho for reporting this.

----------------------------------------

For those users that are upgrading to 0.9.1 from an older version, here are the release notes for version 0.9.0: Version 0.9.0 was a feature release which also contained bugfixes. All new features are described in more detail in the in-game manual.

New features
------------
1) 3 new settings have been added to profiles (maximum number of playout games, maximum thinking time, ponder time). These settings provide much improved control over the computer player's playing strength.

2) Individual profile settings are now hidden in an "Advanced configuration" screen. You can still tweak those settings if you want to, but there is also a simplified "playing strength" screen where, by selecting a playing strength, you adjust several profile settings in a single action, without having to know the technical details behind each setting.

3) The computer player can now be interrupted when it is thinking.

4) You can now choose to send a crash report if the app crashes (available when the app is launched the next time after the crash). Settings are available on the "Diagnostics" tab.

5) You can now send send a bug report email with attached diagnostics information file from within the app. The function is available on the "Diagnostics" tab.

6) The Game Info view now displays the currently active profile.


Bugfixes
--------
1) Loading an .sgf file with bad content no longer crashes the app. Thanks to Andrew Hersee for reporting this bug.

2) iPhone only: The status line is now 2 lines high and no longer truncates texts. Thanks to Andrew Hersee for reporting this bug.

3) Improved protection against data loss after a crash (preferences data is saved more often, and the game in progress is saved after every move). Thanks to Tripp Lilley for reporting this issue.

4) It is no longer possible to enter empty profile and player names

5) iPad only: The Go board is now properly resized when the interface orientation changes while the "Play" tab is not visible

6) Display an error message when an illegal save game name is entered (instead of just silently not saving the game)


Technical changes
-----------------
1) The project's source code is now hosted on GitHub (https://github.com/herzbube/littlego/)

2) The project now has a Trello board where you can see what is currently being worked on (https://trello.com/board/little-go/4fd84c295027333d460dcc32)

3) An Ohloh page now provides mildly interesting source code statistics (https://www.ohloh.net/p/littlego)
0.9.0
2012-12-06
Version 0.9.0 is a feature release which also contains bugfixes. All new features are described in more detail in the in-game manual.

New features
------------
1) 3 new settings have been added to profiles (maximum number of playout games, maximum thinking time, ponder time). These settings provide much improved control over the computer player's playing strength.

2) Individual profile settings are now hidden in an "Advanced configuration" screen. You can still tweak those settings if you want to, but there is also a simplified "playing strength" screen where, by selecting a playing strength, you adjust several profile settings in a single action, without having to know the technical details behind each setting.

3) The computer player can now be interrupted when it is thinking.

4) You can now choose to send a crash report if the app crashes (available when the app is launched the next time after the crash). Settings are available on the "Diagnostics" tab.

5) You can now send send a bug report email with attached diagnostics information file from within the app. The function is available on the "Diagnostics" tab.

6) The Game Info view now displays the currently active profile.


Bugfixes
--------
1) Loading an .sgf file with bad content no longer crashes the app. Thanks to Andrew Hersee for reporting this bug.

2) iPhone only: The status line is now 2 lines high and no longer truncates texts. Thanks to Andrew Hersee for reporting this bug.

3) Improved protection against data loss after a crash (preferences data is saved more often, and the game in progress is saved after every move). Thanks to Tripp Lilley for reporting this issue.

4) It is no longer possible to enter empty profile and player names

5) iPad only: The Go board is now properly resized when the interface orientation changes while the "Play" tab is not visible

6) Display an error message when an illegal save game name is entered (instead of just silently not saving the game)


Technical changes
-----------------
1) The project's source code is now hosted on GitHub (https://github.com/herzbube/littlego/)

2) The project now has a Trello board where you can see what is currently being worked on (https://trello.com/board/little-go/4fd84c295027333d460dcc32)

3) An Ohloh page now provides mildly interesting source code statistics (https://www.ohloh.net/p/littlego)
0.8.1
2012-06-21
Version 0.8.1 is mainly a bugfix release. There are only two new things:

1) A spiffy new app icon, contributed by Daniel Máslo. To see more of Daniel's artwork pay a visit to his website http://www.danielmaslo.com/.

2) I am also pleased to announce that an elusive bug, which has plagued Little Go since before its first public release on the App Store, has finally been found and exterminated. Thanks to Andrew Hersee for reporting the issue, complete with instructions how to reproduce the bug.

The bug, in case you are interested to know more, was hiding in a low-level function and caused undo to not work correctly in certain situations. The error, when it manifested, did not have an immediate visible impact in the GUI, instead it caused all sorts of follow-up problems to occur (capturing stones might not work, suicide moves might be allowed, marking dead stones in scoring mode might not work correctly, and in some extreme cases it might even cause the app to crash).
0.8.0
2012-04-24
New features in this release:
- iPad version with support for retina display and all interface orientations
- iPhone now supports upside-down portrait orientation
- Improved in-game help

Optimizations (or, more adequately: fixes for things things that I don't admit were a bug):
- Loading a game is now much faster
- Drawing, especially while moving a stone around the board, now uses 10-15% less CPU power, which improves battery life

Bugfixes:
- Ko is no longer erroneously detected in certain situations (e.g. black has stones on A2, B1, B3, C1, C3, white has stones on B2 and C2; black now plays on D2, white on B2; in this situation, black C2 was erroneously thought to be illegal due to Ko)
- Profiles: "reuse subtree" is now always enabled (and cannot be disabled) when pondering is enabled; previously the two settings were independent of each other, which was a bug
- Loading a game, which involves creating a temporary file in the background, now works even if that temporary file already exists for some (weird) reason

Source code changes for the technically inclined:
- Rewrite of the Play view drawing code
- Lots of new unit tests
- Upgrade to iOS SDK 5.1
0.7.1
2012-01-09
Release of bugfix version 0.7.1
- loading a game with no moves is now handled correctly
(previously the app would hang and needed to be manually
killed to get into a usable state again)
- capturing moves that "almost" create a Ko are now
correctly recognized as legal moves (e.g. black A1,
white A2, black D1, white B2, black C2, white C1,
previously the black move on B1 was thought to be illegal)
- it is no longer possible to place stones outside the
board in the top-left and top-right corners
- board size 7x7 no longer allows handicaps greater than 4
(selecting such a handicap previously would result in no
handicap being set at all)
0.7.0
2011-12-23

Ways to hack Little Go

Download hacked APK

Download Little Go MOD APK
Request a Hack

Ratings

3.2 out of 5
109 Ratings

Reviews

Levithepuppy0869,
Outstanding (learn the setting)
While out of the box the computer will mercilessly defeat a beginner, this is a FREE amazing learning tool. You MUST read the instructions and understand how to adjust it to your skill level otherwise prepare for a very uneven match that will make the most stubborn challenger want to give up. After tweaking I found the features quite useful and the game is now addictive in ways i can only describe a three hours of satisfying gameplay I that was traded for sleep or time with my family.
ProdigiousMiguel,
Fun Learning Tool
As a beginner, I have a lot of fun with this app. Even on weaker difficulty, I really struggle to keep up with the AI, and that’s great. Anytime I mess up I will consistently get harshly punished and it has really opened my eyes to the weaknesses in certain play styles. I’ve learned so much from this app and I’ve gotten to watch the margin of loss drop more and more as I keep playing. Sometimes it is frustrating to lose all the time, but every game I learn something and get a little better.

I noticed that the game is open source, but I haven’t gotten a chance to check out the algorithms used. It surprises me that there isn’t a way to tweak the difficulty level to easier levels, as that’s usually pretty easy to do from a developer standpoint. I’ve read that Fuego uses MCTS to make its moves and there should be parameters one could tune to make playing a little easier.

Thanks again for this tool, its really great!
ShoobyTaylor,
MUCH TOO HARD, not fun at all
Give up. You're going to lose. You were going to lose within the first few moves. Even with the engine on the weakest setting, you are going to lose badly, very quickly, every single time. It is not fun at all. Don't even bother playing. You lose. And in case there are some random chance you might accidentally win, don't worry, the computer gives itself seven points ahead of you, even though you don't get a handicap with extra pieces to start like you're supposed to. Or, if you find a very well hidden the setting that allows you to get a couple of extra pieces is a handicap for the other player, the very first time you take one of its pieces, it simply resigns. So, I hope you like losing, and losing badly, because that is all that's going to happen in this game. If you think having even the slightest chance of winning is fun, forget it, because it will quit the minute it thinks there's even a tiny chance you will win. You lose.
screw nicknamesssssssssssss,
Great App
My favorite part about this app is how much you can customize & tweak. Overall, everything else about it is also pretty strong; display, UI, and even the manual is pretty clear/thorough. People whining about the AI being difficult don’t understand just how high the skill ceiling is for this board game, and even the weakest setting should still take some decent practice to overcome. Besides, if you’re constantly losing to the AI, then that’s a perfect opportunity to see what types of moves are being used to beat you — Look for patterns and adapt your strategy accordingly!!

To the developer(s): Very nice work. 5/5
Jvemp,
Best Free Go/Baduk App
This is the best free Go/Baduk app on iOS. From the graphical user interface, from all the customization options with scoring and AI difficulty.

I see with other reviews people are raging at the difficulty with the AI... but this is one of the few go apps/programs that even HAVE an AI difficulty setting. For newbs: set the ai to lowest difficulty and only play on smaller board sizes like 7x7, 9x9.

Really my only complaint is that I wish it had a windows program too, as this is excellent baduk freeware.
JDN_Vessel_of_Chaos,
Too hard for beginners.
I enjoy the game, but the computer is much to advanced for beginners, and the second I turn on a handicap the bot resigns on its first move. If there was some way to stop the bot from resigning, I would give it a 4/5, but as is the app is simply infuriating.

Edit: I found the setting to turn off AI resignation. It’s well hidden, but as promised I am changing my score to 4/5.
commissar1,
Very good app
This app is excellent. The AI is tough. But I followed some of the guidance about weakening it, gave myself a 5-stone handicap, and am enjoying some competitive games. The FAQs and the Help are fine; you have to dig around a little bit, but it’s not really difficult. I am a weak, novice Go player, and I find this app great fun. And there are a lot of options that I haven’t even looked at. I dumbed down Fuego as much as possible, changed the board to 19x19, and that’s about it.
Rkanecook,
Best go app I can find
This app has everything you need to play go. You can save games and play them back turn by turn. It's fully customizable, you can change the board size, the rules, who's black and white, ect. Yes the ai is incredibly difficult. I can spend hours on this app trying and failing to beat it. It's great practice for fighting real opponents and eventually you can find a way to beat the ai.
CrowOKC,
Useless to beginners
This game has no use for people trying to learn the game of Go. The AI is much too hard even at the easier setting. You will have lost the game by your this move without knowing why.
If you hope to learn how to play using the two computer setting that sets up a game with rude computer against itself, you will be disappointed because the game will start several moves in, which prevents you from seeing the early moves that set up everything else.
cosmotommy,
Use the Settings
There’s a lot of ways to play around with the level of difficulty, so you can make the computer as weak or as strong as you. It’s excellent. You make new computer characters that resign easy, or never resign, and you can have it as experienced as 1 game worth of knowledge, or thousands of games.