Recent changes to Home

WikiPage Home modified by user unknown

user unknown — Thu, 12 Jul 2012 04:45:58 -0000

--- v62
+++ v63
@@ -33,7 +33,7 @@
 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):
-[CODE]
+
 \# 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
@@ -44,7 +44,7 @@
 \# 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
-[/CODE]
+
 
 Upgrade from 1.3.2:
 1) Update /lib/usunpokertools.jar

WikiPage Home modified by user unknown

user unknown — Thu, 12 Jul 2012 03:49:10 -0000

--- v61
+++ v62
@@ -24,7 +24,55 @@
 - To provide an apportunity to combine auto-scanner tools and install/run as OS services.
 
 ---
-Release 1.3.2
+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):
+[CODE]
+\# 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
+[/CODE]
+
+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.

WikiPage Home modified by user unknown

user unknown — Tue, 03 Jul 2012 04:55:57 -0000

--- v60
+++ v61
@@ -6,7 +6,7 @@
 
 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.
+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]

WikiPage Home modified by user unknown

user unknown — Sun, 01 Jul 2012 04:45:20 -0000

--- v59
+++ v60
@@ -29,6 +29,7 @@
 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.
@@ -40,6 +41,8 @@
 .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

WikiPage Home modified by user unknown

user unknown — Sun, 01 Jul 2012 04:13:12 -0000

--- v58
+++ v59
@@ -33,12 +33,11 @@
 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:
-[CODE]
-# Socket connection time-out in millis
+
+\# Socket connection time-out in millis
 .transport.http.connectTimeout=60000
-# Socket read time-out in millis
+\# Socket read time-out in millis
 .transport.http.readTimeout=120000
-[/CODE]
 
 2) Fixed bug with not restarted proxies, for command "|proxy|restart|hostsystemidhere" from Manage Proxies tool.

WikiPage Home modified by user unknown

user unknown — Sun, 01 Jul 2012 04:12:52 -0000

--- v57
+++ v58
@@ -24,7 +24,42 @@
 - To provide an apportunity to combine auto-scanner tools and install/run as OS services.
 
 ---
-Release 1.3.1
+Release 1.3.2
+What's new:
+Overview:
+1) Make socket timeouts configurable.
+2) Fix restart proxies for host.
+
+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:
+[CODE]
+# Socket connection time-out in millis
+.transport.http.connectTimeout=60000
+# Socket read time-out in millis
+.transport.http.readTimeout=120000
+[/CODE]
+
+2) Fixed bug with not restarted proxies, for command "|proxy|restart|hostsystemidhere" from Manage Proxies tool.
+
+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.

WikiPage Home modified by user unknown

user unknown — Sat, 30 Jun 2012 05:26:07 -0000

--- v56
+++ v57
@@ -24,82 +24,23 @@
 - To provide an apportunity to combine auto-scanner tools and install/run as OS services.
 
 ---
-Release 1.3
+Release 1.3.1
 What's new:
 Overview:
-1) SharkScope integration updated, usunpokertools is now officially approved and licensed by SharkScope.
-2) Estimations for hidden OPR stats feature was reworked to reduce possible risks with PokerStars, it now doesn't show any numerical estimated values for hidden stats, just text labels of various categories.
-3) GUI improved.
-4) Player search timeouts reworked.
-5) Proxy list support is extended, now proxy for has stats and it possible to configure restrictions based on that stats.
-6) New tool "Manage Proxies" was added.
+1) Player search process optimization.
+2) Fix default configs for business operation stats restriction in case of list of proxies.
 
 Details:
-1) Stats about proxies used are tracked for each host system and business operation (login, logoff, player search) under it: 
-success attempts, failure attempts, maximum success and failure streaks, current streak.
-Proxy failure (which we we track to determine when proxy should be discarded) is not considered as failure attempt for business operation stats and doesn't affect streaks.
+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) New "Manage Proxies" tool added.
-/config/globalconfigs.properties
-
-New configs:
-
-.tool.manageproxy.id=manageproxy
-.tool.manageproxy.name=Manage Proxies
-.tool.manageproxy.description=Console to manage proxies, host system access via proxy stats.
-.tool.manageproxy.className=edu.usun.poker.tool.proxy.ManageHostProxyTool
+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.
 
 
-Update existing:
+Upgrade from 1.3:
+1) update /lib/usunpokertools.jar
 
