NTU Forest Bridge Club
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Note Insights Sharing URL Help
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    --- tags: 叫牌 title: 1.4 弱開叫 --- ## 1.4 弱開叫 {%hackmd d2RMsoXWQqKwk15kWYT0Hg %} 想要使用弱開叫,就必須清楚的了解弱開叫的用意——**阻塞**。只有在敵方看起來有成局點力時,阻塞才有意義,否則弱開叫就只是阻塞了自己的同伴,阻塞了自己的分數。 因此,在初學者階段,**第一二家皆不建議弱開叫**,等到同伴 pass 了以後,看到自己手上的牌,感受到敵方很可能有超過 25 點時(如自己只有 3 點,加上同伴最多 11 點,很顯然敵方至少有 25 點以上),這時候拿著一門長牌組出來弱開叫才是最合適的。 :::warning 需遵循 [234 定律](/6zIjLAo8SZ6XvpF42MWHrA),對[**計分方式**](/fxaeMsBPRdGDDnBc58DD9A)及**手牌強度評估**都有一定的瞭解再進行弱開叫。 ::: :::danger 一旦進行了弱開叫,即對自己的手牌已經有了完整的描述,千萬不可以因為同伴幫你加了一線,就又自己再加一線,否則下場只會是被敵方狠狠地砍一刀,來回痛失上千分。 ::: ### 1.4.1 弱二開叫(2D/2H/2S) - **至少要有 AKQ 其中一張帶頭**,如 Q98643。 - ==旁門不可以有 A,也不可以有 4+ 張的另一門高花。== #### 初學版(沒有約就用這個就好了) - 2:diamonds: → 5-11 點,一門 6+ 張的方塊牌組。 - 2:hearts: → 5-11 點,一門 6+ 張的紅心牌組。 - 2:spades: → 5-11 點,一門 6+ 張的黑桃牌組。 #### 進階版(要和同伴特別約過再用) - 2:diamonds: → 5-11 點,一門 6+ 張的紅心或黑桃牌組,~~或是 16-24 點,(4441) 牌組~~。([:building_construction:Multi 2D]()) - 2:hearts: → 5-11 點,5 張紅心和某門 4+ 張的低花。([:building_construction:Muiderberg]()) - 2:spades: → 5-11 點,5 張黑桃和某門 4+ 張的低花。([:building_construction:Muiderberg]()) ### 1.4.2 弱三開叫(3C/3D/3H/3S) 滿足 234 定律的一門長牌組,**必須為弱牌**。 三線開叫通常是 7+ 張的牌組,且點力集中在叫的花色上比較好。 **至少要有 AKQ 其中一張帶頭**,如 K976432。 ==旁門不可以有 A,也不可以有 4+ 張的另一門高花。== - 3:clubs: → 7+ 張梅花牌組 - 3:diamonds: → 7+ 張方塊牌組 - 3:hearts: → 7+ 張紅心牌組 - 3:spades: → 7+ 張黑桃牌組 ### 1.4.3 弱四開叫(4C/4D/4H/4S) (較少使用) 滿足 234 定律的一門長牌組,**必須為弱牌**。 四線開叫通常是 8+ 張牌組,且點力集中在叫的花色上比較好。 **至少要有 AKQ 其中一張帶頭**,如 AJ986543。 ==旁門不可以有 A,也不可以有 4+ 張的另一門高花。== - 4:clubs: → 8+ 張梅花牌組 - 4:diamonds: → 8+ 張方塊牌組 - 4:hearts: → 8+ 張紅心牌組 - 4:spades: → 8+ 張黑桃牌組

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully