List of available moves in 2 x 2 dungeon game. How this is possible?

Logically thinking you're right, but it's not the way that program is written. It removes some move choices only if one of the player's coordinates is equal to the edge of the board. If your outside the board, your coordinates is "more than edge", so following the logic of the program, the move stays as an available option. The program simply doesn't think it's possible to be outside the board. In my opinion it should be corrected, but that's actually not the main topic of this particular section of the course.

I though this was the case as well however if you correct the test to use the coordinates (0, 1) which would be within the bounds of the game grid the function still returns ['RIGHT', 'UP', 'DOWN'] as possible options.

To figure out what was going on I used pdb (Python Debugger) to step through the code as it was executing. It turns out the new GAME_DIMENSIONS variable we set in the unit test (or in the python shell as shown below) is not used by the function and it is instead reading the original values set in dd_game.py

Here is my output when running the code through pdb:

Python 3.6.3 (v3.6.3:2c5fed8, Oct  3 2017, 17:26:49) [MSC v.1900 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import pdb
>>> from dd_game import get_moves
>>> GAME_DIMENSIONS = (2, 2)
>>> get_moves((0, 1))
> d:\projects\python\python testing\dungeon\dd_game.py(70)get_moves()
-> x, y = player
(Pdb) n
> d:\projects\python\python testing\dungeon\dd_game.py(71)get_moves()
-> moves = ['LEFT', 'RIGHT', 'UP', 'DOWN']
(Pdb) x, y
(0, 1)
(Pdb) GAME_DIMENSIONS
(5, 5)

Whilst I did step through some more of the function the useful information is all here. You can see that it is registering the position of the player correctly however the values returned for GAME_DIMENSIONS is that of the variable as it is set in dd_game.py and not as we set it prior to running the function.

Now, can anyone explain why our variable is ignored? I'm sure there's a simple explanation but it'd be great to hear from an authority.

Thanks, Alex

Someone already mentioned about this in the previous questions. I'm not sure if there's an error in the video, or was it intentional.

First, Kenneth forced grid size to 2x2, then he set the player's position to be (0,2) - remember that it's 0-based location, so actually the player is now outside the board. That's why the moves has three choices instead of two - the player actually isn't in the corner.

In case anyone is interested someone has answered this here: https://teamtreehouse.com/community/how-could-the-player-possibly-move-up-python-testing