Merge branch 'release-0.12.0' into dl/animation-player

content/news/2023-10-21-bevy-0.12/index.md

@@ -45,6 +45,78 @@ let clip_handle = player.animation_clip();
 player.seek_to(1.0);
 ```
 
+## Ignore Ambiguous Components and Resources
+
+<div class="release-feature-authors">authors: @hymm</div>
+
+Ambiguity Reporting is an optional feature of Bevy's scheduler. When enabled it reports conflicts between systems that modify the same data, but are not ordered in relation to each other. While some reported conflicts can cause subtle bugs, many do not. Bevy has a couple existing methods and two new ones for ignoring these.
+
+The existing APIs: `ambiguous_with`, which ignores conflicts between specific sets, and `ambiguous_with_all`, which ignores all conflicts with the set it's applied to. In addition, there are now 2 new APIs that let you ignore conflicts on a type of data, `allow_ambiguous_component` and `allow_ambiguous_resource`. These ignore all conflicts between systems on that specific type, component or resource, in a world.
+
+```rust
+#[derive(Resource)]
+struct R;
+
+// These systems are ambiguous on R
+fn system_1(_: ResMut<R>) {}
+fn system_2(_: Res<R>) {}
+
+let mut app = App::new();
+app.configure_schedules(ScheduleBuildSettings {
+  ambiguity_detection: LogLevel::Error,
+  ..default()
+});
+app.insert_resource(R);
+
+app.add_systems(Update, ( system_1, system_2 ));
+app.allow_ambiguous_resource::<R>();
+
+// Running the app does not error.
+app.update();
+```
+
+Bevy is now using this to ignore conflicts between the `Assets<T>` resources. Most of these ambiguities are modifying different assets and thus do not matter.
+
+## Spatial Audio API Ergonomics
+
+<div class="release-feature-authors">authors: @rparrett, @hymm, @mockersf</div>
+
+A simple "stereo" (non-HRTF) spatial audio implementation was heroically [put together](https://bevyengine.org/news/bevy-0-10/#spatial-audio) at the last minute for Bevy 0.10, but the implementation was somewhat bare-bones and not very user-friendly. Users needed to write their own systems to update audio sinks with emitter and listener positions.
+
+Now users can just add a `TransformBundle` to their `AudioBundle`s and Bevy will take care of the rest!
+
+```rust
+commands.spawn((
+    TransformBundle::default(),
+    AudioBundle {
+        source: asset_server.load("sounds/bonk.ogg"),
+        settings: PlaybackSettings::DESPAWN.with_spatial(true),
+    },
+));
+```
+
+## Added HSL methods to `Color` struct
+
+<div class="release-feature-authors">authors: @idedary</div>
+
+You can now use `h()`, `s()`, `l()` together with their `set_h()`, `set_s()`, `set_l()` and `with_h()`, `with_s()`, `with_l()` variants to manipulate _Hue_, _Saturation_ and _Lightness_ values of a `Color` struct without cloning. Previously you could do that with only RGBA values.
+
+```rust
+// Returns HSL component values
+let color = Color::ORANGE;
+let hue = color.h();
+// ...
+
+// Changes the HSL component values
+let mut color = Color::PINK;
+color.set_s(0.5);
+// ...
+
+// Modifies existing colors and returns them
+let color = Color::VIOLET.with_l(0.7);
+// ...
+```
+
 ## <a name="what-s-next"></a>What's Next?
 
 We have plenty of work that is pretty much finished and is therefore very likely to land in **Bevy 0.13**: