BindIP is used if your computer has two (or more) network cards (or network card(s) and modem(s)), which are connected to the internet. You can specify which IP you wish to use for that socklisten.
For example, let's say you have 2 network interface cards (NICs) installed in your computer. NIC1 uses the IP 12.34.56.78 and NIC2 uses the IP 23.45.67.89. You can set up a socklisten on either of those IP addresses using either of these two commands:
- /socklisten -d 12.34.56.78 SListenNIC1 4321
[color:black]
This would set up a socklisten on port 4321 of IP 12.34.56.78 called SListenNIC1 and you would reference that socklisten as SListenNIC1 for all your scripts that deal with that socklisten.
on *:SOCKLISTEN:SListenNIC1:{
; commands
}
/socklisten -d 23.45.67.89 SListenNIC2 1234
This time, you have specified that you want to listen to IP 23.45.67.89 on port 1234 and refer to that socklisten as SListenNIC2 in your scripts.
on *:SOCKLISTEN:SListenNIC2:{
; commands
}[/color]
I hope this clears up what the bindip is, how to use it, and when to use it. By far, most people won't use it, but since some folks can, there needs to be a way to get to that other IP in your script(s).