Home

[Quick Start] [Licenses and Restrictions] [Features] [Old Releases] [Developers Guide]

---

usunpokerutils - set of Poker tools/utilities, mostly for tournaments, some for cash.

usunpokertools integrates online ranking host systems (SharkScope - officially approved by them, ProLabs/Top Shark, OPR - restrictions apply, PTR - which is not supported for PokerStars!, etc), poker rooms (PokerStars, PartyPoker, 888/Pacific, etc), local trackers/HUDs (Holdem Manager 1,2, PokerTracker 3,4, etc). It scans poker room local hand history, search information about some players against online ranking host systems, and saves that information as player notes stored in local trackers/HUDs.

Auto and manual scan for players on your tables is supported against multiple rooms and host systems, Notes are generated based on configurable templates and saved into HUD player notes. To reduce the load on the host systems, local caches with players info are supported. usunpokertools 1.3+ is reviewed and approved by PokerStars.

See further details about suported systems and known issues (HM2, PokerHands support): [Features]

Please read this carefully before tools usage: [Licenses and Restrictions]
For system requirements and installation guide, please follow to [Quick Start]

Releases
Currently in development: 1.4

Scope:

• New tool to manage Tracker/HUD player notes, delete old ones by regexp in particular;
• Add Microgaming (Unibet) support;
• Extend SharkScope integration and cache to store more data and stats. Support estimated feature.
• To provide an apportunity to combine auto-scanner tools and install/run as OS services.

---

Release 1.3.3
What's new:
Overview:
1) You can restrict optionally the load on some host system. It is helpful in order to reduce load on OPR and therefore reduce risk of ban by IP from OPR.

Details:
1) Host access load can be restricted. Only login and player search operations are tracked. Load record is added to the cache just prior the first actual request is about to be sent to the target host system. The record in the cache will expire after the configured amount of time. When tasks for player search are taken to be execute inside internal server, they are verified if load already exceeded the maximum allowed for corresponding host system(s); if reached the limit, the task is skipped for this portion. Therefore, it is possible to have an overload, if mulitple tasks (5 by default) of the same host system are taken within the same portion, and limit is not reached yet. Thus, actual load sometimes might reach configured max + max of (max tasks in one portion to execure; max amount of task execution threads), in default configs it is (configured max amount + 5). If proxy from the configured list is changed - all load tracks for the corresponding host systems are cleared.

New optional settings (will restrict OPR access by 5 operations per two minutes: 1 login + 4 player search attempts or 5 searches):

# Operation load restrictions (e.g. 5 operations per minute). Only login and search operations are tacked without regard if they were successful or not.
# If load restrictions should be enabled, false if not specified
.hostsystem.opr.extra.USE_LOAD_RESTRICTIONS=true
.hostsystem.opr.extra.USE_LOAD_RESTRICTIONS.type=java.lang.Boolean
# Max operation attempts load per given period of time to track (e.g. 5 operations per minute should have 5 here).
.hostsystem.opr.extra.MAX_LOAD=5
.hostsystem.opr.extra.MAX_LOAD.type=java.lang.Integer
# Period of time to track the load (e.g. 5 operations per minute should have 60000 here).
.hostsystem.opr.extra.LOAD_EXPIRATION_PERIOD=120000
.hostsystem.opr.extra.LOAD_EXPIRATION_PERIOD.type=java.lang.Long

Upgrade from 1.3.2:
1) Update /lib/usunpokertools.jar

2) Update /config/globalconfigs.properties
Add new optional settings (will restrict OPR access by 5 operations per minute: 1 login + 4 player search attempts or 5 searches):

