Can any reg comment on this ? I like the idea alot, I just wanted to know what get some input from regs ?

NoteCaddy does support LHE. The only thing to take in consideration is the bet sizing. Any pre flop/flop bet or raise is considered a min bet/raise. Turn and river bets are considered "small" bets but raises are always min raises.

Currently, NoteCaddy won't let you make a definition that would work only for LHE but not NLH as it does not differentiate

If I want to use the notes synchronization, will it be done automatically or do I need to synchro everytime a new note is added?

The problem right now is that you can't synchronize with the client (stars/ftp) open. In the current version 1.09 you do have to manually synchronize. However, the next version is going to allow scheduled synchronization and color coding.



Also, for anyone who didn't see in the newsletter:

NoteCaddy will be running its first definition contest. All participants will play in a free roll so check out the details here http://forums.assaultware.com/showth...nition-contest

The free roll is on December 18th with a $500 prize pool and the best definition writer gets $100.

re - color coding

what happens if a player matches two different color code definitions? how does NoteCaddy color coding handle this.

Each color definition has a "priority" which you can modify. If someone matches two colors of equal priority, then it is whichever comes first alphabetically.

After the last FTP update, it was introduced the feature to change the local time, from ET to something else...

I have set mine to CET, and after this all hands are now recorded with CET time (and also ET time), as follows:

The problem is that now Notecaddy doesn't recognize the hands anymore, generating errors...

Could you please fix it?

Thanks,

Gustavo

Thank you for pointing this out to me gfadel. I have done a fix for this but I am hesitant to release a general patch because there is a chance of regressions. Please download the latest files from http://assaultware.com/NoteCaddy.latest.zip

Copy these files into your c:\program files (x86)\NoteCaddy directory, overwriting any files when prompted. If you experience any other problems please let me know

I didn't work... It freezes when the "finding hands" process is started... The "stop" button doesn't work also...

cheers,

Gustavo

ouch you're right. I did update the zip file though so please try again

It is working now... Thanks a lot!

still trying for plo support before the end of the year?

Definitely trying and I put my chances of success at around 70%. By the end of January we're talking 99%. It will be a separate license though so I hope not to be hated too much for that but it is a ton of work

separate license is to be expected imo

Hey I've been loving the software man, but I have two suggestions for improvement:

1. When displaying a range of hands like:

CC {KK,JJ,AK,AQs,KQs-3,TT,JTs,QJs,QTs,99,88,55-2,33-2,AQ-3,KQ}

It would be nice if this could be displayed like:

KK, JJ-88, 55, 33, AQ+, AQs, KQ, QJs-JTs, etc

I could see not wanting consolidate all the pairs down and making it KK-33 since people might do something different with medium pairs in a certain spot. But the way you have it displayed makes it really hard to process their range in a short period of time and is just messy.

Also could you add a toggle to turn on or off the frequency number? There are some notes where the frequency matters, but with something like CC it's just arbitrary not helpful.

2. And a smaller thing, but how about an option for not displaying the frequency number for "do not take notes for missed opportunities".

[PF]Defends BB {QJs,KTs,T9s,54s,A8s,22,AQ,QJ,JT}(9)
[PF]Defends SB {AJ}(1)

The (1) and the (9) here aren't useful at all.

Again, this is great software and you've put this together in a really amazing way that makes setting up the scripts so easy. This software is very useful and well done.

Also, am I missing something or is there no way to specify "Calls 4bet for less than full stack". So in other words it would count where someone calls a 4b from 22 to 42, but not when someone calls a 4b from 22 to 200.

And hey I'm a developer who used to make and sell software for the fantasy football world, and I remember getting reports like this... but, you seem to have a debugging popup showing up in the test environment screen.

Can this program filter notes by time frame.. could I have it only make notes on hands within the past 6 months?

Thank you for using NoteCaddy and thank you for the suggestions

Apart from the technical challenges of implementing that, there is also the question of personal preferences. Where do you draw the line for the big pocket pairs? 88, 99? No matter where I decide to do it, people will disagree and then I am on the hook for making that configurable. It has been requested several times but I am hesitant to implement it for the above reasons. Unless TJD makes a recommendation, which would be binding

Is this the same suggestion as #2? I am not able to differentiate

I agree with you but there are also some technical issues there. I can look into the possibility of removing them optionally. There are some suggestions that have been made previously that I feel would add more value which would gain higher priority though.

You can specify "player had to act on the flop" in flop->general which ensures he wasn't all in pre flop.

This is true. I have noticed this a bunch of times but always forget when I am actually writing code

Yes. File->filters allows you to specify date ranges among other things

I think you might have misunderstood my suggestion.

So you display this:

