Adding callout boxes to all Boss Room pages

Author: jabbacakes

com.unity.netcode.gameobjects/Documentation~/samples/bossroom/architecture.md

@@ -1,5 +1,8 @@
 # Boss Room architecture
 
+> [!WARNING]
+> Boss Room is no longer being actively maintained as of 2026. While it remains available as a learning resource, it may not be compatible with the latest versions of Netcode for GameObjects or Unity.
+
 Boss Room is a fully functional co-op multiplayer RPG made with Unity Netcode. It's an educational sample designed to showcase typical Netcode patterns often featured in similar multiplayer games. Players work together to fight Imps and a boss using a click-to-move control model.
 
 This article describes the high-level architecture of the Boss Room codebase and dives into some reasoning behind architectural decisions.

com.unity.netcode.gameobjects/Documentation~/samples/bossroom/bossroom-actions.md

@@ -1,5 +1,8 @@
 # Boss Room actions walkthrough
 
+> [!WARNING]
+> Boss Room is no longer being actively maintained as of 2026. While it remains available as a learning resource, it may not be compatible with the latest versions of Netcode for GameObjects or Unity.
+
 Boss Room's actions each use a different pattern for good multiplayer quality. This doc walks you through each of them and goes into details about how we implemented each and what lessons you can learn from each. You can get their implementations [here](https://github.com/Unity-Technologies/com.unity.multiplayer.samples.coop/tree/main/Assets/Scripts/Gameplay/Action).
 
 <figure>

com.unity.netcode.gameobjects/Documentation~/samples/bossroom/getting-started-boss-room.md

@@ -1,5 +1,8 @@
 # Getting started with Boss Room
 
+> [!WARNING]
+> Boss Room is no longer being actively maintained as of 2026. While it remains available as a learning resource, it may not be compatible with the latest versions of Netcode for GameObjects or Unity.
+
 Boss Room is a fully functional co-op multiplayer RPG made with Unity Netcode. It's an educational sample designed to showcase typical netcode [patterns](bossroom-actions.md) often featured in similar multiplayer games.
 
 > [!NOTE]

com.unity.netcode.gameobjects/Documentation~/samples/bossroom/networkobject-parenting.md

@@ -1,8 +1,7 @@
 # NetworkObject parenting inside Boss Room
 
-:::note
-Required reading: [NetworkObject Parenting](../../advanced-topics/networkobject-parenting.md)
-:::
+> [!WARNING]
+> Boss Room is no longer being actively maintained as of 2026. While it remains available as a learning resource, it may not be compatible with the latest versions of Netcode for GameObjects or Unity.
 
 Before detailing Boss Room's approach to NetworkObject parenting, it's important to highlight a limitation of Netcode: A dynamically-spawned NetworkObject **can't** contain another NetworkObject in its hierarchy. If you spawn such a NetworkObject, you can't spawn children `NetworkObjects`. You can only add children NetworkObject components to a NetworkObject that is part of a scene.
 

com.unity.netcode.gameobjects/Documentation~/samples/bossroom/networkrigidbody.md

@@ -1,8 +1,7 @@
 # NetworkRigidbody inside Boss Room
 
-:::note
-Required reading: [Physics](../..//advanced-topics/physics.md)
-:::
+> [!WARNING]
+> Boss Room is no longer being actively maintained as of 2026. While it remains available as a learning resource, it may not be compatible with the latest versions of Netcode for GameObjects or Unity.
 
 Boss Room leverages `NetworkRigidbody` to simulate physics-based projectiles. See the Vandal Imp's tossed projectile, the [`ImpTossedItem` prefab](https://github.com/Unity-Technologies/com.unity.multiplayer.samples.coop/blob/main/Assets/Prefabs/Game/ImpTossedItem.prefab). At its root, this Prefab has a NetworkObject, a `NetworkTransform`, a `Rigidbody`, and a `NetworkRigidbody` component. Refer to [`TossAction.cs`](https://github.com/Unity-Technologies/com.unity.multiplayer.samples.coop/blob/main/Assets/Scripts/Gameplay/Action/ConcreteActions/TossAction.cs) for more implementation details.
 

com.unity.netcode.gameobjects/Documentation~/samples/bossroom/optimizing-bossroom.md

@@ -1,5 +1,8 @@
 # Optimizing Boss Room performance
 
+> [!WARNING]
+> Boss Room is no longer being actively maintained as of 2026. While it remains available as a learning resource, it may not be compatible with the latest versions of Netcode for GameObjects or Unity.
+
 Optimization is critical for networked and non-networked games. However, you have more limitations and constraints to consider when building a networked game. For example, networked games must account for latency, packet loss, reliability, and bandwidth limitations.
 
 One of the more critical optimizations of a networked game is how much bandwidth it consumes. The following issues can occur with networked games that have high bandwidth usage:

com.unity.netcode.gameobjects/Documentation~/samples/bossroom/spawn-networkobjects.md

@@ -1,8 +1,7 @@
 # Spawn NetworkObjects in Boss Room
 
-:::note
-Required reading: [Object Spawning](../../basics/object-spawning.md).
-:::
+> [!WARNING]
+> Boss Room is no longer being actively maintained as of 2026. While it remains available as a learning resource, it may not be compatible with the latest versions of Netcode for GameObjects or Unity.
 
 This document serves as a walkthrough of Boss Room's approach to solving the following issue: Late-joining clients entering networked sessions encountering zombie `NetworkObjects`. Zombie `NetworkObjects` represent `NetworkObjects` that are instantiated for a client due to scene loads but aren't despawned or destroyed by Netcode.