Hey there! If your code seems to be working ok, that's the most important thing - but I think I see a few nasty bugs (and a few ways to clean up the code, while I'm at it).


if(moveRight == true && moveLeft == false)
{
if (xVel <= maxSpeed)
{
xVel = int(0.40 * speedTimes);
speedTimes +=1;
}
}
if(moveRight == false && moveLeft == true)
{
if (xVel >= (maxSpeed * -1))
{
xVel = int(-0.40 * speedTimes);
speedTimes +=1;
}
}


You can, in theory, switch between these two instantly. Since you reset speedTimes only if there is a frame where the left and right are both pressed or both unpressed, if someone were to release right and hit left at such a time that the code below isn't executed, your xVel would invert itself entirely, causing the object to fly off in the other direction.

(A clever person could also abuse this to get arbitrarily high speeds, as speedTimes is incremented each time the trick is pulled off)


if(moveRight == false && moveLeft == false)
{
if(xVel >0)
{
speedTimes = 1;
xVel = -0.20;
}
if(xVel <0)
{
speedTimes = 1;
xVel = +0.20;
}
}
if(moveRight == true && moveLeft == true)
{
if(xVel >0)
{
speedTimes = 1;
xVel = -0.20;
}
if(xVel <0)
{
speedTimes = 1;
xVel = +0.20;
}
}


First off, you can simplify this. The bodies of the conditionals are the same, and you can test for both conditionals at once by seeing of moveRight and moveLeft are the same.

But, this doesn't seem to be what you want. If the person lets go of the keys, then xVel will be set to a constant - no matter how fast they were going, it'll be set. I suspect you want something more along the lines of xVel-=0.20;, as that will cause slowing down instead of instantly changing the speed to a constant.

Also, you set xVel to a negative value if it's positive, then have an if (xVel<0) clause right afterwards. That'll get triggered even if it's positive, since it will pass through the if(xVel>0) loop first, which will set it to a negative value. I suspect an else if clause was what was meant.

Though, even if you do all that, you'll still be vulnerable to the glitch in the other part of the code - pressing left or right will instantly set the velocity to that direction, regardless of your prior direction. In fact, every time you change xVel, you change it to a constant or a multiple of another variable (speedTimes) which is actually independant. I would not recommend that - set it based on its own value. It's easier and far less likely to end up with bugs like the directional switching one. I'd probably rewrite the thing like this:


if (moveRight == moveLeft)
{
if (xVel>0)
xVel-=1;
if (xVel<0)
xVel+=1;
}
else if (moveRight && xVel<maxSpeed)
{
xVel+=2;
}
else if (moveLeft && xVel>(maxSpeed * (-1)))
{
xVel-=2;
}


You could also use xVel as a float, and cast it as an int when using to to physically move the object. I just chose to make it an int here so I wouldn't have to deal with rounding errors (like it possibly never actually hitting zero and thus oscillating when moveRight==moveLeft).