> For the complete documentation index, see [llms.txt](https://postica.gitbook.io/binding-system-3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://postica.gitbook.io/binding-system-3/help/support.md).

# Support

Where to ask, and what to include.

## Before writing in

Two pages answer most of it: [FAQ](/binding-system-3/help/faq.md) and [Troubleshooting](/binding-system-3/help/troubleshooting.md). If the problem is one binding behaving oddly, turning on [Live Debug](/binding-system-3/project-tools/diagnostics/live-debug.md) usually shows the cause in a few seconds.

## Where to write

<table><thead><tr><th width="230">Channel</th><th>Where</th></tr></thead><tbody><tr><td>Email</td><td><a href="mailto:ggpostica.publisher@gmail.com">ggpostica.publisher@gmail.com</a></td></tr><tr><td>Asset Store</td><td>The <a href="https://assetstore.unity.com/publishers/62937">publisher page</a> has a support link.</td></tr><tr><td>Tutorials</td><td><a href="https://www.youtube.com/playlist?list=PLv4Me0tiq_kE9wctI3g495T8CsAndKWkq">The video playlist</a></td></tr></tbody></table>

## What to include

The more of this you send, the more likely the first reply is the answer.

<table><thead><tr><th width="290">Item</th><th>What to include</th></tr></thead><tbody><tr><td>Unity version</td><td>Exact, for example 6000.0.32f1.</td></tr><tr><td>Binding System version</td><td>In the Package Manager, or from <code>BindSystem.Version</code>.</td></tr><tr><td>Scripting backend and platform</td><td>Mono or IL2CPP, and the target.</td></tr><tr><td>Editor or build</td><td>And whether it differs between the two.</td></tr><tr><td>The Console output</td><td>Including the stack trace, not just the message.</td></tr><tr><td>A screenshot of the bind row</td><td>With <a href="/binding-system-3/project-tools/diagnostics/live-debug.md">Live Debug</a> on, if the value is wrong.</td></tr><tr><td>What you expected, and what happened</td><td>One sentence each.</td></tr></tbody></table>

For a reproduction, a minimal scene with one component and one binding is worth far more than a large project. Two objects and one connection is usually enough.

## Reporting a performance problem

Include a screenshot of the [Bindings Monitor](/binding-system-3/project-tools/diagnostics/bindings-monitor.md) footer and its top few rows, sorted by execution time, taken after pressing **Reset** and playing for a while. That single screenshot answers most of the questions that would otherwise be asked.

## Feature requests

Welcome, and useful when they include the situation rather than only the proposed feature. "I need to connect X to Y and the only way I found was Z" leads somewhere; "please add a Z" sometimes does not.

## Translations

The editor UI is translated through simple dictionaries, and contributions are welcome. See [adding a language](/binding-system-3/reference/localization.md#adding-a-language). A table for a language the package does not yet ship can be included for everybody.

## Bug reports

If something is genuinely broken, saying which version last worked is the single most useful detail. The package keeps a version history in `Library/BS_Welcome.json`, and the [welcome screen](/binding-system-3/getting-started/welcome-screen.md) shows the transition after each update.

{% hint style="success" %}
If you turned off [phased bindings](/binding-system-3/project-tools/performance/phased-bindings.md) because something misbehaved, please say what broke. That toggle exists as an escape hatch, and the reports are what remove the need for it.
{% endhint %}