Skip to content

Glacier_PlayerVariables

Daniel Hunter edited this page Mar 18, 2020 · 5 revisions

ZHitman3 contains a API for player variables manipulation.

As an example the ZMovementControl class (Which is derived from ZHitman3) implements two methods for setting up player variables.

A reversed variables list is below:

Boolean

Player

m_bChangingClothes

m_bChangingClothesAllowed

m_bSneaking

m_bStrangulating

m_bInjecting

m_bPunching

m_bPushing

m_bClimbingHatch

m_bLockPicking

m_bNightVisionEnabled

m_bBinocularsEnabled

m_bFacingEnabled

m_bIsInMotion

m_bIsRunning

m_bIsWalking

m_bIsCrouching

m_bIsSneaking

m_bIsOnLadder

m_bIsOnGuide

m_bForceCrouch

m_bDragPosForced

hasAimTargetCallBack

m_bDisableMovement

m_bStrafeModeActive

m_bNoTurnStrafeMode

m_bForceFaceCamera - First person camera enabled?

Weapon control

m_bDualActionEnabled

m_bHumanShieldAimModeActive

m_bFireTargetCallBackWait

m_bFireLock

Integer

Weapon control

m_iNrAmmoProjectiles

m_iPrevProjectilesInMagazine

m_iProjectilesInMagazine

m_iNumberOfAmmoClips

Float

m_fInjectingTime

m_fMovementSpeedPrc

m_fTurnToWalkAngle

Weapons control

m_fTargetDistance

Enum (?)

Player

m_eRoomZone

m_eCustomZone

Pointer

Weapon control

m_pAimLastTarget

Possible unused

Player

m_RailInfo.pRailGeom

m_RailInfo.vP1

m_RailInfo.vP2

m_RailInfo.vP3

m_RailInfo.vColiPt

Time

Weapon control

m_ttLastAttackTime