Quote:
Originally Posted by cbk1994
It's a problem because it's not documented and it didn't happen in v5. From what I understand about it, it's also a problem because he's drawing on the tile layer, therefore the coordinates should be relevant to tiles. The only way to fix it would be to add GraalControl.y / 16 to the y you're drawing at, which is nasty if GraalControl's y is not a multiple of 16.
|
Probably better to use things like
worldx() and
worldy() for that, perhaps with
GraalControl.globaltolocalcoord() if needed, so that you do not need to really worry about whether the
GraalControl's position is a multiple of 16 or not.