# Operation load restrictions (e.g. 5 operations per minute). Only login and search operations are tacked without regard if they were successful or not .
# If load restrictions should be enabled, false if not specified
.hostsystem.opr.extra.USE_LOAD_RESTRICTIONS=true
.hostsystem.opr.extra.USE_LOAD_RESTRICTIONS.type=java.lang.Boolean
# Max operation attempts load per given period of time to track (e.g. 5 operations per minute should have 5 here).
.hostsystem.opr.extra.MAX_LOAD=5
.hostsystem.opr.extra.MAX_LOAD.type=java.lang.Integer
# Period of time to track the load (e.g. 5 operations per minute should have 60000 here).
.hostsystem.opr.extra.LOAD_EXPIRATION_PERIOD=120000
.hostsystem.opr.extra.LOAD_EXPIRATION_PERIOD.type=java.lang.Long

Optionally pretend to bet a browser for OPR:
.hostsystem.opr.extra.HEADER_USERAGENT=Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)

Optionally, you may change default OPR search player to some other, may be even yourself (by default player should be from PartyPoker):
.hostsystem.opr.extra.DEFAULT_PLAYER_SEARCH=here_new_player_name

---

Release 1.3.2
What's new:
Overview:
1) Make socket timeouts configurable.
2) Fix restart proxies for host.
3) Logs improved.

Details:
1) httpunit 3rd party library was updated (new one is /lib/httpunit/httpunit-1.7-usun-patch2.jar) to support new configurable timeouts for sockets. By default max connect time is 1min, max wait for response data 2min.
New optional settings:

# Socket connection time-out in millis
.transport.http.connectTimeout=60000
# Socket read time-out in millis
.transport.http.readTimeout=120000

2) Fixed bug with not restarted proxies, for command "|proxy|restart|hostsystemidhere" from Manage Proxies tool.

3) Additional logs for proxies.

Upgrade from 1.3.1:
1) Update /lib/usunpokertools.jar

2) Add new /lib/httpunit/httpunit-1.7-usun-patch2.jar

3) Update and reconfigure if required (JAVA_HOME variable) /bin/_setEnv.bat

4) Update /config/globalconfigs.properties
Add new settings:

# Socket connection time-out in millis
.transport.http.connectTimeout=60000
# Socket read time-out in millis
.transport.http.readTimeout=120000

--
Release 1.3.1
What's new:
Overview:
1) Player search process optimization.
2) Fix default configs for business operation stats restriction in case of list of proxies.

Details:
1) Multithreading for all connectors is rewritten according to the JDK 1.5+ recommendations. Some bad proxy can in theory block the whole search process and require application restart but the danger was minimized as much as possible. Thirdparty library used for HTTP communication should be rewritten to completely resolve the issue, it doesn't really worth it.

2) 1.3 release had business operation restrictions in the wrong place, they should be under host system section .extra, instead of HTTP transport section .extra.

Upgrade from 1.3:
1) update /lib/usunpokertools.jar

2) update /config/globalconfig.properties
Remove
.transport.http.extra.LOGIN_MAX_FAIL_STREAK=6
.transport.http.extra.LOGIN_MAX_FAIL_STREAK.type=java.lang.Integer
.transport.http.extra.LOGOFF_MAX_FAIL_STREAK=6
.transport.http.extra.LOGOFF_MAX_FAIL_STREAK.type=java.lang.Integer
.transport.http.extra.PLAYER_SEARCH_MAX_FAIL_STREAK=11
.transport.http.extra.PLAYER_SEARCH_MAX_FAIL_STREAK.type=java.lang.Integer

Add
# The following settings are only used if .transport.http.useProxy=true, .transport.http.useProxyListFromFile=true,
# .hostsystem.<host system="" id="">.extra.USE_PROXY=true are set for corresponding host system.
# They are additional restrictions for individual operations done via this host system connector.
# If operation failure streak exceeds these settings, current proxy for the host system is discarded regardless of .transport.http.maxAttemptsViaProxy.
# If values are not specified or <= 0, then restriction is ignored.
.hostsystem.opr.extra.LOGIN_MAX_FAIL_STREAK=6
.hostsystem.opr.extra.LOGIN_MAX_FAIL_STREAK.type=java.lang.Integer
.hostsystem.opr.extra.LOGOFF_MAX_FAIL_STREAK=6
.hostsystem.opr.extra.LOGOFF_MAX_FAIL_STREAK.type=java.lang.Integer
.hostsystem.opr.extra.PLAYER_SEARCH_MAX_FAIL_STREAK=11
.hostsystem.opr.extra.PLAYER_SEARCH_MAX_FAIL_STREAK.type=java.lang.Integer</host>

