New thing for scripting
 

a new thing that should be added is to make it so we can see the players ip address in a script

it would be useful for things like reward systems to stop cheating from the same computers

like if you killed player a it would check ip and if it didnt match with player b then they would not get the reward for killing the player

but then again people can always kill friends for rewards

but it would be useful

Do you mean it checks the ip of both player a and player b and if they are the same they don't get the reward?

That would be sorta useful... such as checking the IPs of all the players in an event to make sure that someone isn't cheating and trying for a second chance at winning.

What would be more useful though, is adding a MAC address check. Maybe not avaliable through script, but as a replacement for IP bans, or an addition to them. IP bans are easy to get around, especially if you have a proxy or simply a dynamic IP.
That way two people on the same network could both play on a server without any problems, but if they're on the same computer they can be caught red handed for account sharing by doing something as simple as cheating at an event.

Im pretty sure it is illegal or something to do that.

[edit]
I don't think you can ban a MAC if they are more than one hop outside your network. Also you can change your MAC address easily with software in many OS. Correct me if i'm wrong.
[/edit]

The MAC is reported directly from your NIC.. your network card, so no, unless you can somehow mask a responce from the NIC, you can't alter it.
Also, it would be -easy- to ban an MAC address. You have the client check the MAC of the host and send that to the server, which would then check it against a list of banned MAC's, as well as the IP it came from. If either are banned, then bang. connection closed.

simple enough?

All I have seen from a few webpages that it would be impractical to do. Easy enough to do on a LAN, but like I said, outside of one hop you can't even find the MAC address.

You're missing the point.
The CLIENT (as in graal.exe) gets the client's (local computer's) MAC and sends it to the server. Think of it like a second username or something, its just data that's being sent for authentication.

You're thinking of it as the server is reading the last hop's MAC from the packet's header (which changes with every hop), not from the data portion (which never changes).

Solve the issue with people changing their MAC and you can have a quarter.

Calani, you still need to trust the client to be honest.

It's illegal, using IP's and MAC addresses as a comparison you could likely find out if they're cheating their MAC address... and then inform some persons that aren't interested. Good deterent, none the less.