#YES

The game is cheatable.

Like most software, the game is cheatable whenever there is a debugger available.

In this case, I have loaded up FireBug in Firefox, and learned a few tricks. Here's how the game is cheatable.

Note, this is based on playing the game from your source here:

• The game can be played here: http://www.zomis.net/codereview/memory/MemoryGWT.html

Process

1. Enable FireBug

2. Load the game (click the link)

3. In the 'Scripts' tab in Firebug, select script[9] and scroll to line 273. This is the JavaScript code used to populate your initial grid....:

   Which Scripts to debug

4. Enable a break point at about that line

5. Hit f5 to refresh the page. This should cause the page to partially load, and the break point will be where you set it....

6. Then, in the "Watch" tab we can inspect the ints array, which is the 'shuffled' collection of cell values that the grid is initialized with. Each member in the array documents the exact value which is placed at each location. This can be used to chose exact pairs without concern for mistakes.

   Cell Values

7. Profit?

##Notes

It took me a little while to track down exactly where the GWT content is stored, about.... 30 minutes to find FireBug, install, learn how it works, track down where things go, understand how GWT loads the scripts from an array of text which it loads separately, etc.

A person who is more familiar with JavaScript, the execution model in a browser, and the debug tooling could probably do it much faster.

The obfuscated code bases would make that harder, but the concept would still be the same.

YES

The game is cheatable.

Like most software, the game is cheatable whenever there is a debugger available.

In this case, I have loaded up FireBug in Firefox, and learned a few tricks. Here's how the game is cheatable.

Note, this is based on playing the game from your source here:

• The game can be played here: http://www.zomis.net/codereview/memory/MemoryGWT.html

Process

1. Enable FireBug

2. Load the game (click the link)

3. In the 'Scripts' tab in Firebug, select script[9] and scroll to line 273. This is the JavaScript code used to populate your initial grid....:

   Which Scripts to debug

4. Enable a break point at about that line

5. Hit f5 to refresh the page. This should cause the page to partially load, and the break point will be where you set it....

6. Then, in the "Watch" tab we can inspect the ints array, which is the 'shuffled' collection of cell values that the grid is initialized with. Each member in the array documents the exact value which is placed at each location. This can be used to chose exact pairs without concern for mistakes.

   Cell Values

7. Profit?

Notes

It took me a little while to track down exactly where the GWT content is stored, about.... 30 minutes to find FireBug, install, learn how it works, track down where things go, understand how GWT loads the scripts from an array of text which it loads separately, etc.

A person who is more familiar with JavaScript, the execution model in a browser, and the debug tooling could probably do it much faster.

The obfuscated code bases would make that harder, but the concept would still be the same.