-.tool.active=playerscan_history_tournament,playerscan_history_cash,playerscan_console_tournament,playerscan_console_cash,manageplayerscache,manageproxy
-
-
-3) Default DB name for HM1,HM2 was changed to holdemmanager, holdemmanager2
-
-4) If "estimated" feature for OPR is enabled, do not use numerical estimation values, use category labels instead:
-ROI replacement: d- (the weakest),d+,s-,s+/0 (neutral),f-,f+,w-,w+ (the strongest) - means player strength category; the idea is based on http://www.pocketfives.com/articles/how-much-variance-mtt-s-224464/
-Profit replacement: 0 (operates small amounts),!,!!,!!!,!!!!,!!!!! (operates highest amounts) - it won't show "+" or "-" sign, so it doesn't say if player is actually winning or loosing, just an indicator of volume; 
-Average Buy-In replacement (OPR only): l-(lowest stakes),l,l+,m-,m,m+,h-,h,h+,t (highest stakes) - category for game stakes.
-
-Example note generated: 
-opr2Dec26: Ew+ROI/16ITM/484($l)/516AFS/13RA/$12k(!) 2/10/53/21/13
-instead of 
-opr2Dec26: E+170ROI/16ITM/484($9)/516AFS/13RA/$12k(+7.8k) 2/10/53/21/13
-
-In such way, the PokerStars should be ok with this feature and it opens way to license tools against this room.
-
-Estimated feature is now enabled by default:
-.hostsystem.opr.extra.ESTIMATED_PLAYER_STATS_ENABLED=true
-
-5) Integration with new SharkScope API was updated, now it uses official application name and license key provided by SharkScope for usunpokertools. 
-In other words, from now on the usunpokertools is approved and licensed by SharkScope.
-
-Just in case, you may update User-Agent header. 
-
-\# The HTTP header "User-Agent" to be used for all host requests.
-.hostsystem.sharkscope.extra.HEADER_USERAGENT=usunpokertools 1.x
-
-No need to configure license and application name, they are hardcoded inside usunpokertools code, as this license was given only for these tools. 
-
-In case you want to implement a spin-off, please contact SharkScope and request your own application name and license. This process is very easy and friendly.
-
-If you want to reuse SharkScope connector implemented here, just extend edu.usun.poker.integration.hostsystem.sharkscope.SharkScopeConnector and override #specificTransactionInit - with your own application name and license used there.
-
-6) GUI: press Enter in input command text field = Send button clicked
-
-7) UI/GUI/Tools: output search results for players async as soon as they appear as valid records in the local cache.
-
-8) Small fix for PTR to avoid NPE for error case.
-
-9) For proxy list feature, additional restriction added for proxy against host systems and their business operations.
-It's covered in details in config notes provided below.
-
-\# The following settings are only used if .transport.http.useProxy=true, .transport.http.useProxyListFromFile=true, 
-\# .hostsystem..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.
+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
@@ -107,43 +48,58 @@
 .transport.http.extra.PLAYER_SEARCH_MAX_FAIL_STREAK=11
 .transport.http.extra.PLAYER_SEARCH_MAX_FAIL_STREAK.type=java.lang.Integer
 
-This should resolve issue with proxies that are not caught as "IP/proxy" failures.
 
-10) UI logs were reduced for hand history auto-scan tools, now it shows something is something happens or there is a meaningful data to display.
-
-11) GUI: auto-scrolling clickable button-icon for tool results area added.
-
-12) Player search task runs two additional threads: executer with search business logic and cleaner - which will phisycally kill executer thread in case of task timeout. 
-This should resolve issue with some bad proxy got stuck.
+Add
+\# The following settings are only used if .transport.http.useProxy=true, .transport.http.useProxyListFromFile=true, 
+\# .hostsystem..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
 
 
-Upgrade from 1.2:
-1) update /lib/usunpokertools.jar
-
-2) update /config/globalconfig.properties, all changes are optional, you need them only if you need corresponding new features.
-
-Update:
-.hostsystem.opr.extra.ESTIMATED_PLAYER_STATS_ENABLED=true
-.hostsystem.sharkscope.extra.HEADER_USERAGENT=usunpokertools 1.x
-.tool.active=playerscan_history_tournament,playerscan_history_cash,playerscan_console_tournament,playerscan_console_cash,manageplayerscache,manageproxy
-.tracker.hm1.db.url=jdbc:postgresql://127.0.0.1:5432/holdemmanager
-.tracker.hm2.db.url=jdbc:postgresql://127.0.0.1:5432/holdemmanager2
-
-
-New
-.tool.manageproxy.id=manageproxy
-.tool.manageproxy.name=Manage Proxies
-.tool.manageproxy.description=Console to manage proxies, host system access via proxy stats.
-.tool.manageproxy.className=edu.usun.poker.tool.proxy.ManageHostProxyTool
 
 \# The following settings are only used if .transport.http.useProxy=true, .transport.http.useProxyListFromFile=true, 
 \# .hostsystem..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.
