> 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/reference/settings.md). # Settings Every option in Project Settings, what it does and when to change it. **Project Settings ▸ Binding System** Five sections. Nothing here has to be changed for the system to work; the defaults are the recommended configuration for a new project.

## Language

Setting	What it does
Language Source	Unity Editor Language follows the editor. System Language follows the OS. Custom lets you pick.
Specific Language	Shown only for Custom. Lists the languages the package ships.

See [Language and Localization](/binding-system-3/reference/localization.md). ## Visualization Everything the binding system draws for you, gathered in one panel as quick toggle cards, no matter which subsystem owns it. **None of these options change how a binding behaves.** Three buttons at the top: **Enable All**, **Disable All**, and a reset that restores the values a fresh project starts with. A counter shows how many are on. **Enable All** sets **Visible Source** to **Auto**, and both buttons leave **Micro UI** alone, since turning it on draws less rather than more.

### Bind fields

Option	What it does
Micro UI	A bound field keeps its own control, showing the value the binding produces, and only the hexagon beside it. The centre of the hexagon lights up to say which value the field shows: green for the binding's, red when it produced none. Click the hexagon to open the whole binding in a popup, right click it to unbind. Switching rebuilds the open Inspectors. See Micro UI.
Visible Source	Starts the path button with the binding's source, in the colour of its source mode: `Player (Transform)→Position`. Off, On, or Auto for only where the whole line fits. See The source on the path.
Popup Target	Heads the bind popup with the bound object and the path of its field; clicking the object pings it. Useful where the popup opens away from the field, as from the Dependency Graph.
Source Replacement	Shows the control that replaces the source object of every binding in a header or group at once. Costs a little extra work when the UI is built, so turn it off if inspectors with many bindings are slow to appear.
Debug At Edit Time	Lets Live Debug report outside play mode. The read side goes through the same accessors the binding uses, so a path that ends in a method is called on every Inspector tick. Turn it off to go back to reporting during play mode only.
Realtime Debug	Refreshes Live Debug values at 60Hz instead of only when the Inspector repaints. Constant repaint. Leave it off unless you are actively debugging.

### Binding menu

Option	What it does
Methods	Lists methods next to fields and properties. Methods are the bulk of what a Unity type exposes, so turning this off makes the menu much shorter and noticeably quicker to build on large types. Bindings already pointing at a method keep working.
Last Used Sources	Recent sources at the top of the menu.
Last Used Pins	Recent pinned paths in the menu. Pinning itself keeps working when off.

### Scene and inspector

Option	What it does
Proxy Bindings	Shows the proxy bindings an object holds, to see at a glance everything it drives. A GameObject shows a read-only list in its Inspector; a ScriptableObject shows its Bindings sub-asset in the Project window. The sub-asset keeps its visibility in its asset's file, so switching this rewrites the assets that hold bindings.
Scene Variables Object	Reveals the GameObject carrying the scene variables in the Hierarchy. Hidden by default because nothing should depend on where it sits.
Scene Visualizer	Draws every binding of the loaded scenes as an arrow in the Scene view. The Bind Visualizer overlay in the Scene view carries the rest of its options. Unlike the other cards on this page, this one is a per-user setting rather than a project one, so it is not shared with the team. See Scene Visualizer.

## Optimization Each option is a card, folded by default. The control sits on the right of the header, with the tag after it, so a folded panel can be read and changed without opening anything; opening one shows what the setting means and whatever extra settings it has. An on-or-off option is a pair of pills, **Enabled** and **Disabled**, rather than a checkbox: the state is in words, and it reads the same way as the options with three choices.

Setting	What it does
Max Bind Path Depth	How deep the bind path menu walks into a single type. Editor only, capped at 4. Reduce this if the editor hangs when opening the binding menu. Existing deeper paths keep working.
Phased Bindings	Switches inspector-set bindings to phased bindings. On an unchanged source the converter and modifiers are skipped, at the cost of a slightly larger build. Read when a binding builds its pipeline, so a change in play mode only affects bindings that start afterwards.
IL2CPP Specializations	Names, at build time, the generic types the bindings will instantiate so IL2CPP compiles them specialised instead of through shared code. Standard types is a fixed set of numeric and Unity value types; All types adds whatever the build's own bindings reach. More code in the build and more memory at runtime, several times faster per call. IL2CPP builds only. See IL2CPP Specializations.
Universal Bind Control	Lets any object update, pause or resume its own bindings through the engine, not only those implementing `IBindController`. Useful for third party components. Every bound object gets tracked, which costs a little memory. Requires a play mode restart. See Controlling Bindings at Runtime.

## Configuration Nine collapsible managers. Each one owns a feature. ### General Settings

Setting	What it does
Bindings Path #	Where the package stores its project data: bind types, meta values, global pins, field routes, generated standard modifiers. Relative to the project root. Defaults to `Packages/com.postica.binding-system/Bindings`. Apply and Move relocates the existing data; Browse picks a folder; the undo arrow reverts an unapplied edit.
Performance Mode	Editor only. Drops the decorative parts of the bind UI. See Performance Mode.
Auto Enable Above	Turns Performance Mode on automatically for an Inspector holding at least this many proxy bindings. 0 never engages automatically. The hint below states the current rule in words.
Auto Register Converters / Modifiers / Providers	Find and register your custom extensions automatically. All on by default. See Extending.

