[ferenz]

It uses the correct xyz coordinates from the client, in which y is height. All official lua from the main behavior framework treat y as height, and all API functions the bot regard y as height also. MAHA switched the y/z values because I guess people have a hard time accepting y as height...it's not my personal favorite choice because it confuses users in exactly the way you've experienced, but addon developers are free to implement functionality however they choose.

Ah ok. That's my bad then. I thought that the main framework treats y as normal y, and h as height. It's not a problem, it's just a bit annoying to transcribe stuff from the tp files for maha into this, as we need to keep it in mind.

That is indeed a valid concern. I will most likely modify the TP module we added to the dev code to use y for height instead of z. We used MAHA's code for that module also and I did not switch the y/z values back (due to pure laziness). Actually now that I think about it, I may add a button to the Dev - TP module that spits out a correctly formatted position table to the console so that you can simply copy and paste it into your profile. That seems like the optimal solution.