[CoolJosh3k]

I am working on a rather complex plugin, but my experience is not what I would like it to be yet. So question:

What code can I use to set a players velocity?

I am able to provide the direction, speed and duration. I also have client id and timer setup, but I lack enough understanding of editing entity data.

[NIGathan]

PHP Code:

// To get the player velocity:
new Float:vec[3];
GetEntPropVector(client, Prop_Data, "m_vecVelocity", vec);

// Here we can modify the data in the array
vec[3] = 300.0; // Raise the player 300 units upward.

// Then to set the players velocity we will do:
TeleportEntity(client, NULL_VECTOR, NULL_VECTOR, vec); 


[GsiX]

Originally Posted by NIGathan PHP Code: // Here we can modify the data in the array vec[3] = 300.0; // Raise the player 300 units upward.

vec[2] = 300.0;

[CoolJosh3k]

Thankyou, I will try this. Didn't realize you could set it using a teleport input. Clever.

[shavit]

That works too, confirmed;

/**
 * Sets the Base velocity of an entity.
 * The base velocity is the velocity applied
 * to the entity from other sources .
 *
 * @param entity        Entity index.
 * @param vel            An 3 dim array
 * @noreturn
 */
stock Entity_SetBaseVelocity(entity, const Float:vec[3])
{
    SetEntPropVector(entity, Prop_Data, "m_vecBaseVelocity", vec);
}

/ smlib

[CoolJosh3k]

Originally Posted by shavit That works too, confirmed; /** * Sets the Base velocity of an entity. * The base velocity is the velocity applied * to the entity from other sources . * * @param entity Entity index. * @param vel An 3 dim array * @noreturn */ stock Entity_SetBaseVelocity(entity, const Float:vec[3]) { SetEntPropVector(entity, Prop_Data, "m_vecBaseVelocity", vec); } / smlib

This looks like a much better way to do it. The kind of thing I was thinking of, but thought the engine would not allow it.

Thanks for this :)

[NIGathan]

Originally Posted by GsiX vec[2] = 300.0;

Oh wow... Whoops.

[CoolJosh3k]

Been writing some code and testing things, in which I found some interesting results.

in m_vecBaseVelocity based on the 3 possible vectors...

'x' will move you towards the positive y direction if your y eye angle is in the Quadrants 1 or 2 (0 to +180), but negative direction if your angle is in the Q3/Q4 (-180 to 0)

'y' will move you towards the x direction when your eye angle is Q1/Q4 (-90 to +90) and reversed for the other 2 quads

'z' will actually move you toward whatever direction you are already moving.

EDIT: Later testing with this, seem to send the player in the expected way. -100 sends the player towards the negative x direction. Unsure why my results changed.

All of these only work when the client in moving in both the horizontal and vertical planes. It also appears to ramp up the speed, rather than directly setting it.

[GsiX]

I m not sure about all this stuff but I think it depend on how the map being constructed will defined your origin and angle.

[NIGathan]

By x,y, and z do you mean 0,1, and 2 relatively?

Also I believe setting the m_vecBaseVelocity will alter the m_vecVelocity based off what you give it. It won't actually change it to what you set. So for example:

m_vecVelocity is currently 42,42,0.
If you change the m_vecBaseVelocity to -42,-42,0 then the player will actually have no velocity at all.

If you are trying to actually set the velocity then set m_vecVelocity.