# The following settings are only used if .transport.http.useProxy=true, .transport.http.useProxyListFromFile=true,
# .hostsystem.<host system="" id="">.extra.USE_PROXY=true are set for corresponding host system.
# They are additional restrictions for individual operations done via this host system connector.
# If operation failure streak exceeds these settings, current proxy for the host system is discarded regardless of .transport.http.maxAttemptsViaProxy.
# If values are not specified or <= 0, then restriction is ignored.
.hostsystem.sharkscope.extra.LOGIN_MAX_FAIL_STREAK=6
.hostsystem.sharkscope.extra.LOGIN_MAX_FAIL_STREAK.type=java.lang.Integer
.hostsystem.sharkscope.extra.LOGOFF_MAX_FAIL_STREAK=6
.hostsystem.sharkscope.extra.LOGOFF_MAX_FAIL_STREAK.type=java.lang.Integer
.hostsystem.sharkscope.extra.PLAYER_SEARCH_MAX_FAIL_STREAK=11
.hostsystem.sharkscope.extra.PLAYER_SEARCH_MAX_FAIL_STREAK.type=java.lang.Integer</host>

# The following settings are only used if .transport.http.useProxy=true, .transport.http.useProxyListFromFile=true,
# .hostsystem.<host system="" id="">.extra.USE_PROXY=true are set for corresponding host system.
# They are additional restrictions for individual operations done via this host system connector.
# If operation failure streak exceeds these settings, current proxy for the host system is discarded regardless of .transport.http.maxAttemptsViaProxy.
# If values are not specified or <= 0, then restriction is ignored.
.hostsystem.prolabs.extra.LOGIN_MAX_FAIL_STREAK=6
.hostsystem.prolabs.extra.LOGIN_MAX_FAIL_STREAK.type=java.lang.Integer
.hostsystem.prolabs.extra.LOGOFF_MAX_FAIL_STREAK=6
.hostsystem.prolabs.extra.LOGOFF_MAX_FAIL_STREAK.type=java.lang.Integer
.hostsystem.prolabs.extra.PLAYER_SEARCH_MAX_FAIL_STREAK=11
.hostsystem.prolabs.extra.PLAYER_SEARCH_MAX_FAIL_STREAK.type=java.lang.Integer</host>

# The following settings are only used if .transport.http.useProxy=true, .transport.http.useProxyListFromFile=true,
# .hostsystem.<host system="" id="">.extra.USE_PROXY=true are set for corresponding host system.
# They are additional restrictions for individual operations done via this host system connector.
# If operation failure streak exceeds these settings, current proxy for the host system is discarded regardless of .transport.http.maxAttemptsViaProxy.
# If values are not specified or <= 0, then restriction is ignored.
.hostsystem.ptr.extra.LOGIN_MAX_FAIL_STREAK=6
.hostsystem.ptr.extra.LOGIN_MAX_FAIL_STREAK.type=java.lang.Integer
.hostsystem.ptr.extra.LOGOFF_MAX_FAIL_STREAK=6
.hostsystem.ptr.extra.LOGOFF_MAX_FAIL_STREAK.type=java.lang.Integer
.hostsystem.ptr.extra.PLAYER_SEARCH_MAX_FAIL_STREAK=11
.hostsystem.ptr.extra.PLAYER_SEARCH_MAX_FAIL_STREAK.type=java.lang.Integer</host>