Trying to take some of Stone's comments one at a time.

Am I making money on limps? Don't know, but I'm at 16 ptbb/100 so far, despite losing one full stack getting it all in with nut straight on turn and getting quadded on river.

As to the overall stat of 36/16: at some tables I'm playing like 18/18 more or less and at others maybe upper 30s. Anyhow, the 36 part has gone down.

With the A6o, I really am starting to feel MUCH more confident with hands like that 6max, although I hate them FR. I actually feel a bit wt because I'll generally fold it to a raise, but I'll raise it OTB pretty much every time. I think folding it is really only good if you get into a game where you're almost going to have to play for stack when you hit your A. But seriously, I just had a great pot vs. a bluffer that I picked off with A4. I think a lot of it is figuring out whether your opponent is attempting to buy or value-betting.

Anyhow, your first post sounds to me tighter than necessary for 6max (probably leaving some good money at the table, too, although no doubt decreasing variance a bit)--and trust me, I'm perhaps the biggest diehard advocate of tight for FR that there is!

I should note that my current trend is tightening up a bit from the 36 (I'm down to 33 now and probably running more like 26 or so usually since the old 36 part of the database is still counted) and limping less. But I still think there can be good reasons to limp both weakish hands and monsters.

I think it was bk who recommended something like 25/18 as optimal, and that sounds about right--but imo there are tables where 36/16 is quite reasonable and tables where 18/16 is more like it. I think the trick is adjusting your play so as to play or not play the more marginal candidates (AX, offsuit connectors, Q8s, etc.) and also limping anywhere from fairly often to almost never depending on the game.

And back to Stone: Surely you jest about not playing KJo to a raise 6max. I don't even think twice about playing to a raise or raising myself on KTo unless raiser seems just horribly nitty.