variable resetting "randomly" - c++

Question

I am building a text based adventure game and I'm currently stuck on an issue.
I have a two variables that hold the values for the map(rooms) called x and y, I am changing them from a class and as soon as it exits the class code back to main it resets the values for x and y.
int x = 0, y = 0;
...
void IncreaseY(){
y++;
}
void MoveDirection(Direction direction)
{
switch (direction)
{
case North:
DecreaseY();
break;
case South:
IncreaseY();
break;
case East:
IncreaseX();
break;
case West:
DecreaseX();
break;
case None:
break;
default:
break;
}
}
...
class player{
void DoStuff()
{
MoveDirection(South);
}
}
...
void main()
{
Player player = Player.NewOrLoadCharacter();
player.doStuff();
}
This is most of the relevant code summarized.
I have stepped through the program using breakpoints and stepping several times and I am completely sure that as soon as I leave the Player class the variables x and y reset back to 0.
Question:
What could be causing the resetting of the variables x and y?
Note: This is an issue that just popped up since it has worked previously just fine.
edit: Source code: http://pastebin.com/uKS55LEZ
P.S.: I know the code is poorly written, I started with C++ moving from C# a week ago.

Answer 1

The code changed considerably since this answer was first posted, yet the problem is still actually a kind of mirage.
Here's what's happening at the current version of the code (the OP question does not represent this situation at the time of this writing):
In main, there is a Player declared thus:
Player player;
In a standard game loop, this code exists:
while( true )
{
ClearConsole();
Print(map.CreateMap(player));
map.doRoom(player);
}
This is greatly improved over earlier versions (much cleaner). There is one small problem causing the behavior described. It's the signature of the function doRoom (and this may apply to CreateMap, though I doubt it).
void doRoom(Player player)
This is a member of Room (in the loop above, that's map). The problem is that player is passed by value. This means a copy of player is made to provide the input parameter for doRoom. This copy is changed by doRoom (moving x and y, for example). When doRoom returns, the copy which it acts upon evaporates (falls from scope) - and the edited data goes with it.
Change the signature to
void doRoom(Player & player)
Now, the function takes a reference to player. There is no copy being made. As such, changes made to player are retained from one iteration of the loop to the next.
I said earlier this MIGHT apply to map.CreateMap, but that's true only if CreateMap modifies contents of player. If not, it wouldn't matter, but it would be technically slower to create a copy of player just to make the output CreateMap produces. It can take a reference, as I've suggested doRoom must take.
There is one other minor problem. The main loop above has no means of escape. There is no way to end the game. map.doRoom( player ) should probably return a bool, and perhaps if a false is returned, break the loop.