> 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/solitaire-star.md).

# Solitaire Star

Scoring System

Each card moved to the deck is worth the base value of +10 points.

Each card moved to the deck in sequence adds +1 to the multiplier bar. The score multiplier bar goes up one multiplier point every 3 consecutive cards placed on the deck. Once the sequence is broken, the multiplier resets to x1.

The score multiplier only applies to the cards moved to the deck.

Each cleared column is worth +100 points. Once the game is completed, a +500 bonus is awarded.

Upon finishing the game, 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/solitaire-star.md?ask=<question>&goal=<user_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.
