cClientInfo

[mo3ad001]

cClientInfo

class cClientInfo
{
public:

char _0x0000[4];
	__int32 Index; //0x0004 
char _0x0008[8];
	char pName[12]; //0x0010 
char _0x001C[12];
	int* Object; //0x0028 
	__int32 pKills; //0x002C 
	__int32 pDeaths; //0x0030 
char _0x0034[48];
	__int32 pFTMission; //0x0064 
char _0x0068[8];
	__int32 pTeam; //0x0070 
char _0x0074[4];
	BYTE pIsDead; //0x0078 
char _0x0079[319];
	__int32 pRank; //0x01B8 
char _0x01BC[80];
	__int32 pFTScore; //0x020C 
	BYTE pFTSpawn; //0x0210 
char _0x0211[3];
	__int32 pFTLongestLife; //0x0214 
	__int32 pFTKill; //0x0218 
char _0x021C[88];
	cClientInfo* PlayerNext; //0x0274 


};//Size=0x0278

Note : i reversed it by using eu files so i think na have it too

~Mo3ad001

[ISmokeWeedAmICoolNow]

why do you put "p" in front of some members but not others?

[Jason]

why do you put "p" in front of some members but not others?

Usually the "p" prefix indicates that the variable is a "pointer". It's present with types as well

PBYTE
PVOID

...etc

It's just a common notation.

[ISmokeWeedAmICoolNow]

Usually the "p" prefix indicates that the variable is a "pointer". It's present with types as well

PBYTE
PVOID

...etc

It's just a common notation.

yes thats what i was thinking, but if you look at his class he puts it in front of integers and bytes

[S0aD]

No Changes?

[mo3ad001]

No Changes?

it's changed , playerNext and Missions !

[freedompeace]

Usually the "p" prefix indicates that the variable is a "pointer". It's present with types as well

PBYTE
PVOID

...etc

It's just a common notation.

That's Microsoft notation , which is gay. Yay let's introduce 10000 more types into this ! TCHAR, PVOID, DWORD, QWORD, HRESULT, ATOM, CALLBACK, WINAPI, APIENTRY, COLORREF, FLOAT (lol its defined as #define float FLOAT), HANDLE, HDC ...

[ISmokeWeedAmICoolNow]

That's Microsoft notation , which is gay. Yay let's introduce 10000 more types into this ! TCHAR, PVOID, DWORD, QWORD, HRESULT, ATOM, CALLBACK, WINAPI, APIENTRY, COLORREF, FLOAT (lol its defined as #define float FLOAT), HANDLE, HDC ...

thats half true, i hate how they just wrap int in INT and float in FLOAT, but for HANDLE and things like that it's expected. it makes the variable more opaque. and HANDLE looks better than void*.

[Jason]

That's Microsoft notation , which is gay. Yay let's introduce 10000 more types into this ! TCHAR, PVOID, DWORD, QWORD, HRESULT, ATOM, CALLBACK, WINAPI, APIENTRY, COLORREF, FLOAT (lol its defined as #define float FLOAT), HANDLE, HDC ...

Cool story bro.

And there's a heap of useless typedefs, like INT, VOID..etc, some are more useful as they give you more of an idea of what the datatype relates to, although FARPROC just sounds stupid.

[_Dead]

its called hungarien notation, thats where it was start completely.

[Jason]

its called hungarien notation, thats where it was start completely.

It's more of a modified form of hungarian notation, in which actual types aren't specified in the prefix.

Say for a PBYTE

This notation
pVarName

True Hungarian:
pbVarName

Hungarian notation - Wikipedia, the free encyclopedia

[-Bl00d-]

i have the WeaponMgr class info if anyone wants it illpost it up

[topblast]

That's Microsoft notation , which is gay. Yay let's introduce 10000 more types into this ! TCHAR, PVOID, DWORD, QWORD, HRESULT, ATOM, CALLBACK, WINAPI, APIENTRY, COLORREF, FLOAT (lol its defined as #define float FLOAT), HANDLE, HDC ...

callback is not a type and they need them as they clearly are all used

[qwerty01]

CALLBACK is Microsoft notation, which is what he was talking about...

[topblast]

Cool story bro.

And there's a heap of useless typedefs, like INT, VOID..etc, some are more useful as they give you more of an idea of what the datatype relates to, although FARPROC just sounds stupid.

Those might be defined for reference to 64bit and 32bit code and windows if just the same source being built over and over like what we do in hacks, wanna bet that most these haacks got garbage in them from updates

thats half true, i hate how they just wrap int in INT and float in FLOAT, but for HANDLE and things like that it's expected. it makes the variable more opaque. and HANDLE looks better than void*.

That's the point of C++, some IDEs might define int as integer, is so they will be easily fixed. C++ is object oriented its just C at the next lvl. Would you like to type DWORD as unsigned int32 everytime? What about the unsigned chars(BYTE) and unsigned long(QWORD). They must be a reason or its the programmers habits, your the the programmers of windows so deal with it

CALLBACK is Microsoft notation, which is what he was talking about...

I like it just the way it is