Source metadata

Key takeaways

  • Unity now presents the Input System package as the preferred input solution for most projects.
  • The older Input Manager remains available for legacy projects, but the documentation frames it as secondary.
  • The Input System package is installed through the Package Manager, not treated as part of the old built-in UnityEngine.Input workflow.
  • Unity highlights the package’s flexibility and editor-side configuration workflow, especially the Actions editor.

Notable claims

  • Unity’s manual says the Input System package provides the engine’s “best support” for input.
  • The Input System package is described as more extensible and customisable than the classic UnityEngine.Input approach.

Relevance

This source primarily informs:

It also supports:

Open questions raised

  • Where should the vault draw the line between beginner-friendly legacy input teaching and current-package best practice?
  • Which parts of the Input System are most important for students before controller rebinding and advanced device support?