PokerTracker

Struggling to create a note for NFB lines. I want to describe the cases where a player bets or raises once the flush has come with NFB in PLO, and they don't have a boat+.

The filters as set up return hands where a player bets the NFB but flushes aren't possible it's then check down and the flush comes in on the river, or they bet a flushing street with a boat despite 'made hands' flushes or better being set to 'NOT'. Ideally the note would specified bet,bet lines once the flush is in or raises.

I think the problem here is how your logic is set up. You have it set up right now to any time they bet or raise anytime they have the nut flush blocker on any street. That means that sometimes you get times where they bet the flop with the nut flush blocker and the river completes the potential flush and they don't bet there.

So I think what you want to do is reorder your groupings so it's something more like:
(nut flush blocker on river and flush is possible on the river and (bet or raise river))
or
(nut flush blocker on turn and flush is possible on turn and (bet or raise turn))
or
...

You should exclude monotone flops, the filter for nutflushblocker doesn't work correctly for monotone boards (PLO, don't play any holdem).

If you have a hand history where one of the filters doesn't work correctly please attach it to a Support Ticket and tell us exactly which filter doesn't work. The development team are doing some work on the nut flush blockers at the moment and this will help us make sure that we cover all cases correctly.

I guess, you guys should be able to reproduce it easily, because it doesn't work for any HH. Just filter for mono flops and nutblocker and will show all the mono flops where you did have the nutflush, as said I have only PLO hands in my database.

Maybe this workaround works for you.

Code: Select all

and ((not (made flush on flop) and nut flush blocker on flop)
  or (not (made flush on turn) and nut flush blocker on turn)
  or (not (made flush on river) and nut flush blocker on river))

We've identified some issues from the submitted hands and expect to have a fix in our next release.