This was marked as fixed a while back. I've requested for it to be tested again. There isn't a HM3 ticket to be notified with, because it's a NC ticket. I will make an update here when I hear back.Originally Posted by shaymalus
This was marked as fixed a while back. I've requested for it to be tested again. There isn't a HM3 ticket to be notified with, because it's a NC ticket. I will make an update here when I hear back.
Hi Shaymalus,
Apparently you need to use the HM3 VPIP stat rather than the Compiled version to get the color coding to work as you expect, at the moment.
Compiled stats sometimes aren't synced up with the HM3 stats, and this is likely what is causing the issues for you. I'm told that the compiled and HM3 stats should match up after HM3 is restarted though. Please let me know if you see otherwise.
It appears there is some sort of bug with the HM3 compiled stats, which won't make them match up even after HM3 is restarted. This issue is being addressed.
Last edited by NotecaddyEdge; 09-02-2020 at 09:21 AM.
This bug is still present.
So basically color coding has been broken for all of 2020.
Hi shaymalus,
Did you try using only HM3 stats and NoteCaddy stats, while omitting Compiled stats in your Color Coding definitions?
From what I gather there are 3 types of stats you can use in Color Coding Definitions
1. HM3 stats
2. NoteCaddy stats
3. Compiled stats
#3, Compiled stats, is the one that has a bug that needs addressed from what I understand. Please let us know if that is incorrect.
Last edited by NotecaddyEdge; 12-09-2020 at 02:09 PM.
I am only using HEM3 VPIP, and the bug is present.
I'm not using compiled stats. I doubled checked.
Btw: My database is PLO only hands
I tried testing this feature out, but I believe it's applying incorrect colors for me as well.
We are doing some more testing and will make sure the developers are aware, so that they can issue a fix.
Thank you for the extra details, and bringing it up again.
Upon further investigation, it looks like colors are applied correctly from what I can see on my end.
I was thrown off because the pokerstars notes.xml file which NoteCaddy writes to was showing color codes that don't match with the colors that are applied at the tables.
So it might be that some things here are applying to you: http://wiki.assaultware.com/Color-co...Read-this.ashx
For instance, NC could be applying a color to a player for heads-up, but then that player sits at your 6-handed table, and you see his heads-up color.
Do you think any of these things in this link apply to some of the inconsistencies you were seeing with the color coding? http://wiki.assaultware.com/Color-co...Read-this.ashx
Ok I tried "TEST" to my definitions, and I think I've identified the source of the bug:
I will attach screenshot of my definition to illustrate.
- all of my definitions use "Min players = 3" , Max = 10
- this is supposed to exclude all heads up hands, and not color the player for HU hands
- Heads up hands are returning "OUTPUT: SUCCESS for game Omaha CashGame - 2 players" , and thus assigning this colour when it should not be
I had set "priority" higher for the high vpip colours
Hi shaymalus,
Thank you for the details. Is it possible for you to check a player who only has HU hands, to see if he was assigned a color in PokerStars?
It might be that the Test feature just ignores game sizes completely, so I just want to be sure before writing it up for the developers.
Posting Permissions
Reply With Quote