-.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
+.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
+
+
+
+\# The following settings are only used if .transport.http.useProxy=true, .transport.http.useProxyListFromFile=true, 
+\# .hostsystem..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
+
+
+\# The following settings are only used if .transport.http.useProxy=true, .transport.http.useProxyListFromFile=true, 
+\# .hostsystem..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
+

WikiPage Home modified by user unknown

user unknown — Fri, 29 Jun 2012 17:02:50 -0000

--- v55
+++ v56
@@ -1,4 +1,4 @@
-[Quick Start] [Licenses and Restrictions] [Features] [Old Releases] [Technical Design] [Developers Guide]
+[Quick Start] [Licenses and Restrictions] [Features] [Old Releases] [Developers Guide]
 
 ---

WikiPage Home modified by user unknown

user unknown — Fri, 29 Jun 2012 02:55:06 -0000

--- v54
+++ v55
@@ -57,7 +57,7 @@
 
 3) Default DB name for HM1,HM2 was changed to holdemmanager, holdemmanager2
 
-4) If "estimated" feature for OPR is enabled, do not use actual money value, use disguising labels instead:
+4) If "estimated" feature for OPR is enabled, do not use numerical estimation values, use category labels instead:
 ROI replacement: d- (the weakest),d+,s-,s+/0 (neutral),f-,f+,w-,w+ (the strongest) - means player strength category; the idea is based on http://www.pocketfives.com/articles/how-much-variance-mtt-s-224464/
 Profit replacement: 0 (operates small amounts),!,!!,!!!,!!!!,!!!!! (operates highest amounts) - it won't show "+" or "-" sign, so it doesn't say if player is actually winning or loosing, just an indicator of volume; 
 Average Buy-In replacement (OPR only): l-(lowest stakes),l,l+,m-,m,m+,h-,h,h+,t (highest stakes) - category for game stakes.

WikiPage Home modified by user unknown

user unknown — Fri, 29 Jun 2012 02:54:13 -0000

--- v53
+++ v54
@@ -58,9 +58,9 @@
 3) Default DB name for HM1,HM2 was changed to holdemmanager, holdemmanager2
 
 4) If "estimated" feature for OPR is enabled, do not use actual money value, use disguising labels instead:
-ROI: d- \[-100;-54\], d+ (-54;-31\], s- (-31;-8\], s+/0 (-8;15\], f- (15;38\], f+ (38;61\], w- (61;84\], w+ (84;+inf) - the idea is based on http://www.pocketfives.com/articles/how-much-variance-mtt-s-224464/
-Profit (+/- won't be displayed): 0 \[0; 1k), ! \[1k; 10k), !! \[10k; 25k), !!! \[25k; 100k); !!!! \[100k; 500k); !!!!! \[500k;+inf)
-ABI (only for OPR): l- \[0;5), l \[5;10), l+ \[10;20), m- \[20; 40), m \[40; 60), m+ \[60; 100), h- \[100; 200), h \[200;400), h+ \[400; 600), t \[600;+inf)
+ROI replacement: d- (the weakest),d+,s-,s+/0 (neutral),f-,f+,w-,w+ (the strongest) - means player strength category; the idea is based on http://www.pocketfives.com/articles/how-much-variance-mtt-s-224464/
+Profit replacement: 0 (operates small amounts),!,!!,!!!,!!!!,!!!!! (operates highest amounts) - it won't show "+" or "-" sign, so it doesn't say if player is actually winning or loosing, just an indicator of volume; 
+Average Buy-In replacement (OPR only): l-(lowest stakes),l,l+,m-,m,m+,h-,h,h+,t (highest stakes) - category for game stakes.
 
 Example note generated: 
 opr2Dec26: Ew+ROI/16ITM/484($l)/516AFS/13RA/$12k(!) 2/10/53/21/13