Hundreds of features to explore
Games made in Construct
Your questions answered
Popular & trusted by schools and Universities world-wide
Construct 3 runs in the browser & works offline
Students do not need accounts with us
Our educational partners
Free education resources to use in the classroom
World class complete documentation
Official and community submitted guides
Learn and share with other game developers
Upload and play games from the Construct community
Game development stories & opinions
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.
To further illustrate the redundancy, imagine if Sprite.X read as Sprite.HotSpotX in expressions.
Develop games in your browser. Powerful, performant & highly capable.
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.