You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the odds are the 4 of a kind is much harder to get then the tractor. So the 4 of kind (Bomb, e.g. 8888) should be higher than the tractor even it's has higher cards(e.g. AAKK) regardless which one is played 1st.
I guess this is based on how many decks of card are used. I think the 4 of a kind would extend to when playing any tractor the other player should play all the same card to beat the tractor, e.g.: JJQQ < 6666, or AAAKKK < 777777, etc.
The text was updated successfully, but these errors were encountered:
blu-world
changed the title
Request: Option to make 4 of a kind (Bomb, e.g.: 8888) bigger then tractor (e.g. KKQQ)
Request: Option to make 4 of a kind (Bomb, e.g.: 8888) bigger then tractor (e.g. KKQQ) in Finding Friend
Oct 15, 2022
in general the system does not currently permit winning a trick with any set of cards of incorrect format (e.g. JJQQ is a tractor, and 6666 is not). I think this is a fairly well-understood part of the game, similar to how you can't play 222 to beat KK in pairs, even though triples are rarer than pairs.
Changing this would make evaluation pretty confusing for people, since if you have 2233 and 6666, I would presume that you have to play 2233 on a tractor trick format, not 6666...
that said, what you're suggesting is theoretically doable, it just seems pretty unique
It seems that the odds are the 4 of a kind is much harder to get then the tractor. So the 4 of kind (Bomb, e.g. 8888) should be higher than the tractor even it's has higher cards(e.g. AAKK) regardless which one is played 1st.
I guess this is based on how many decks of card are used. I think the 4 of a kind would extend to when playing any tractor the other player should play all the same card to beat the tractor, e.g.: JJQQ < 6666, or AAAKKK < 777777, etc.
The text was updated successfully, but these errors were encountered: