Updates for 3D positions and sizes; Bug fixes.
It would be a really good time to introduce actual Vec2 and Vec3 data types now if there is a transition from 2D position to 3D position anyways.
Needing 2 variables to store a position was already annoying enough.
It will get even worse now every time you want to store or send a position. Add size to it and you have to create 6 variables where you only need 2 in other software.
In Construct3 I have to do
update_object(pos_x,pos_y,pos_z,size_x,size_y,size_z)
instead of
update_object(position, size)
good point