> 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/getting-started/welcome-screen.md). # The Welcome Screen The window that opens once per version.

## When it opens The window opens twice: on the first import after installing, and again after a version change. It does not open when you simply restart the editor. What decides this is the last version the project was told about, stored in `Library/BS_Welcome.json`.

Stored version	What opens
None	Welcome: the first-run page, with links into the documentation and the tutorials.
Older than the installed one	What's New: the changes between the two versions, newest first.
The same as the installed one	Nothing opens.

The version is saved when you **close** the window, not when it opens. If the editor crashes first, you get the window again. {% hint style="info" %} `Library/` is not under version control, so each person on the team sees the window on their own machine. That is intended. {% endhint %} ## Opening it yourself

Menu	What it does
Window ▸ Binding System ▸ What's New	Opens the window at any time.
Window ▸ Binding System ▸ Reset Welcome Screen	Forgets the stored version and your answers, so the next domain reload treats the project as a fresh install.

## What the update page shows The most important changes get a full row with a picture. The rest are listed below them. If you skip a release, nothing is lost: the window shows every change since the version you were on, not only the newest one. The header says which versions it covers, for example `3.0.0 → 3.1.0`.

The What's New page, covering two versions

## The questions Some releases add a setting whose best default depends on the project. Instead of choosing for you, the window asks once, applies your answer immediately, and does not ask again.

Question	What it means
Keep phased bindings on?	Pipeline stages run only when their input changed. On an unchanged source the converter and modifiers are skipped entirely: a four-stage chain reads in well under half the time on IL2CPP and about a fifth on Mono, while a chain with nothing to cache costs the same as it would fixed. The build is slightly larger. See Phased Bindings.
Let every object control its bindings?	Any object can pause, resume and refresh its own bindings, not only one implementing `IBindController`. Costs a little memory per bound object. See Controlling Bindings at Runtime.
Name your bound types for IL2CPP?	Name nothing, Standard types or Everything I bind. On IL2CPP the pipeline runs through shared generic code unless its types are named at build time; naming them makes a chain of struct members several times faster, at the cost of more code in the player. Mono builds ignore it. See IL2CPP Specializations.
Name the source on the bind path?	Path only, Always or When it fits: whether the path button starts with the binding's source, `Player (Transform)→Position`. See The source on the path.
Draw bound fields as a single hexagon?	Full rows or Micro UI. Micro UI keeps a bound field's own control, showing the value the binding produces, with only the hexagon beside it, its centre lit green or red for the value shown. See Micro UI.

Which questions appear depends on the version you install. All of them are ordinary settings afterwards, under **Project Settings ▸ Binding System ▸ Optimization** or **▸ Visualization**, so you can change your mind at any time. A question you skip is asked again next time. A question you answer is not, unless you use **Reset Welcome Screen**, which clears the answers as well. ## The footer

Link	Where it goes
Documentation	Opens this site.
Tutorials / Full changelog	The video playlist on a fresh install, and the change log after an update.
Settings	Opens Project Settings ▸ Binding System. See Settings.