lol this is way more complicated


just create an array with clients listed as int rather than reading xuid's.

then you can just verify the same way you were doing

if((int)verify == 0)
{
//unverified
}
else if(verify == 1)
{
//basic verification
}
else if(verify == 2)
{
//upgraded verification
}
else if(verify == 3)
{
//co-host
}
else if(verify == 4)
{
// host
}


other ways of doing this with more optimized cod3nz but you probably wouldnt understand

lampr4y wrote lol this is way more complicated


just create an array with clients listed as int rather than reading xuid's.

then you can just verify the same way you were doing

if((int)verify == 0)
{
//unverified
}
else if(verify == 1)
{
//basic verification
}
else if(verify == 2)
{
//upgraded verification
}
else if(verify == 3)
{
//co-host
}
else if(verify == 4)
{
// host
}


other ways of doing this with more optimized cod3nz but you probably wouldnt understand

You can also find the host with functions in this struct
struct XenonUserData//Credit to SnappiestJack
{
int signInState;
char name[0x20];
};
XenonUserData * xenonUserData = (XenonUserData *)0x838BA820;
then loop through all 18 clients's names in the playerstate, and compare it to the one that is the name of the one int the XenonUserData Struct.

hacksorce wrote

lampr4y wrote lol this is way more complicated


just create an array with clients listed as int rather than reading xuid's.

then you can just verify the same way you were doing

if((int)verify == 0)
{
//unverified
}
else if(verify == 1)
{
//basic verification
}
else if(verify == 2)
{
//upgraded verification
}
else if(verify == 3)
{
//co-host
}
else if(verify == 4)
{
// host
}


other ways of doing this with more optimized cod3nz but you probably wouldnt understand

You can also find the host with functions in this struct
struct XenonUserData//Credit to SnappiestJack
{
int signInState;
char name[0x20];
};
XenonUserData * xenonUserData = (XenonUserData *)0x838BA820;
then loop through all 18 clients's names in the playerstate, and compare it to the one that is the name of the one int the XenonUserData Struct.

like I said, he wouldnt understand that

lampr4y wrote
like I said, he wouldnt understand that

You're comparing apples to oranges. You posted a way to store the verification state of the players(which was incorrect, should be an enumerator), and hacksorce posted a way to find the host.

M0D1F13D wrote

lampr4y wrote
like I said, he wouldnt understand that

You're comparing apples to oranges. You posted a way to store the verification state of the players(which was incorrect, should be an enumerator), and hacksorce posted a way to find the host.

ok,

the most efficient way of doing it would be to just have the clients start out crouched, get their pos in the centity_t struct, and then verify through simply detecting client positions. ex: if a client is crouched unverified, once able to stand up, verified.....

lampr4y wrote
ok,

the most efficient way of doing it would be to just have the clients start out crouched, get their pos in the centity_t struct, and then verify through simply detecting client positions. ex: if a client is crouched unverified, once able to stand up, verified.....

Was that sarcasm? It's so hard to tell on the internet...

lampr4y wrote

M0D1F13D wrote

lampr4y wrote
like I said, he wouldnt understand that

You're comparing apples to oranges. You posted a way to store the verification state of the players(which was incorrect, should be an enumerator), and hacksorce posted a way to find the host.

ok,

the most efficient way of doing it would be to just have the clients start out crouched, get their pos in the centity_t struct, and then verify through simply detecting client positions. ex: if a client is crouched unverified, once able to stand up, verified.....

That is a good idea ;) but I was thinking that in the g_client_s struct you could just freeze their velocity, thus freezing them and making a giant black icon on their screen. Until they are verified by the host of the game.

hacksorce wrote

lampr4y wrote

M0D1F13D wrote

lampr4y wrote
like I said, he wouldnt understand that

You're comparing apples to oranges. You posted a way to store the verification state of the players(which was incorrect, should be an enumerator), and hacksorce posted a way to find the host.

ok,

the most efficient way of doing it would be to just have the clients start out crouched, get their pos in the centity_t struct, and then verify through simply detecting client positions. ex: if a client is crouched unverified, once able to stand up, verified.....

That is a good idea ;) but I was thinking that in the g_client_s struct you could just freeze their velocity, thus freezing them and making a giant black icon on their screen. Until they are verified by the host of the game.

Or you could use r_scaleviewport "0" that's what I did and its perfect.

M0D1F13D wrote

lampr4y wrote
ok,

the most efficient way of doing it would be to just have the clients start out crouched, get their pos in the centity_t struct, and then verify through simply detecting client positions. ex: if a client is crouched unverified, once able to stand up, verified.....

Was that sarcasm? It's so hard to tell on the internet...

do you think anyone somewhat with knowledge would actually say that.......

cmon mane

Nice Tut !

1100101010010101