CC {KK,JJ,AK,AQs,KQs-3,TT,JTs,QJs,QTs,99,88,55-2,33-2,AQ-3,KQ}

And I'm saying you should display it like:

KK, JJ-88, 55, 33, AQ+, AQs, KQ, QJs-JTs, etc

All I'm saying is that if these are the pairs listed:

KK, JJ, TT, 99, 88, 55, and 33

you can consolidate the sections that have no gaps between them. So it becomes KK, JJ-88, 55, 33. This is shorter, easier to read, and doesn't have the arbitrariness that it has now.

So AK, AQ, AJ becomes AK-AJ, and if there is a range of suited connectors maybe range those as well. Implementation might be slightly harder than just sticking the hand at the end of the string, but it would look alot more professional.

My other suggestion was just that when you have JJ, JJ, JJ you display it as JJ-3, and often this is useless information.

I did understand your suggestion but I didn't express my response correctly. It would be more professional the way you suggest but at this moment any shorter notation is very subjective. It seems that in your implementation you may lose how many times a starting hand was seen. For example if you've had AA-7,KK-2, AJ-1 by my notation what does that say in your notation?

But again, there are alot of times when the the frequencies that a hand were seen is not important.

If a guy cold calls: KK, JJ-88, 55, 33, AQ+, AQs, KQ, QJs-JTs, etc I can estimate his frequencies on my own and they aren't that important for that stat. Granted, they are meaningful some times... for instance even though it would be small sample size, knowing the frequencies for hands a guy flats 4bets with would be very important. Maybe you could have two different types of notation and let users decide for each stat?

Also, is could you just clean up your notation so that:

CC {KK,JJ,AK,AQs,KQs-3,TT,JTs,QJs,QTs,99,88,55-2,33-2,AQ-3,KQ}

is displayed in a non random way like maybe:

CC {KK,JJ,TT,99,88,55-2,33-2,AK,AQs,AQ-3, KQs-3,KQ,QJs,QTs,JTs}

Maybe I'm just a nit but that would look cleaner to me I understand it's not a huge priority.

I agree with the second option here. I also think that it's worth thinking about the number of times somebody does something. Perhaps there could be an option to ignore number altogether, though I personally would not do this.

Another option, more complex, would be to just drop instances off the list that have occurred not often enough to be statistically significant- for example, if someone has done something with KK fifteen times, QQ thirteen times, JJ eight times, TT thirteen times, and once with 55, it's not that useful to know about the 55 because it's such an anomaly and not statistically or practically significant. This is tough because it would matter if the numbers were lik KK (15) QQ (13) JJ (8) TT (13) 99 (5) 88 (5) 77(6) 55 (1) 33 (2), where somebody is clearly playing medium pairs or baby pairs like big pocket pairs in a small number of statistically important instances, and in this case looking at the number is as important as the range.

I think I have found an issue with the way opportunities are counted.

Here's an example i have set up: 3 Bet BB vs SB steal (I want to know what % of the time a player 3bets when the SB opens in a 6-handed game, compared to times he calls or folds).

description: 3b BB vs SB Steal $cardrange
missed opps: "define opportunities by action"
min occurrences: 1
preflop general: position BB
previous actions: I created a "SB steal" action (action has to be folded to player, position SB, open minraise)
Action: Min 3-bet


The problem is it seems to be matching 'missed opportunities' for when other things happen preflop - like when someone else open raises). For example:



PokerStars Game #53071785897: Hold'em No Limit ($2/$5) - 2010/11/22 00:00:00 ET
Table 'Augeias' 6-max Seat #3 is the button
Seat 3: 2pocket8 ($148 in chips)
Seat 4: Hood34 ($368 in chips)
Seat 5: chezlaw ($251 in chips)
Hood34: posts small blind $2
chezlaw: posts big blind $5
*** HOLE CARDS ***
Dealt to Hood34 [8c 4c]
2pocket8: raises $5 to $10
Hood34: folds
chezlaw: folds
2pocket8 collected $12 from main pot
*** SUMMARY ***
Total pot $12 | Rake $0
Seat 3: 2pocket8 (button) mucked
Seat 4: Hood34 (small blind) folded before Flop
Seat 5: chezlaw (big blind) folded before Flop

>>>READ: 3b BB vs SB Steal {} *OPPORTUNITY* PLAYER: chezlaw PROBLEM: incorrect pre flop action


Note this is getting set as an opportunity missed for chezlaw to 3bet - even tho it's the BTN that opens. He never gets the opportunity to 3bet vs a SB steal, which is the point of the definition. The result is everyone ends up with stuff like "2/256 (2%)".

hi Hood,

Can you email the xml file that contains the definition you described to support@notecaddy.com? That way I will be able to quickly analyze what's happening later and get a fix out.