Jan Hohenheim
Jan Hohenheim
If this is used for jams, people who worked on the submission need to be credited correctly.
I want to try to move Foxtrot to using pure `bevy_ui` in the future. The biggest blocker right now is that `bevy_editor_pls` is really really useful. Ideally, I'd like something...
https://github.com/Leafwing-Studios/leafwing_manifest/tree/main/examples
Copying this [from a discussion we had a while ago on Discord](https://discord.com/channels/691052431525675048/1124043933886976171/1254029309216161802), [this other list](https://discord.com/channels/691052431525675048/1124043933886976171/1243115219757174824), and a [discussion resulting from me creating this issue](https://discord.com/channels/691052431525675048/1124043933886976171/1263156705697464363) While Avian is currently not ready...
Per my reasoning [here](https://discord.com/channels/691052431525675048/1124043933886976171/1270344315633406002), I personally believe the following to provide the best API: ```rust pub fn plugin(app: &mut App) { app.add_systems(Startup, spawn_zone); app.observe(on_character_entered_zone); } #[derive(Event, CollisionEvent)] struct CharacterEnteredZone {...
Missing stuff: - [ ] #465 - [ ] #466 - [ ] #469 - [x] #444 - [ ] #438 - [ ] #467
- [ ] #451 - [ ] #445 - [ ] #450 - [ ] #453 - [ ] #452
Add a set of physics test cases like [Solver2D](https://github.com/erincatto/solver2d/tree/main/samples/collection) or a lot of Rapier's examples, and maybe an all_examples example that could run all of those test cases, similarly to...
My hierarchy looks something like this: - Fire Exit (has a scale of x = -1, y = 1, z = 1) - RigidBody - Collider 1 - Collider 2...
See Rapier's [`ActiveCollisionTypes`](https://rapier.rs/docs/user_guides/bevy_plugin/colliders/#active-collision-types)