Binding System 3

[ Documentation | Discussions | Tutorials | Video Tutorials ]

Most Unity projects end up with plenty of small scripts whose only job is to copy a value from one object to another. Binding System lets you skip them and connect the values directly. A health bar can follow the player's health, or a door can open as a lever turns.

It works with any field, property, method or event, whether it belongs to Unity, a third party asset or your own scripts. If you prefer, your scripts can also use Bind<float> instead of float, or Bind<T> for any other type, and it still reads like a normal value in code.

Values can be converted or adjusted on the way, for example clamped, remapped or turned into text, with more than 30 modifiers to pick from. The source can be an object you drag in, a shared variable, or something found at runtime by name or tag, so prefabs spawned later can be bound too.

While the game runs, you can watch the value of each binding, and a validator checks the project for bindings that have broken. Bindings are optimized at build time, so they run close to the speed of hand-written code.

For users coming from version 2: Method calls with bound arguments, UI Builder (UI Toolkit) support, Bind Variables, Source modes and a compact Micro UI for bound fields are new in 3.0, along with plenty of other improvements to performance, quality of life and debugging.