Maybe I'm misunderstanding what you're getting at, but just putting MathHelper.Clamp() in the declaration of your Vector2 won't do anything afterwards.  If you want to keep the values in that range, you should insert the following at the appropriate place in your code, in the Update() method or wherever: ...

If somebody steals your code and re-skins it, take them to court.  Problem solved.

It would help if you gave us some more specific information, but it sounds like what you're seeing is the overscan (i.e. drawing outside the visible section of the screen) of your television.

I really like the idea of becoming any character you meet, and if it's done well, it could be a really interesting game mechanic that I don't think I've seen in an RPG before (reminds me a bit of Suikoden, I suppose, but to a greater degree). I'm not wild about the art, but my project at the moment is 100% programmer art, so ...

It's hexadecimal (base-16) notation.

I just played it for a few minutes and had a lot of fun with it!  Keep us posted on updates.

It seems like a better (or, at least, more practical) idea would be to simply create bounding circles / rects / polygons for the sprites ahead of time and work from there.  Creating the paths from the texture data at runtime and then turning that into something useful seems, to me at least, to be more trouble than its worth for what ...

I'm getting pretty scared that my 2nd XBox is going to RROD before too long.  It's starting to freeze up every once in a while, and it was about two months after that started that my 1st one RRODed.  Ugh.

1.  All you have to do to slow down the fall is to scale back on the your object.Acceleration.  It's an arbitrary number you've chosen, so simply make it smaller. 2.  If you're orienting everything in the same direction as it appears on the screen, jumping should impart a negative velocity, not a positive one.

I, for one, am excited about turning in a non-trivial submission this time around.