Configuration

A setting can have default, user, and project values. Its effective value depends on the scopes it supports and which value overrides another.

Common scopes

• User: affects projects opened by the current user.
• Workspace or project: affects the current game project and can express team conventions.
• Default: supplied by PinK or a feature module when no override is set.

Change settings

Use PinK's Settings interface: ⌘, on macOS or Ctrl+, on Windows and Linux. You can also search for Settings in the Command Palette. Check whether you are editing user or workspace settings.

The interface can show types, available values, groups, descriptions, and specialized editors. Editing files directly can bypass that guidance. If a setting is missing, search by name and check whether it requires an initialized project or enabled feature.

Some features react immediately to changed settings. Others require reloading the window or restarting a task. Follow the setting description and interface feedback.

Project isolation

Project settings belong to the current project. After switching projects, do not assume that a previous project's value still applies. Check the current scope and effective value when diagnosing configuration problems.