Well, in this case, the only people who could view it is anyone the scripters make it accessible to. Just a point.

I really have no problem broadcasting my IP to the world, nobody can do **** with it anyways. Its nothing personal, so here's my IP: 70.116.147.166.

Paranoia comes from ignorance and Graal seems to have alot of that.

http://techxonline.net/temp/ip.png
OMG NOW YOU CAN BE HAXORED! AL QUEDA IS COMING! RUN!!!!!!!!!!!!

--
Skyld, would it be okay if I use a requestHTTP() when the player logs on to get the players IP, trigger it serverside, and then put it in a log. I don't need to make any clientr.ip or such variable.

Why do you want this information?

I already posted about this:

With no legit reason as to why it shouldn't be allowed. You say with staff comes the responsibility of keeping players' information private, well, what's the difference in opening a player's attributes to read an ip over doing so with a variable? It would still only be able to be viewed by staff, except now servers can add more to their security with ip checks and so forth.

Also you could make it so certain things can be IP locked-based on the players preference. For example, to drop/sell items, you have to have an IP in your IP list. When you first log on, you set an account password, saved as md5 in a db npc. When you try to drop/sell something, if your IP isn't listed, you get a pop-up saying "Your IP is not recognized! Please enter password:" and if you know the password, you can manage the list of IPs allowed.

This would be very nice to have, and also could prevent people losing items if their account was hacked (aka they did something wrong with their password-though I suppose graal.net could be hacked again, and anti-graal could get the passwords for peoples accounts again).

Skyld, I see nothing wrong with logging IPs on login, if not saved into a variable. Since you have not strictly forbidden this (and I think you'd need Stefan's permission anyway) I'm going to go ahead and make this system. You may come look at it when I'm finished. If you feel that it is bad for people to have extra account protection, you are free to talk to Stefan and get him to stop me.

I like to see some initiative being taken.

Stefan has previously stated that he does not want people getting IPs with requestHTTP/URL.
Way to disregard what I have said:

You have given me no reason as to why I should not use this.

Why? Because Stefan does not want people doing it.

I have already explained other reasons in this thread, but it boils down to the final line: Stefan does not want people doing it.

So the big man says he doesn't want it but we can't argue for it? I don't think you've clearly read this thread, but there are no valid reasons as to why to prevent it, while there are many valid reasons as to why it should be implemented.


You can't argue for privacy with something that isn't private to begin with.

Take it up with Stefan if you want, but this thread is going nowhere and solving nothing.

If anything, a PC ID variable or a function that tells you if someone is currently logged in from inside their IP ranges/PC IDs is more likely to help with identifying people, but I highly doubt a player.ip variable will happen.

Then a PC ID variable would be much appreciated.

Also something else I would like is Custom Object Types =(

Perhaps there could be an MD5 of an IP, or something that will be unique in each household (or even each computer). That way we will be able to log it fine, without upsetting Stefan >_<

I requested the ability to define global custom data types directly to Stefan and he simply said to use classes. I'd much prefer doing temp.baddy = new baddyclass("supersoldier"); as well as being able to modify the original datatypes to add custom functions / vars.

That would be handy.

Indeed, I don't want to have to settle for less like using TStaticVars with classes.