Briggs Softworks

Ideally we would like to avoid people playing on the same IP and definitely not at the same table.. Problem is when running bots like IPB or MavensDev that is basically an impossible task.. I'm thinking if there was a way to make an exception, such as we have with the whitelist for API access might be a consideration to add. Or maybe a loophole allowing the internal IP of 127.0.0.1 to be allowed as a duplicate because while we can allow dup IPs in general but block on individual tables to prevent collusion if were running propbots or whatever you want to call them we have to allow all duplicate IPs onto the system even at the same tables.. Don't know how much of a major issue that would be to allow such.. I personally have been testing my bots running directly on my server so they login to the local 127.0.0.1 but a white list would probably be more practical if somebody wanted to for example stress test their server by running 300 or so bots temporarily from a remote machine possible.. Just a thought..

Exempting localhost IPs from the duplicate ban does make sense. I will put that on my to-do list.

This has been implemented in 5.16. IP address 127.0.0.1 and ::1 (the ipv6 localhost) are both automatically exempted now.