[Netsys]

I can not find the m_flPainShock ( 108 ) offset in the gamedata, where is it?

[PartialCloning]

It's probably m_flVelocityModifier. I didn't even know you could use gamedata in plugins, I thought it was just for reference. Can you give an example of how you're using it?

[Netsys]

Get the hitgroup: get_ent_data(iVictimID, "CBaseMonster", "m_LastHitGroup")
Get user weapon entity: get_ent_data_entity(iMessageEntity, "CBasePlayer", "m_pActiveItem")

Fire rate:

set_ent_data_float(iEntityID, "CBasePlayerWeapon", "m_flNextPrimaryAttack", 0.6);
set_ent_data_float(iEntityID, "CBasePlayerWeapon", "m_flNextSecondaryAttack", 0.6);
set_ent_data_float(iEntityID, "CBasePlayerWeapon", "m_flTimeWeaponIdle", 0.6);

[PartialCloning]

Oh, that's cool, thanks. Did m_flVelocityModifier work? If not try m_flFlinchTime or wait for Arkshine to reply. I couldn't find it either but my guess is it's one of those two.

Edit: Unless he actually forgot to add it, and didn't rename it.

[Netsys]

I think its m_flVelocityModifier

[PartialCloning]

Yeah that's what I figured but m_flFlinchTime sounded like a name that could have repalced m_flPainShock. Anyway, do you know what this means:

"m_pActiveItem" // CBasePlayerItem* { "type" "classptr" "windows" "1492" "linux" "1512" "mac" "1512" }

What's the CBasePlayerItem supposed to mean when it's in CBasePlayer?

[Arkshine]

All offsets have been dumped from the binary. So, those are the original names. If you don't find it, just search by its value (108*4 to get char-based value).

The comment is the member type. m_pActiveItem is a member of type pointer to CBasePlayerItem class.
Basically an entity index (a player's active item), that you would use before get_pdata_cbase to get its value.

@Netsys, don't forget your other thread.

[klippy]

It's just a comment for reference. Says that m_pActiveItem is a pointer to a CBasePlayerItem object, which is just any weapon.

EDIT:
Arkshine quicker and more detailed... Oh well.

[PartialCloning]

Alright, thanks. But is using the new natives better than using get_pdata..? I know it says safer, but is it slower?

[klippy]

Originally Posted by PartialCloning Alright, thanks. But is using the new natives better than using get_pdata..? I know it says safer, but is it slower?

It probably is slower (Arkshine, correct me if I'm wrong), but you probably aren't going to notice any difference. Other than being safer and slower, it's probably easier to deal with. Use new natives if it's not any time-critical code, like forwards that are called per-frame (pfnPreThink, pfnAddToFullPack, etc).

But if you do have to use old natives for performance, looks like you can use them in combination with the following native (just found out this native a few minutes ago):

PHP Code:

native find_ent_data_info(const class[], const member[], &FieldType:type = FIELD_NONE, &arraysize = 0, &bool:unsigned = false); 


This should save you from hardcoding offsets into your plugin.