clientr.var inconsistancy

[DustyPorViva]

I set various clientr.vars with my system. For example, I have one that increases a clientr.var whenever I slash a bush, like so:
findplayer(params[1]).clientr.bushstat += params[2];
Which increases appropriately by params[2].

However, I also have clientr.vars that enables/disables certain modes in my system, like so:
findplayer(params[1]).clientr.enablesword = params[2];
Which sets it to true/false.

The first example shows up in my client.vars list in RC. The second does not. The second is recognized by scripts however(as my scripts function fine), but like I said... it doesn't appear in my player attributes on RC. Does this have to do with true/false being used in client.vars or something?

[Mark Sir Link]

Originally Posted by DustyPorViva

I set various clientr.vars with my system. For example, I have one that increases a clientr.var whenever I slash a bush, like so:
findplayer(params[1]).clientr.bushstat += params[2];
Which increases appropriately by params[2].

However, I also have clientr.vars that enables/disables certain modes in my system, like so:
findplayer(params[1]).clientr.enablesword = params[2];
Which sets it to true/false.

The first example shows up in my client.vars list in RC. The second does not. The second is recognized by scripts however(as my scripts function fine), but like I said... it doesn't appear in my player attributes on RC. Does this have to do with true/false being used in client.vars or something?

if the flag is set to true, it will appear in the list, if it is false, it won't.

If it doesn't exist, it will evaluate to false.

[DustyPorViva]

Originally Posted by Mark Sir Link

if the flag is set to true, it will appear in the list, if it is false, it won't.

If it doesn't exist, it will evaluate to false.

Hmm... guess I never thought of that, however I can't remember if I encounted the problem even if it was true or not. Ah well!

[Mark Sir Link]

Originally Posted by DustyPorViva

Hmm... guess I never thought of that, however I can't remember if I encounted the problem even if it was true or not. Ah well!

it seems like it may be functioning similar to how set and unset flags used to work in GS1 (mostly pre-NPC Server) where flags were being used as booleans quite a bit.

[Twinny]

It is annoying and I've been caught out a few times but this but any string with a null value disappears =(

[Admins]

False/null/"" is the default value, if you set a network string (client., clientr, server., serverr.) to such value then it is removed, means less data to send and an easy way to clear variables.