### Standard Modifiers Generates the Set Value, Link To, Value Delayer, Value Logger, Value Events, Value Conditions and Null Check modifiers for types Unity cannot serialize generically.

Setting	What it does
Generate Standard Modifiers	The switch.
+ Add Type	Enables them for a type you cannot edit, such as a Unity or third party type. Types you own use `[EnableStandardModifiers]` instead.
Standard Modifiers Path	Where the generated file goes. Empty means the Bindings folder.

See [Standard Modifiers for Your Types](/binding-system-3/pipeline/standard-modifiers.md). ### Proxy Bindings Manages the project-wide asset that holds [proxy bindings](/binding-system-3/overview/proxy-bindings.md) attached to project assets. Scenes and prefabs carry their own, embedded. ### Pinning Lists every [pinned path](/binding-system-3/overview/pinning.md), grouped by the storage that holds it, with a **Children** badge on paths pinned with **Pin Children**. Remove them from here. ### Fields Rerouting Lists every [field route](/binding-system-3/reference/extending/field-rerouting.md) in the project, with its type, source field and target member. ### Refactor Manager

Setting	What it does
Enable Refactoring	Get the review window and choose per member. Off means an unresolvable proxy binding is removed with no prompt.
Refactor Unity Classes	Also handle members of Unity's own types.
Prefer Renaming Auto Fix	Follow `[FormerlySerializedAs]` and repair an unambiguous rename without asking.

Two buttons in the header, a line reporting how many members are currently waiting for a decision, and the list of **Rules**: every decision applied so far, one row each, with a **⌫** button to forget that one.

Button	What it does
Open Refactor Window	Shows the members bindings point at that no longer exist.
Forget All Rules	Forgets every rule in `Library/bs-refactors.json`. Bindings already rewritten stay as they are; each member is asked about again next time one of its bindings comes up. Confirms first.

See [Refactoring](/binding-system-3/project-tools/diagnostics/refactoring.md). ### Bindings Validator No settings; the checks themselves are chosen in the window, per run. Two buttons in the header:

Button	What it does
Validate Active Scene	Checks every binding in the scene you are working in.
Validate Project	Checks every scene, prefab and asset. Scenes that are not open are opened one at a time and your original set of open scenes is restored afterwards. Slow, and stoppable at any point.

See [Bindings Validator](/binding-system-3/project-tools/diagnostics/validator.md). ### Dependencies

Setting	What it does
Search in Children	A GameObject in the dependency scope also contributes its children. On is usually what you want.

### Build-Time Optimized Accessors

Setting	What it does
Generate Optimized Accessors	Replace deterministic bound paths with generated direct-access methods at build time.
Min Path Pieces	Paths with fewer pieces than this skip codegen.
On Stale Build	Ignore, Warn or Fail Build when the generated set would change. Use Fail Build on CI.
Keep Generated File For Inspection	Keep the file after the build.
Generated Accessors Path	Must be inside `Assets/`.
↻ Generate Now	Runs the scan and writes the file now.

A status card above reports state: *Never generated*, *Up to date*, *Out of date*, *Scanning*, or *Disabled*. See [Optimized Accessors](/binding-system-3/project-tools/performance/optimized-accessors.md). ### Default Bind Data The bind data a newly created binding starts from. Out of the box that is **UPDATE** with **Optimized Update** on, in `Read` mode. Set the flags, mode and [update points](/binding-system-3/overview/modes-and-updates.md) you want as your project's default and every new binding begins there. The update points apply to [proxy bindings](/binding-system-3/overview/proxy-bindings.md), which is where they have an effect. ## Tools Five launchers, each with a description.

Tool	What it shows
Bindings Monitor	All active bindings, their status and their cost.
Bindings Dependencies Analyzer	Dependencies between bindings, with a ↗ Graph button for the graph view.
Bind Variables Manager	Every variable container, scene and asset, in one place.
Bindings Validator	Resolves every binding the way the runtime would and reports what it finds. ↗ Validate Scene and ↗ Validate Project start a run straight away.
Templates	Modifiers, converters and paths saved with their values filled in. One button per tab: ↗ Modifiers, ↗ Converters, ↗ Paths.

## Bindings Path Worth its own note, because moving it is the one setting that touches files. The folder holds the package's project data: registered bind types, meta values, global pins, field routes, and the generated standard modifiers file. It defaults to a folder inside the package, which keeps it out of `Assets` and out of your diff. Move it into `Assets` if you want that data under your own version control layout rather than inside the package folder. **Apply and Move** relocates the existing data; it does not copy it, so there is only ever one. {% hint style="info" %} If the package finds a valid Bindings folder somewhere other than the configured path, for example after a manual move, it adopts it and logs that it has done so. {% endhint %} ## Where settings are stored `ProjectSettings/Packages/com.postica.binding-system/settings.json`, so they are project settings and shared with the team. Two of them, phased bindings and universal bind control, are stored as runtime options rather than editor settings, because the runtime needs them.