> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/play/layers/game-mechanics/item-slicer.md).

# Item Slicer

A slicing game. The player swipes to slice items as they fly across the screen, and avoids the hazards.

Item Slicer launches items into the play area in batches. The player swipes across them, or taps them, to slice them. Missed items cost health, and slicing a **Hazard Item** costs health too.

### Layers

* **Item 1** to **Item 10** are the items the player slices. The game uses as many as **Number of Items** asks for, and hides the rest.
* **Slice Effect (Sequence)** is the image sequence that plays when an item is sliced. Only used when **Slice Animation** is set to **Sequence**.
* **Hazard Item** is the item the player should avoid. Hidden when **Hazard Item** is off.

### Game Settings

**Items**

* **Number of Items** sets how many different item designs appear, from **1** to **10**. Default is **5**.
* **Item Direction** sets whether items **Rise** from the bottom or **Fall** from the top. Default is **Rise**.
* **Allow Angles** sends items across the screen at an angle instead of straight up or down. Default is **on**.
* **Spawn Interval** sets the time between batches, from **0.1** to **5** seconds. Default is **1s**.

**Mechanics**

* **Slice Animation** sets what happens to a sliced item: **Break Apart** splits it in two, **Sequence** plays the Slice Effect layer. Default is **Break Apart**.
* **Item Speed** sets how fast items move, from **0.1** to **10**. Default is **3**.
* **Items Per Batch** sets how many items launch together: **1**, **2**, **3**, **4**, or a random range of **1-2**, **2-3**, **3-4**, or **4-5**. Default is **3**.

**Special**

* **Hazard Item** mixes hazards in with the regular items. Default is **on**.
* **Hazard Frequency** sets how often hazards appear: **Low**, **Medium**, or **High**. Default is **Medium**. Only shown when Hazard Item is on.

**Swipe Trails**

* **Swipe Trails** draws a trail behind the player's finger. Default is **on**.
* **Swipe Trail Color** sets the trail color. Default is **#FFFFFF**.
* **Trail Thickness** sets the trail width, from **1** to **10**. Default is **5**.

Swipe Trail Color and Trail Thickness only appear when Swipe Trails is on.

### Progression

| Variable            | Default | What it does                                               |
| ------------------- | ------- | ---------------------------------------------------------- |
| **Starting Health** | 10      | The health the player begins with.                         |
| **Loss Per Miss**   | 1       | Health lost for each item that leaves the screen unsliced. |
| **Starting Score**  | 0       | The Score the game begins at.                              |
| **Normal Slice**    | 2       | Points added for each item sliced.                         |

Triggers can watch **Score** and **Health**.

* **Score** rises by Normal Slice for each item sliced.
* **Health** drops by Loss Per Miss for each missed item, and by 1 for each Hazard Item sliced.

**Example triggers:**

* Score **Reaches** 100, action starts your end card scene.
* Health **Drops to** 0, action starts your try-again scene.


---

# 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://help.craftsmanplus.com/play/layers/game-mechanics/item-slicer.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.