> For the complete documentation index, see [llms.txt](https://sheets.bed.codes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sheets.bed.codes/advanced/platform-specific.md).

# Platform-Specific

Sheets is designed to provide a unified experience across Java and Bedrock Edition, but some features are platform-specific.

### Unified Titles

You can provide different titles for Java and Bedrock within a single configuration.

```yaml
title:
  java: "&cJava Inventory"
  bedrock: "&bBedrock Form"
```

If a simple string is provided, it will be used for both platforms.

### Bedrock-Specific Features

#### Button Images

Bedrock forms support images on buttons. You can provide a URL or a resource path.

```yaml
buttons:
  - slot: 0
    material: DIAMOND
    name: "&bDiamond Button"
    image: "https://example.com/diamond_icon.png"
```

#### Bedrock-Only Content

You can define items and content that will only be visible to Bedrock players.

```yaml
buttons:
  - slot: 1
    material: BEDROCK
    name: "&cBedrock Players Only"
    requirements:
      view:
        - "%sheets_is_bedrock% = true"
```

See [Requirements](/features/requirements.md) for more information on conditions.

### Java-Specific Features

#### Chest Edit Mode

The visual [chest editor](/features/editor.md#1-chest-edit-mode-java-only) is only available to Java players.

#### Inventory Types

Java supports various inventory types (e.g., HOPPER, DISPENSER, BREWING\_STAND), which are rendered as standard forms on Bedrock.

#### Advanced Lore and Formatting

Java Edition supports more complex text formatting and multi-line lore that may be rendered differently in Bedrock forms.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sheets.bed.codes/advanced/platform-specific.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.