Issue with direction values (1.16.5)

[Babelincoln1809]

Hi, I'm making an item class that when releasing a right click it'll do a "slam attack". I had it working fine, but one big issue arose. The slam's distance is affected by the Y facing axis, so if the player is looking up or down the slam goes nowhere. I'm trying to find a method to where only the X and Z facing values are used, not the Y. I tried using the player's rotation, which did get rid of the Y issue, but lead to inaccurate slams. Any help is much appreciated!

 

Here's the "slam attack" code: https://pastebin.com/sh1LdNWZ

Edited July 27, 2021 by Babelincoln1809

[poopoodice]

  Quote

Vector3d look = user.getLookAngle();

Expand  

Gets the normalized vector from player's pitch and yaw, so a simple way would be change the pitch to the horizontal value (I think it is 0), get the angle, and then change it back. Otherwise just do some simple trig...

[Luis_ST]

just ignore the y value? and use only the x and z values for your attack

[Babelincoln1809]

  On 7/27/2021 at 11:47 PM, poopoodice said:

Gets the normalized vector from player's pitch and yaw, so a simple way would be change the pitch to the horizontal value (I think it is 0), get the angle, and then change it back. Otherwise just do some simple trig...

Expand  

So far I have this, but only fires in one direction

[Draco18s]

  Quote

new Vector3d(x, z, y);

Expand  

👀

[Babelincoln1809]

  On 7/28/2021 at 8:52 PM, Draco18s said:

👀

Expand  

Please tell me that means I'm close lololol 👀👄👀

[Draco18s]

No:
Why are you pushing the Z and Y values in the wrong order?

[Babelincoln1809]

  On 7/28/2021 at 10:11 PM, Draco18s said:

No:
Why are you pushing the Z and Y values in the wrong order?

Expand  

I saw some old forum saying to swap them cause of how Y is coded

[poopoodice]

Well... just simply something like 

pitch = player.pitch

player.pitch = 0

vec = player.getLookVec

player.pitch = pitch 

 

Should work, I guess.

 

 

 

 

 

 

 

[Draco18s]

  On 7/29/2021 at 12:26 AM, poopoodice said:

pitch = player.pitch

player.pitch = 0

vec = player.getLookVec

player.pitch = pitch 

Expand  

Or, more sensibly:

vec = player.getLookVec
vec.y = 0

[poopoodice]

  On 7/29/2021 at 1:44 AM, Draco18s said:

Or, more sensibly:

vec = player.getLookVec
vec.y = 0

Expand  

But if I understand it correctly, the getLookVec returns the normalized vec, means the value of y will affect the distance of x and z.

[Babelincoln1809]

  On 7/29/2021 at 1:44 AM, Draco18s said:

Or, more sensibly:

vec = player.getLookVec
vec.y = 0

Expand  

What if instead I used a Quaternion based off the player's direction and rotation instead of using a Vector3D?

[Luis_ST]

  On 7/29/2021 at 12:26 AM, poopoodice said:

pitch = player.pitch

player.pitch = 0

vec = player.getLookVec

player.pitch = pitch 

Expand  

why you don't use that?

[Draco18s]

  On 7/29/2021 at 3:31 AM, poopoodice said:

But if I understand it correctly, the getLookVec returns the normalized vec, means the value of y will affect the distance of x and z.

Expand  

So... renormalize the vector...

https://www.khanacademy.org/computing/computer-programming/programming-natural-simulations/programming-vectors/a/vector-magnitude-normalization

Edited July 29, 2021 by Draco18s

[Babelincoln1809]

  On 7/29/2021 at 1:44 AM, Draco18s said:

Or, more sensibly:

vec = player.getLookVec
vec.y = 0

Expand  

So I have this, but x and z are still being affected by the y value

[poopoodice]

If the code does not even compile, how do you know it's not working?

They are final in 1.16.

[Babelincoln1809]

  On 7/30/2021 at 3:35 AM, poopoodice said:

If the code does not even compile, how do you know it's not working?

They are final in 1.16.

Expand  

I've tried other ways of setting it to zero, but those ways have just given me the same result