Thanks! I am glad you like it!Just to clarify what "taking into account card removal" means:If you take AA for instance in the grid, the spreadsheet goes and count all of the opening range combos possible without these 2 Aces (cause villain can't have them), then it goes and count every combos in the raisecalling range (once again without the 2 Aces) and calculate the chances we are getting called by comparing the number of combos in the raisecalling range by the number of combos in villain's opening range. It does that for every single hand in the grid at the same time. So for KK in the grid it will count combos without these 2 Kings and so on...Also there is a small bug. It's only cosmetic but still...When you exclude 22-55 from the opening range all PP disappear from the calling range text under the drop down box (where you choose your opponent's calling range) 66+ should still be there OBV! thankfully they are only omitted in the text and not in the calculations!. I will fix that. EDIT: i have just fixed that and I am sending the new versions. I' let you know when it's up.

Can you explain please what is AllInternalPasswords in macros section?Just looked into that. it's an excel password cracking subroutine I used to recover my excel password after forgeting it during the holiodays. I didn't realize I left it in there. It's harmless but If you are worried about it go in the developer tab, visual basic and delete the subroutine. There is no need for it

Take any range say Super Tight. Are you taking every card in that range as part of the "Card Removal?" Also as a side issue we are not taking Hero's cards into consideration as part of the "card removal."ok you obviously misunderstood something. I am ONLY taking hero's card into consideration!Let me try to explain: The ranges in the drop down box (like the super tight you mentioned)are the Raisecalling range (meaning the range our villain calls our shove with). Take for instance this same "supertight" raise calling range 66+, A9s, KQs, ATo. It is made up of 126 combos. Now if our villain preflop raises his top 52.04% that's 690 combos. so villain will calls 126/690=18.26% of the time and therefore folds 81.74% of the time (100%-18.26%). Right?Now to make it clearer, lets do the same calculations but this time with card removal. Hero has any hand in the grid. For instance A6o. Now if villain Raisecall with this same "supertight" Raisecalling range 66+, A9s, KQs, ATo, this range is NOW only made up of 103 combos because we have one Ace and one 6 he cannot call our shove with. Also if he still raises his top 52.04% that's now 620 combos only because once again there is one ace and one 6 he cannot raise with (cause they are in our hand). so villain calls 103/620=16.61% of the time and therefore folds 83.39% of the time. Including card removal like in this second calculation is just more accurate (but a pain in the neck to do on a spreadsheet :) )I hope this help. Don't hesitate if you need more clarification.

Does that mean you are taking every possible combo (1326) in the grid working out the % difference & then taking an "average." Because obviously there is no way of imputing Hero's particular hand?   Hero's hands are the hands in the grid! how do you translate that into BB's won or lost? There is a very good and detailed explanation of 3 bet shoving calculations here :  http://forumserver.twoplustwo.com/58...ective-444194/

Any change you could tell me how to remove macros? Sorry to sound to stupid, i have never used open office beforeif you remove the macros it won't work :) PM me with your skype contact and I'll try to help you.

@ raisedaAceI have posted an answer to your problem in the 2+2 thread, let me know.

Update 5.0:There was a bug in one of the hand calc (T6o). When I checked it all, I also found an other small one in the "call your shove calc" formula (luckily it made the results a bit too conservative and not the opposite! ).I fixed it all and while I was at it I also removed the slider for the effective stack. I figured out that it was easier and quicker to type than click endlessly on the slider . That way you guys can also use it for stack> at 25BB if you wish or use more precise effective stacks (decimals other than .5).I also ran many more tests to make sure there wasn't any other bug hanging around. All good!Enjoy it!