|
Originally Posted by RyDeR`
 DeleteBadWorld? Anyway. I made a similar function which will work a lot faster and do the same thing:
pawn Code:
pawn Code:
|
|
Originally Posted by Nero_3D
Cant it be improved if we leave strcat out and pass the address directly to strfind ?
|
#define PI 3.14159265
stock Float:ToRadian(Float:Degrees)return Degrees*(PI/180);
//This was set for On Foot Recording Files usage, maybe be different when used with something else
stock EulerToQuaternion(Float:angle,&Float:w,&Float:x,&Float:y,&Float:z) //Angle = Z rotation
{
new Float:c1,Float:c2,Float:c3,Float:s1,Float:s2,Float:s3;
c1=floatcos(0.0); //"Heading" -- Just guessing, but I think X rotation goes here
c2=floatcos(ToRadian(angle)/2); //"Attitude" -- Definitely Z
c3=floatcos(0.0); //"Bank" -- Possibly Y rotation
s1=floatsin(0.0);
s2=floatsin(ToRadian(angle)/2);
s3=floatsin(0.0);
w=(c1*c2*c3)-(s1*s2*s3);
x=(s1*s2*c3)+(c1*c2*s3);
y=(s1*c2*c3)+(c1*s2*s3);
z=(c1*s2*c3)-(s1*c2*s3);
}
|
Originally Posted by Joe Staff
Not sure if already posted, but here are 2 functions/formulas that I direly needed.
pawn Code:
|
|
I just copied this out of my gamemode, change it how you like. |
|
Originally Posted by Lorenc_
ANTI-CAR WARP
Fags be car warping, I just copied this out of my gamemode, change it how you like. Just make sure you don't use PutPlayerInVehicle too fast, or you can even simply just hook: p_CarWarpTime[ playerid ] = gettime( ) + 1; to those functionsThe average car jack per vehicle is around 400ms (0.4 seconds), the highest I've caught to was 634ms. It's good to be safe than sorry, so I've now set it to 1 second. It's barely possible to enter more than two vehicles in under two seconds anyway, as previously with two seconds. It was possible to enter two cars within 2 seconds. Version 0.3 - NEW pawn Код:
|
|
Originally Posted by Pizzy
I made this around 2 weeks ago and posted it in the filterscripts section, however it got removed for no specific reason.
I'm guessing you got the idea from me? |
GetWeaponModel(weaponid)
{
switch(weaponid)
{
case WEAPON_BRASSKNUCKLE: return 331;
case WEAPON_GOLFCLUB: return 333;
case WEAPON_NITESTICK: return 334;
case WEAPON_KNIFE: return 335;
case WEAPON_BAT: return 336;
case WEAPON_SHOVEL: return 337;
case WEAPON_POOLSTICK: return 338;
case WEAPON_KATANA: return 339;
case WEAPON_CHAINSAW: return 341;
case WEAPON_DILDO: return 321;
case WEAPON_DILDO2: return 322;
case WEAPON_VIBRATOR: return 323;
case WEAPON_VIBRATOR2: return 324;
case WEAPON_FLOWER: return 325;
case WEAPON_CANE: return 326;
case WEAPON_GRENADE: return 342;
case WEAPON_TEARGAS: return 343;
case WEAPON_MOLTOV: return 344;
case WEAPON_COLT45: return 346;
case WEAPON_SILENCED: return 347;
case WEAPON_DEAGLE: return 348;
case WEAPON_SHOTGUN: return 349;
case WEAPON_SAWEDOFF: return 350;
case WEAPON_SHOTGSPA: return 351;
case WEAPON_UZI: return 352;
case WEAPON_MP5: return 353;
case WEAPON_AK47: return 355;
case WEAPON_M4: return 356;
case WEAPON_TEC9: return 372;
case WEAPON_RIFLE: return 357;
case WEAPON_SNIPER: return 358;
case WEAPON_ROCKETLAUNCHER: return 359;
case WEAPON_HEATSEEKER: return 360;
case WEAPON_FLAMETHROWER: return 361;
case WEAPON_MINIGUN: return 362;
case WEAPON_SATCHEL: return 363;
case WEAPON_BOMB: return 364;
case WEAPON_SPRAYCAN: return 365;
case WEAPON_FIREEXTINGUISHER: return 366;
case WEAPON_CAMERA: return 367;
case WEAPON_PARACHUTE: return 371;
default: return 0;
}
}
/*
What's this CLEO?
This cleo demolishes your closest players that are in vehicles.
It sends them so far away, that your screen is completely ruined.
What's the fix meant to do?
Most players tend to relog inorder to fix this. Players then would
report this a bug in your bug report board within your server forums.
This stops that spam and also adds a SA-MP like client message to
indicate that it's just a SA-MP issue.
As people just relog to fix the issue, this just slays them two times
and the issue is automatically resolved once you're spawned. No more
hassle with relogging just because of a cruel person!
Minor Information:
X Y Z
999999.875000 | 10000000.000000 | 1410065408.000000
(999999.9) (1e07) (1e10)
This is the debug information I've got.
*/
new
Float: p_PlayerBuggerX[ MAX_PLAYERS ],
Float: p_PlayerBuggerY[ MAX_PLAYERS ],
Float: p_PlayerBuggerZ[ MAX_PLAYERS ]
;
public OnPlayerUpdate( playerid )
{
static
Float: X, Float: Y, Float: Z
;
GetPlayerPos( playerid, X, Y, Z );
if( X >= 99999.0 || Y >= 99999.0 || Z >= 99999.0 || X <= -99999.0 || Y <= -99999.0 || Z <= -99999.0 ) {
SendClientMessage( playerid, 0xa9c4e4ff, "Warning: Excessive X, Y, Z has been breached thus last location set." );
SetPlayerPos( playerid, p_PlayerBuggerX[ playerid ], p_PlayerBuggerY[ playerid ], p_PlayerBuggerZ[ playerid ] );
}
else
{
p_PlayerBuggerX[ playerid ] = X;
p_PlayerBuggerY[ playerid ] = Y;
p_PlayerBuggerZ[ playerid ] = Z;
}
return 1;
}
static Float:x, Float:y,Float:z;
GetPlayerPos(playerid, x, y, z);
if(x > 0xdbb9f && y > 0xdbb9f && z > 0xdbb9f) {
SendClientMessage(playerid, -1, "[Suspeita] Hacking de bugar jogadores detectado");
SetPlayerPos(playerid, GetPVarFloat(playerid,"xposSet"), GetPVarFloat(playerid,"yposSet"), GetPVarFloat(playerid,"zposSet"));
}
else {
SetPVarFloat(playerid,"xposSet", x);
SetPVarFloat(playerid,"yposSet", y);
SetPVarFloat(playerid,"zposSet", z);
}
|
@Drakins it would make much more sense to use regular variables, PVars are slower so it's a waste to use them in OnUpdate. |
|
And why hex values? In this context seems a bit useless, makes it harder to read... |
)
