1,741
edits
(grammar/wording) |
|||
Line 1: | Line 1: | ||
'''Sekinin barai''' {{kana|責任払い}}, or the rule of '''pao''' {{kana|パオ}}, forces | '''Sekinin barai''' {{kana|責任払い}}, or the rule of '''pao''' {{kana|パオ}}, forces a player whose discard is used to form an apparent [[yakuman]] to be liable for partial or full payment if the yakuman-holder wins. It is generally used for yakuman hands only, but certain rules also invoke pao for [[rinshan kaihou]]. Only certain types of yakuman are affected by this rule, which will depend on the ruleset. | ||
== Sekinin barai for yakuman == | == Sekinin barai for yakuman == | ||
Line 9: | Line 9: | ||
* If the yakuman is later won by ron against a non-liable player, that player will pay half the value of the hand. The liable player will pay the other half of the hand, including any extra points for honba. | * If the yakuman is later won by ron against a non-liable player, that player will pay half the value of the hand. The liable player will pay the other half of the hand, including any extra points for honba. | ||
If playing with | If playing with rulesets that recognize [[multiple yakuman]], sekinin barai may be invoked only on certain yakuman. Point exchanges happen independently for each yakuman scored with extra points for any honba paid only once. Honba payments are still paid by the liable player. | ||
==== Example ==== | ==== Example ==== | ||
Line 17: | Line 17: | ||
* North player: 8000 (part of tsuuiisou) | * North player: 8000 (part of tsuuiisou) | ||
=== | === Yakuman affected by sekinin barai === | ||
==== Daisangen ==== | ==== Daisangen ==== | ||
If a player has called two [[mentsu]] of [[ | If a player has called two [[mentsu|groups]] of [[dragon]]s, then calls for a group of the third dragon (upgrading to daisangen), the player who dealt into the third dragon call is affected by pao if the calling player later wins the hand. | ||
: {{#mjt:8s}}, last: {{#mjt:777'z}}, formers: {{#mjt:55'5z}} {{#mjt:1'23p}} {{#mjt:6'66z}} | : {{#mjt:8s}}, last: {{#mjt:777'z}}, formers: {{#mjt:55'5z}} {{#mjt:1'23p}} {{#mjt:6'66z}} | ||
Line 26: | Line 26: | ||
==== Daisuushi ==== | ==== Daisuushi ==== | ||
If a player has called three | If a player has called three groups of [[wind]]s, then calls for a group of the fourth (upgrading to daisuushii), the player who dealt into the fourth wind call is affected by pao if the calling player later wins the hand. | ||
: {{#mjt:5p}}, last: {{#mjt:22'2z}}, formers: {{#mjt:1'11z}} {{#mjt:4'44z}} {{#mjt:333"z}} | : {{#mjt:5p}}, last: {{#mjt:22'2z}}, formers: {{#mjt:1'11z}} {{#mjt:4'44z}} {{#mjt:333"z}} | ||
Line 32: | Line 32: | ||
=== Judgement of liability === | === Judgement of liability === | ||
When the last group of a yakuman is called for an open [[kan]], the discarder is still liable for pao. This may not make sense as first, since the yakuman already existed without needing the kan. | |||
To explain how liability works with "the responsibility of completing an ensured yakuman", it is better to switch to the opponent's point of view. When a yakuman-holder has called for two groups of dragons, daisangen is not guaranteed ''in the opponent's eyes''. Once an opponent discards the third dragon, and it is called for a kan, daisangen becomes guaranteed ''in the opponent's eyes''. So, when discarding a tile used for a kan, pao is still invoked: from the opponent's point of view, daisangen goes from not guaranteed -> guaranteed. | |||
'''Example''': | '''Example''': | ||
Suppose a player completed a daisangen, and the hand looks like the following one in his view: | |||
: {{#mjt:1234m}}, last: {{#mjt:666'6z}}, second: {{#mjt:5'55z}}, first: {{#mjt:77'7z}} (Main perspective) | : {{#mjt:1234m}}, last: {{#mjt:666'6z}}, second: {{#mjt:5'55z}}, first: {{#mjt:77'7z}} (Main perspective) | ||
Toimen becomes the liable player | Toimen becomes the liable player since they allowed the call from the last dragon group. From the winner's perspective, the yakuman was already completed (see below). | ||
: {{#mjt:1234m666z}}, second: {{#mjt:5'55z}}, first: {{#mjt:77'7z}} (Main perspective) | : {{#mjt:1234m666z}}, second: {{#mjt:5'55z}}, first: {{#mjt:77'7z}} (Main perspective) | ||
However, from the opponent's point of view, the daisangen is not guaranteed. | |||
: {{#mjt:0000000z}}, second: {{#mjt:5'55z}}, first: {{#mjt:77'7z}} (Opponent's view) | : {{#mjt:0000000z}}, second: {{#mjt:5'55z}}, first: {{#mjt:77'7z}} (Opponent's view) | ||
It is | It is not an ensured yakuman yet. | ||
:1. | :1. From this point of view, the winner does not "100%" have a concealed triplet of hatsu: (This is also the reason why kamicha, the feeder of second set, doesn't need to be liable for the yakuman hand.) | ||
:: {{#mjt:1234m111z}} {{#mjt:5'55z}} {{#mjt:77'7z}} | :: {{#mjt:1234m111z}} {{#mjt:5'55z}} {{#mjt:77'7z}} | ||
:2. The hand may | :2. The hand may also choose to discard the hatsu triplet (even if highly unlikely): | ||
:: {{#mjt:12345m66z}} {{#mjt:5'55z}} {{#mjt:77'7z}} | :: {{#mjt:12345m66z}} {{#mjt:5'55z}} {{#mjt:77'7z}} | ||
In this case, since the daiminkan of hatsu | In this case, since the daiminkan of hatsu 100% confirmed a daisangen hand in the opponent's view, and killed the other possible development of being a non-yakuman: | ||
: {{#mjt:0000z}}, last: {{#mjt:666'6z}}, formers: {{#mjt:5'55z}} {{#mjt:77'7z}} (Opponent's perspective) | : {{#mjt:0000z}}, last: {{#mjt:666'6z}}, formers: {{#mjt:5'55z}} {{#mjt:77'7z}} (Opponent's perspective) | ||
The relationship of liability is | The relationship of liability is established for toimen, for becoming the feeder of last required set. | ||
This rule also implies a useful strategy of gameplay: | This rule also implies a useful strategy of gameplay: | ||
* If a | * If a call confirms an ensured yakuman, the opponents should have avoided discarding such tile to get rid of the liability. | ||
* If a | * If a call doesn't guarantee a yakuman, the opponents can discard it safely without liability. | ||
=== Yakumans without sekinin barai === | === Yakumans without sekinin barai === | ||
In general sekinin barai | In general, sekinin barai does not apply to other yakuman, since other types of yakuman cannot be ensured even with all required sets are melded. A common point for these yakuman hands is that they both have some limitation of toitsu (the head pair). | ||
==== Shousuushi ==== | ==== Shousuushi ==== | ||
Line 72: | Line 74: | ||
=== Sekinin barai for suukantsu === | === Sekinin barai for suukantsu === | ||
Sekinin barai is occasionally used for [[suukantsu]]: when a player has three kans, then a player discards a tile that allows the fourth kan, the feeder of the fourth kan becomes liable. | |||
: {{#mjt:3z}}, last: {{#mjt:6666'z}}, formers: {{#mjt:0z22s0z}} {{#mjt:3"33m}} {{#mjt:222'2p}} | : {{#mjt:3z}}, last: {{#mjt:6666'z}}, formers: {{#mjt:0z22s0z}} {{#mjt:3"33m}} {{#mjt:222'2p}} | ||
Line 87: | Line 89: | ||
: Kamicha doesn't become liable, suukantsu is not completed yet at the moment when he discarded 2-pin. It was a pon of 2-pin and the hand is only a sankantsu, even though an added kan of 2-pin happens afterwards. | : Kamicha doesn't become liable, suukantsu is not completed yet at the moment when he discarded 2-pin. It was a pon of 2-pin and the hand is only a sankantsu, even though an added kan of 2-pin happens afterwards. | ||
Since it is difficult for an opponent to know which tile would complete the 4th kan, the pao rule is not commonly used for suukantsu. While a player may know which tiles 100% cannot be a kan, which tile exactly is uncertain (compared to daisaigen, where the third dragon always guarantees the yakuman). | |||
== Sekinin barai for rinshan kaihou == | == Sekinin barai for rinshan kaihou == | ||
Sekinin barai is rarely used for [[rinshan kaihou]]. If a player discards a tile, and it is used for a daiminkan, pao is invoked if the daiminkan declarer wins before their next discard. This means that if the daiminkan wins immediately, or wins after making further kans, the discarder is still liable. | |||
While uncommon, some professional mahjong associations use this rule. | While uncommon, some professional mahjong associations use this rule. |
edits