filter query

[MoniesRemovalPLC]

trying to create a filter that allow me to see hands where i w3as in the BB (heads up table) and villain opened, i 3bet, and they just called. haven't got it working yet, can you give any tips on what i need to creat this filter.

Also, i created and saved a filter called "called 3B preflop" with the following expression : (Raised Preflop Any 3Bet) AND (Called Preflop Called 3Bet)

now i have seen its not working i'd like to delete it, where are these filter saved so i can delete it please

[kraada]

You can delete it by clicking More Filters and clicking Edit Quickfilters - you can remove Quickfilters from that area.

For your other filter you want Raised Preflop Any 3Bet and not(Opportunity to 5Bet+) and Saw Flop

If you 3bet and didn't have a chance to 5bet or higher they must have called or folded. If you saw the flop they must have called. Since it's heads up we don't have to worry about any other edge cases.

[MoniesRemovalPLC]

tyvm

[MoniesRemovalPLC]

the reason i wanted the filter was to check out something on the auto notes, i have been usind the Preflop ~ 004 Called 3bet in position Range note but it hasn't been recording villains hands where i have 3-bet on a HU table and they just called? May be a problem with that note by the looks of it

[kraada]

Thanks I'll take a look into this for you, the problem might be in the filter definition as the note looks like it's built properly.

[MoniesRemovalPLC]

there 2 notes built in for calling 3-bets preflop, one for in position calls and one for oop calls. i only had the calls 3bet in position active b/c if villain 4Bs that'll show under the 4BvSteal note. The only thing i need is to know is what range they flat a 3-bet with in position with.

[MoniesRemovalPLC]

ok i have done some testing and found that when playing HU, the note 005 -Called 3bet out of position gives the note for the range of hands villain calls our BB 3bet with in position, slightly confusing but at least its working

[kraada]

I see what's causing this incorrect behavior in the filter definition and I'll make certain this gets fixed for the next release.