Removed redundant mini-TOCs that appear on random pages

unitALG · unitALG · commit b520e2137fbd · 2025-09-26T14:10:40.000-04:00
- These weren't doc standard compliant and weren't automated (some were missing added sections)
- The sidebar TOCs are already automatically generated by DocFx
diff --git a/Packages/com.unity.inputsystem/Documentation~/ActionAssets.md b/Packages/com.unity.inputsystem/Documentation~/ActionAssets.md
@@ -3,11 +3,6 @@ uid: input-system-action-assets
 ---
 # Input Action Assets
 
-- [Creating Input Action Assets](#creating-input-action-assets)
-- [Editing Input Action Assets](#editing-input-action-assets)
-- [Using Input Action Assets](#using-input-action-assets)
-- [Type-safe C# API Generation](#type-safe-c-api-generation)
-
 An Input Action Asset is an Asset which contains a set of [Input Actions](Actions.md) definitions and their associated [Bindings](ActionBindings.md) and [Control Schemes](ActionBindings.md#control-schemes). These Assets have the `.inputactions` file extension and are stored in a plain JSON format.
 
 The input system creates an Action Asset when you set up the [default project-wide actions](ProjectWideActions.md), but you can also create new Action Assets directly in the Project window.
diff --git a/Packages/com.unity.inputsystem/Documentation~/ActionBindings.md b/Packages/com.unity.inputsystem/Documentation~/ActionBindings.md
@@ -3,32 +3,6 @@ uid: input-system-action-bindings
 ---
 # Input Bindings
 
-* [Composite Bindings](#composite-bindings)
-  * [1D Axis](#1d-axis)
-  * [2D Vector](#2d-vector)
-  * [3D Vector](#3d-vector)
-  * [One Modifier](#one-modifier)
-  * [Two Modifiers](#two-modifiers)
-  * [Writing custom Composites](#writing-custom-composites)
-* [Working with Bindings](#working-with-bindings)
-  * [Looking up Bindings](#looking-up-bindings)
-  * [Changing Bindings](#changing-bindings)
-    * [Applying overrides](#applying-overrides)
-    * [Erasing Bindings](#erasing-bindings)
-    * [Adding Bindings](#adding-bindings)
-    * [Setting parameters](#setting-parameters)
-  * [Interactive rebinding](#interactive-rebinding)
-  * [Saving and loading rebinds](#saving-and-loading-rebinds)
-  * [Restoring original Bindings](#restoring-original-bindings)
-  * [Displaying Bindings](#displaying-bindings)
-* [Control schemes](#control-schemes)
-* [Details](#details)
-  * [Binding resolution](#binding-resolution)
-    * [Binding resolution while Actions are enabled](#binding-resolution-while-actions-are-enabled)
-    * [Choosing which Devices to use](#choosing-which-devices-to-use)
-  * [Conflicting inputs](#conflicting-inputs)
-  * [Initial state check](#initial-state-check)
-
 An [`InputBinding`](../api/UnityEngine.InputSystem.InputBinding.html) represents a connection between an [Action](Actions.md) and one or more [Controls](Controls.md) identified by a [Control path](Controls.md#control-paths). For example, the **right trigger** of a gamepad (a control) might be bound to an an action named "accelerate", so that pulling the right trigger causes a car to accelerate in your game.
 
 You can add multiple bindings to an action, which is generally useful for supporting multiple types of input device. For example, in the default set of actions, the "Move" action has a binding to the left gamepad stick and the WSAD keys, which means input through any of these bindings will perform the action.
diff --git a/Packages/com.unity.inputsystem/Documentation~/Controls.md b/Packages/com.unity.inputsystem/Documentation~/Controls.md
@@ -3,16 +3,6 @@ uid: input-system-controls
 ---
 # Controls
 
-* [Hierarchies](#control-hierarchies)
-* [Types](#control-types)
-* [Usages](#control-usages)
-* [Paths](#control-paths)
-* [State](#control-state)
-* [Actuation](#control-actuation)
-* [Noisy Controls](#noisy-controls)
-* [Synthetic Controls](#synthetic-controls)
-* [Performance Optimization](#performance-optimization)
-
 An Input Control represents a source of values. These values can be of any structured or primitive type. The only requirement is that the type is [blittable](https://docs.microsoft.com/en-us/dotnet/framework/interop/blittable-and-non-blittable-types).
 
 > [!NOTE]
diff --git a/Packages/com.unity.inputsystem/Documentation~/Debugging.md b/Packages/com.unity.inputsystem/Documentation~/Debugging.md
@@ -3,20 +3,6 @@ uid: input-system-debugging
 ---
 # Debugging
 
-- [Debugging](#debugging)
-  - [Input Debugger](#input-debugger)
-    - [Debugging Devices](#debugging-devices)
-    - [Debugging Actions](#debugging-actions)
-    - [Debugging users and PlayerInput](#debugging-users-and-playerinput)
-    - [Debugging layouts](#debugging-layouts)
-    - [Debugging remotely](#debugging-remotely)
-  - [Input visualizers](#input-visualizers)
-    - [`InputControlVisualizer`](#inputcontrolvisualizer)
-    - [`InputActionVisualizer`](#inputactionvisualizer)
-  - [Device Simulator](#device-simulator)
-  - [Unity Remote (iOS, Android)](#unity-remote)
-  - [Other tips:](#other-tips)
-
 When something isn't working as expected, the quickest way to troubleshoot what's wrong is the Input Debugger in the Unity Editor. The Input Debugger provides access to the activity of the Input System in both the Editor and the connected Players.
 
 To open the Input Debugger, go to __Window > Analysis > Input Debugger__ from Unity's main menu.
diff --git a/Packages/com.unity.inputsystem/Documentation~/Devices.md b/Packages/com.unity.inputsystem/Documentation~/Devices.md
@@ -3,41 +3,6 @@ uid: input-system-devices
 ---
 # Devices
 
-- [Devices](#devices)
-  - [Device descriptions](#device-descriptions)
-    - [Capabilities](#capabilities)
-    - [Matching](#matching)
-      - [Hijacking the matching process](#hijacking-the-matching-process)
-    - [Device lifecycle](#device-lifecycle)
-      - [Device creation](#device-creation)
-      - [Device removal](#device-removal)
-      - [Device resets](#device-resets)
-      - [Device syncs](#device-syncs)
-      - [Device enabling and disabling](#device-enabling-and-disabling)
-      - [Background and focus change behavior](#background-and-focus-change-behavior)
-      - [Domain reloads in the Editor](#domain-reloads-in-the-editor)
-  - [Native Devices](#native-devices)
-    - [Disconnected Devices](#disconnected-devices)
-  - [Device IDs](#device-ids)
-  - [Device usages](#device-usages)
-  - [Device commands](#device-commands)
-    - [Sending commands to Devices](#sending-commands-to-devices)
-    - [Adding custom device Commands](#adding-custom-device-commands)
-  - [Device state](#device-state)
-    - [State changes](#state-changes)
-      - [Monitoring state changes](#monitoring-state-changes)
-      - [Synthesizing state](#synthesizing-state)
-  - [Working with Devices](#working-with-devices)
-    - [Monitoring Devices](#monitoring-devices)
-    - [Adding and removing Devices](#adding-and-removing-devices)
-    - [Creating custom Devices](#creating-custom-devices)
-      - [Step 1: The state struct](#step-1-the-state-struct)
-      - [Step 2: The Device class](#step-2-the-device-class)
-      - [Step 3: The Update method](#step-3-the-update-method)
-      - [Step 4: Device registration and creation](#step-4-device-registration-and-creation)
-      - [Step 5: `current` and `all` (optional)](#step-5-current-and-all-optional)
-      - [Step 6: Device Commands (Optional)](#step-6-device-commands-optional)
-
 Physically, Input Devices represent devices attached to the computer, which a user can use to control the app. Logically, Input Devices are the top-level container for [Controls](Controls.md). The [`InputDevice`](../api/UnityEngine.InputSystem.InputDevice.html) class is itself a specialization of [`InputControl`](../api/UnityEngine.InputSystem.InputControl.html). See [supported Devices](SupportedDevices.md) to see what kind of Devices the Input System currently supports.
 
 To query the set of all currently present Devices, you can use [`InputSystem.devices`](../api/UnityEngine.InputSystem.InputSystem.html#UnityEngine_InputSystem_InputSystem_devices).
diff --git a/Packages/com.unity.inputsystem/Documentation~/Events.md b/Packages/com.unity.inputsystem/Documentation~/Events.md
@@ -3,18 +3,6 @@ uid: input-system-events
 ---
 # Input events
 
-* [Types of events](#types-of-events)
-    * [State events](#state-events)
-    * [Device events](#device-events)
-    * [Text events](#text-events)
-* [Working with events](#working-with-events)
-    * [Listening to events](#listening-to-events)
-    * [Reading state events](#reading-state-events)
-    * [Creating events](#creating-events)
-    * [Capturing events](#capturing-events)
-* [Processing events](#processing-events)
-    * [Merging of events](#merging-of-events)
-
 The Input System is event-driven. All input is delivered as events, and you can generate custom input by injecting events. You can also observe all source input by listening in on the events flowing through the system.
 
 > [!NOTE]
diff --git a/Packages/com.unity.inputsystem/Documentation~/Gamepad.md b/Packages/com.unity.inputsystem/Documentation~/Gamepad.md
@@ -3,17 +3,6 @@ uid: input-system-gamepad
 ---
 # Gamepad Support
 
-- [Controls](#controls)
-  - [Deadzones](#deadzones)
-- [Polling](#polling)
-- [Rumble](#rumble)
-  - [Pausing, resuming, and stopping haptics](#pausing-resuming-and-stopping-haptics)
-- [PlayStation controllers](#playstation-controllers)
-- [Xbox controllers](#xbox-controllers)
-- [Switch controllers](#switch-controllers)
-- [Cursor Control](#cursor-control)
-- [Discover all connected devices](#discover-all-connected-devices)
-
 A [`Gamepad`](../api/UnityEngine.InputSystem.Gamepad.html) is narrowly defined as a Device with two thumbsticks, a D-pad, and four face buttons. Additionally, gamepads usually have two shoulder and two trigger buttons. Most gamepads also have two buttons in the middle.
 
 A gamepad can have additional Controls, such as a gyro, which the Device can expose. However, all gamepads are guaranteed to have at least the minimum set of Controls described above.
diff --git a/Packages/com.unity.inputsystem/Documentation~/Installation.md b/Packages/com.unity.inputsystem/Documentation~/Installation.md
@@ -3,11 +3,6 @@ uid: input-system-installation
 ---
 # Installation guide
 
-- [Installation guide](#installation-guide)
-  - [Installing the package](#installing-the-package)
-  - [Enabling the new input backends](#enabling-the-new-input-backends)
-  - [Installing samples](#installing-samples)
-
 This page describes how to install and activate the Input System package for your Unity Project.
 
 > [!NOTE]
diff --git a/Packages/com.unity.inputsystem/Documentation~/Interactions.md b/Packages/com.unity.inputsystem/Documentation~/Interactions.md
@@ -3,23 +3,6 @@ uid: input-system-interactions
 ---
 # Interactions
 
-- [Interactions](#interactions)
-  - [Operation](#operation)
-    - [Multiple Controls on an Action](#multiple-controls-on-an-action)
-    - [Multiple Interactions on a Binding](#multiple-interactions-on-a-binding)
-    - [Timeouts](#timeouts)
-  - [Using Interactions](#using-interactions)
-    - [Interactions applied to Bindings](#interactions-applied-to-bindings)
-    - [Interactions applied to Actions](#interactions-applied-to-actions)
-  - [Predefined Interactions](#predefined-interactions)
-    - [Default Interaction](#default-interaction)
-    - [Press](#press)
-    - [Hold](#hold)
-    - [Tap](#tap)
-    - [SlowTap](#slowtap)
-    - [MultiTap](#multitap)
-  - [Writing custom Interactions](#writing-custom-interactions)
-
 An Interaction represents a specific input pattern. For example, a [hold](#hold) is an Interaction that requires a Control to be held for at least a minimum amount of time.
 
 Interactions drive responses on Actions. You can place them on individual Bindings or an Action as a whole, in which case they apply to every Binding on the Action. At runtime, when a particular interaction completes, this triggers the Action.
diff --git a/Packages/com.unity.inputsystem/Documentation~/Layouts.md b/Packages/com.unity.inputsystem/Documentation~/Layouts.md
@@ -3,16 +3,6 @@ uid: input-system-layouts
 ---
 # Layouts
 
-* [Layout formats](#layout-formats)
-  * [Layout from type](#layout-from-type)
-  * [Layout from JSON](#layout-from-json)
-  * [Generated layouts](#generated-layouts)
-* [Layout inheritance](#layout-inheritance)
-* [Control items](#control-items)
-* [Layout overrides](#layout-overrides)
-* [Precompiled layouts](#precompiled-layouts)
-  * [Creating a precompiled layout](#creating-a-precompiled-layout)
-
 Layouts are the central mechanism by which the Input System learns about types of Input Devices and Input Controls. Each layout represents a specific composition of Input Controls. By matching the description of a Device to a layout, the Input System is able to create the correct type of Device and interpret the incoming input data correctly.
 
 > [!NOTE]
diff --git a/Packages/com.unity.inputsystem/Documentation~/Migration.md b/Packages/com.unity.inputsystem/Documentation~/Migration.md
@@ -3,16 +3,6 @@ uid: input-system-migration
 ---
 # Migrating from the old Input Manager
 
-- [Read the introductory documentation first](#read-the-introductory-documentation-first)
-- [Which system is enabled?](#which-system-is-enabled)
-- [Comparison of API in the old Input Manager and the new Input System package](#comparison-of-api-in-the-old-input-manager-and-the-new-input-system-package)
-  - [Action-based input](#action-based-input)
-  - [Directly reading Gamepad and Joystick controls](#directly-reading-gamepad-and-joystick-controls)
-  - [Keyboard](#keyboard)
-  - [Mouse](#mouse)
-  - [Touch and Pen](#touch-and-pen)
-  - [Sensors](#sensors)
-
 This page is provided to help you match input-related API from Unity's old, built-in input (known as the [Input Manager](https://docs.unity3d.com/Manual/class-InputManager.html)) to the corresponding API in the new Input System package.
 
 ## Read the introductory documentation first
diff --git a/Packages/com.unity.inputsystem/Documentation~/ProcessorTypes.md b/Packages/com.unity.inputsystem/Documentation~/ProcessorTypes.md
@@ -5,21 +5,6 @@ uid: input-system-processors
 
 Below are predefined processors. You can also create custom processors. For guidance on when to use each type, refer to [Using Processors](UsingProcessors.md).
 
-* [Predefined Processors](#predefined-processors)
-    * [Clamp](#clamp)
-    * [Invert](#invert)
-    * [Invert Vector 2](#invert-vector-2)
-    * [Invert Vector 3](#invert-vector-3)
-    * [Normalize](#normalize)
-    * [Normalize Vector 2](#normalize-vector-2)
-    * [Normalize Vector 3](#normalize-vector-3)
-    * [Scale](#scale)
-    * [Scale Vector 2](#scale-vector-2)
-    * [Scale Vector 3](#scale-vector-3)
-    * [Axis deadzone](#axis-deadzone)
-    * [Stick deadzone](#stick-deadzone)
-* [Writing custom Processors](#writing-custom-processors)
-
 ## Predefined Processors
 
 The Input System package comes with a set of useful Processors you can use.
diff --git a/Packages/com.unity.inputsystem/Documentation~/Sensors.md b/Packages/com.unity.inputsystem/Documentation~/Sensors.md
@@ -3,21 +3,6 @@ uid: input-system-sensors
 ---
 # Sensor support
 
-- [Sampling frequency](#sampling-frequency)
-- [`Accelerometer`](#accelerometer)
-- [`Gyroscope`](#gyroscope)
-- [`GravitySensor`](#gravitysensor)
-- [`AttitudeSensor`](#attitudesensor)
-- [`LinearAccelerationSensor`](#linearaccelerationsensor)
-- [`MagneticFieldSensor`](#magneticfieldsensor)
-- [`LightSensor`](#lightsensor)
-- [`PressureSensor`](#pressuresensor)
-- [`ProximitySensor`](#proximitysensor)
-- [`HumiditySensor`](#humiditysensor)
-- [`AmbientTemperatureSensor`](#ambienttemperaturesensor)
-- [`StepCounter`](#stepcounter)
-- [`HingeAngle`](#hingeangle)
-
 Sensors are [`InputDevices`](Devices.md) that measure environmental characteristics of the device that the content is running on. Unity currently supports sensors on iOS and Android. Android supports a wider range of sensors than iOS.
 
 > [!NOTE]
diff --git a/Packages/com.unity.inputsystem/Documentation~/Settings.md b/Packages/com.unity.inputsystem/Documentation~/Settings.md
@@ -3,16 +3,6 @@ uid: input-system-settings
 ---
 # Input settings
 
-- [Create Settings Asset](#create-settings-asset)
-- [Update Mode](#update-mode)
-- [Background Behavior](#background-behavior)
-- [Filter Noise On Current](#filter-noise-on-current)
-- [Compensate Orientation](#compensate-orientation)
-- [Default value properties](#default-value-properties)
-- [Supported Devices](#supported-devices)
-- [Platform-specific settings](#platform-specific-settings)
-
-
 To configure the Input System individually for each project, go to __Edit__ > __Project Settings…__ > __Input System Package__ from Unity's main menu.
 
 This page describes each input setting in detail.
diff --git a/Packages/com.unity.inputsystem/Documentation~/Touch.md b/Packages/com.unity.inputsystem/Documentation~/Touch.md
@@ -3,14 +3,6 @@ uid: input-system-touch
 ---
 # Touch support
 
-- [Touch support](#touch-support)
-  - [`Touchscreen` Device](#touchscreen-device)
-    - [Controls](#controls)
-    - [Using touch with Actions](#using-touch-with-actions)
-  - [`EnhancedTouch.Touch` Class](#enhancedtouchtouch-class)
-  - [Touch Simulation](#touch-simulation)
-  - [Reading all touches](#reading-all-touches)
-
 Touch support is divided into:
 * low-level support implemented in the [`Touchscreen`](#touchscreen-device) class.
 * high-level support implemented in the [`EnhancedTouch.Touch`](#enhancedtouchtouch-class) class.
diff --git a/Packages/com.unity.inputsystem/Documentation~/UISupport.md b/Packages/com.unity.inputsystem/Documentation~/UISupport.md
@@ -3,23 +3,6 @@ uid: input-system-ui-support
 ---
 # UI support
 
-- [Overview and compatibility](#overview-and-compatibility)
-- [Setting up UI input](#setting-up-ui-input)
-- [Required Actions for UI](#required-actions-for-ui)
-- [The UI Input Module component](#the-ui-input-module-component)
-  - [Using the UI Input Module](#using-the-ui-input-module)
-  - [UI Input Module properties](#ui-input-module-properties)
-  - [How the bindings work](#how-the-bindings-work)
-  - [Other notes about the UI Input Module](#other-notes-about-the-ui-input-module)
-- [Multiplayer UIs](#multiplayer-uis)
-- [Virtual mouse cursor control](#virtual-mouse-cursor-control)
-  - [Using the Virtual Mouse component](#using-the-virtual-mouse-component)
-- [Distinguishing between UI and game input](#distinguishing-between-ui-and-game-input)
-  - [Handling ambiguities for pointer-type input](#handling-ambiguities-for-pointer-type-input)
-  - [Handling ambiguities for navigation-type input](#handling-ambiguities-for-navigation-type-input)
-- [Immediate Mode GUI](#immediate-mode-gui)
-
-
 ## Overview and compatibility
 
 Unity has [various UI solutions](https://docs.unity3d.com/Manual/UIToolkits.html). The Input System package's compatibility and workflow with these solutions varies depending on which UI solution you are using, and which version of Unity you are using.
