Hello,

up to now character.acct is a ref to the account object. character.acctname is the name of the account as string.

character.acct is reported as: 'deprecated, will be removed in next release, use Client instead'
character.acctname is not deprecated, will continue to work (really?)

The new client object has no acct member! So we cannot use 'client instead'.
Does this mean, that for character.acct there will be no replacement?

So instead of writing

var playeraccount := character.acct;

we will need to write

var playeraccount := FindAccount(character.client.accntname);

Or is this an oversight in documentation?

Also, while character.acctname is not deprecated, i.e. will continue to work normally, the new client object also has a member 'acctname', so one could write either character.acctname or character.client.acctname. True?

OWHorus

Now that you mention it, the documentation also lists client.acctname as Type "Account" but describes it as a string for the account name.

I prefer the char.acct syntax than the FindAccount(char) syntax. Much cleaner. I hope the struct comes back.

Hehe this looks like a documentation error. It looks like it references:

03-24-2010 Turley:
Added: ClientRef object
pkt.sendpacket() & SendPacket() now accepts client or character
r/o members:
ip, acctname, clientversion, clientinfo, clienttype, clientver_detail, uo_expansion_client
methods:
compareversion()
used as prelogin param for packethooks instead of old struct (so you can send packets)
Added: character.client
returns ClientRef object or error
Note: This or next release duplicate members/methods get deleted from chr (except acctname)