From 1ba662223a59d3c165928742910f3a85df7a0c01 Mon Sep 17 00:00:00 2001 From: bi0qaw Date: Sat, 25 Nov 2017 17:27:33 +0100 Subject: [PATCH] Created Coordinates (markdown) --- Coordinates.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 Coordinates.md diff --git a/Coordinates.md b/Coordinates.md new file mode 100644 index 0000000..236db54 --- /dev/null +++ b/Coordinates.md @@ -0,0 +1,22 @@ +Biosphere2 follows the coordinate system defined by Skript: +![](https://i.imgur.com/mVwngAR.png) + +Note that the Skript coordinate system is the same as the Minecraft coordinate system with ONE exception: The yaw of Minecraft goes from 0 to 180, then changes to -180 and goes back to -0. Skript does not have a negative yaw, instead it goes from 0 to 360. + +For comparison: + +Skript Coordinates|Minecraft Coordinates +---|--- +![](https://i.imgur.com/mVwngAR.png) | ![](https://i.imgur.com/7FHKE7f.png) + +You can generally also use the Minecraft coordinate system in Biosphere2. BUT Biosphere2 will ALWAYS return Skript coordinates. So you have to be careful when you deal with the yaw values of frames: +``` +set {_frame1} to frame with yaw -90 and pitch 0 +set {_frame2} to frame with yaw 270 and pitch 0 +``` +This creates two identical frames because a Minecraft yaw of -90 is identical to a Skript yaw of 270. But when you want to get the yaw of the frame it will always return 270: +``` +set {_yaw1} to frame yaw of {_frame1} +set {_yaw2} to frame yaw of {_frame2} +``` +{_yaw1} and {_yaw2} will both be 270. \ No newline at end of file