> For the complete documentation index, see [llms.txt](https://wiki.gamee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.gamee.com/gameplay/gamee-arc8-faqs/scoring-system-of-games/samurai-holdem.md). # Samurai Hold'Em Scoring System Players get points for creating combinations of 5 cards from the cards on the table and in their hands (the four columns on the table). Points are scored for the type of hand + the rank of the highest-scoring card. Combination Points Rank Points Royal Flush 4,000 A 75 Straight Flush 3,000 K 70 Four of a Kind 2,000 Q 65 Full House 900 J 60 Flush 700 10 55 Straight 500 9 50 Three of a Kind 300 8 45 Two Pair 175 7 40 One Pair 75 6 35 5 30 4 25 3 20 2 15 For example, a Flush with 9-high would score: 700 + 50 = 750 points for that hand. Upon clearing all the cards from all the hands, the remaining time contributes towards the time bonus. The % of time left is the % of the player’s score added to the base score at the end of the game. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://wiki.gamee.com/gameplay/gamee-arc8-faqs/scoring-system-of-games/samurai-holdem.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.