TServerPlayer.ipaddress

[fowlplay4]

Well there's a computerfirstlogin variable, which currently works for detecting multi-clienting.

As seen here: http://forums.graalonline.com/forums...ad.php?t=87901

I'd recommend adding a ipfirstlogin variable, that way we can still determine multi-pc'ing, and the player's will still have their privacy.

[Admins]

I've added TServerPlayer.ipaddresshash, it will be available when I upload the npcserver (probably in a few days).

[Chompy]

Originally Posted by Stefan

I've added TServerPlayer.ipaddresshash, it will be available when I upload the npcserver (probably in a few days).

Nice!

[Programmer]

Originally Posted by Stefan

I've added TServerPlayer.ipaddresshash, it will be available when I upload the npcserver (probably in a few days).

Finally, after all this time bickering. Thanks Stefan.

[Loriel]

Originally Posted by Programmer

Personally, I would use IP checks to determine if a user is multilogging on my server

IP addresses do not work like that

[Skyld]

Originally Posted by fowlplay4

I'd recommend adding a ipfirstlogin variable, that way we can still determine multi-pc'ing, and the player's will still have their privacy.

It would be essentially useless, because it would be accurate for someone with a static IP and then inaccurate for someone with a dynamic IP. Some people get a different IP address every time they connect to the internet, and some people get a different IP address in a completely different IP block (for example, BT users in the UK can get 217.*.*.* addresses or 86.*.*.* addresses or 81.*.*.* addresses etc).

Originally Posted by Programmer

Personally, I would use IP checks to determine if a user is multilogging on my server, or simply evading jail time or ban time. Of course, you could always check using /open, but I believe that script access would be very useful.

An IP address is shared with everyone who is behind a certain NAT, so two different players on two different computers in one house would have the same external IP address, which is why it is bad to try and enforce jails/bans or such using IP addresses.

[salesman]

player.pcid???

[Chompy]

Originally Posted by salesman

player.pcid???

Originally Posted by fowlplay4

Well there's a computerfirstlogin variable, which currently works for detecting multi-clienting.

As seen here: http://forums.graalonline.com/forums...ad.php?t=87901

I'd recommend adding a ipfirstlogin variable, that way we can still determine multi-pc'ing, and the player's will still have their privacy.

(: I guess something like that above will work in the meanwhile

[cbk1994]

Originally Posted by salesman

player.pcid???

TServerPlayer.computerid - integer (read only) - only accessible on authorized servers

Because we can also abuse their PCID.

[Inverness]

Originally Posted by cbk1994

Because we can also abuse their PCID.

I'm choking on all of the sarcasm in this thread.

[salesman]

Has this been added yet? It doesn't seem to be working...

PHP Code:

temp.pl = findPlayer("salesman");
echo(pl.ipaddresshash); 


[cbk1994]

Originally Posted by salesman

Has this been added yet? It doesn't seem to be working...

PHP Code:

temp.pl = findPlayer("salesman");
echo(pl.ipaddresshash); 


Nope. I mentioned it to Stefan a few days ago and he said he'd get to it... eventually.

[Admins]

It should work on Zodiac, Classic and private playerworlds already.

[Rufus]

I guess you didn't add global guild messaging at the same time then

[fowlplay4]

Workz

PHP Code:

function onCreated() {
  temp.pl = new TServerPlayer("fowlplay4");
  echo(temp.pl.ipaddresshash);
} 


Echos "d3dd73d0b7d9cf793b375616490c86dd"