Is it necessary to have to use sprite.ImagePointX(2), to refer to the X position of an image point? Couldn't it just be sprite.X(2)? And if the brackets aren't there then it means (0)?
That WOULD be pretty nice, actually, since I have some pretty lengthy lines filled to the brim with "ImagePointX" and "ImagePointY" over and over. On the other hand, it's a little less intuitive for people who don't know about it.
Develop games in your browser. Powerful, performant & highly capable.
To further illustrate the redundancy, imagine if Sprite.X read as Sprite.HotSpotX in expressions.
Some users have requested the ability to translate co-ordinates between layers. That might be a better candidate for a parameter to the X and Y expressions.