How to fixx Speed Function on 32bit :D

[~ExoduS~*]

DWORD dwPlayerPtr = *(DWORD*)ADR_PlayerPointer

switch( Speed )
{
case 0:*(float*)(dwPlayerPtr+Offset_Speed) = (-0.0f);break;
case 1:*(float*)(dwPlayerPtr+Offset_Speed) = (-50.0f);break;
case 2:*(float*)(dwPlayerPtr+Offset_Speed) = (-100.0f);break;
case 3:*(float*)(dwPlayerPtr+Offset_Speed) = (-150.0f);break;
case 4:*(float*)(dwPlayerPtr+Offset_Speed) = (-200.0f);break;
case 5:*(float*)(dwPlayerPtr+Offset_Speed) = (-300.0f);break;
case 6:*(float*)(dwPlayerPtr+Offset_Speed) = (-400.0f);break;
case 7:*(float*)(dwPlayerPtr+Offset_Speed) = (-500.0f);break;
case 8:*(float*)(dwPlayerPtr+Offset_Speed) = (-600.0f);break;
case 9:*(float*)(dwPlayerPtr+Offset_Speed) = (-700.0f);break;
case 11:*(float*)(dwPlayerPtr+Offset_Speed) = (-800.0f);break;
case 12:*(float*)(dwPlayerPtr+Offset_Speed) = (-900.0f);break;
case 13:*(float*)(dwPlayerPtr+Offset_Speed) = (-1000.0f);break;
}


need the offset addy look in my addy Thread

[AeroMan]

No offence, but you code D3D and can't fix this little issue?

On topic:
- WarRock Scans for memory modifications what basicly means is that this may get detected on some os.
- (-...0f) will slow down your speed and not increase it.
- If i where you i would do it diffrently, and also check if the playerpointer is activated.
- Case 0 is a default, what means if you function is off ( value 0 ) it will activate that case 0, i don't belive the value is "-0.0f".

[~ExoduS~*]

Thx Aeroman I will do it