#bevy #enum #filter #variant #query


Filter by enum variant in Bevy queries

4 releases (2 breaking)

0.3.0 Nov 18, 2023
0.2.0 Sep 2, 2023
0.1.1 Oct 6, 2022
0.1.0 Oct 6, 2022

#6 in #enum-variants

Download history 6/week @ 2023-11-01 5/week @ 2023-11-08 40/week @ 2023-11-15 14/week @ 2023-11-22 18/week @ 2023-11-29 14/week @ 2023-12-06 10/week @ 2023-12-13 15/week @ 2023-12-20 8/week @ 2023-12-27 12/week @ 2024-01-03 10/week @ 2024-01-10 5/week @ 2024-01-17 12/week @ 2024-01-24 14/week @ 2024-01-31 7/week @ 2024-02-07 63/week @ 2024-02-14

96 downloads per month


120 lines


Crates.io Docs License

Filter queries by enum variants!

In Rust, enum variants aren't types. This means we normally can't filter for them in a Bevy Query. The alternative, then is to use a set of "marker" components. This works well enough, but we miss out on the semantics of using an enum (and the ability to perform enum-specific operations such as match-ing).

This crate allows us to query for entities based on the specific variant of an enum component:

use bevy::prelude::*;
use bevy_enum_filter::prelude::*;

#[derive(Component, EnumFilter)]
enum ItemType {

fn apply_potion(item_query: Query<(Entity, &ItemType), Added<Enum!(ItemType::Potion)>>) {
  // ...

fn main() {
    // ...
    .add_systems(Update, apply_potion)

๐Ÿ“ฒ Installation

Add the following to the [dependencies] section of your Cargo.toml.

bevy_enum_filter = "0.3.0"

๐Ÿคจ How it works

Surprise! It's just marker structs!

Deriving EnumFilter generates a module containing a marker struct per variant. The module is named using the enum's name (snake-cased) followed by _filters. For example, our ItemType enum generates the following module:

// Auto-generated!
mod item_type_filters {
  pub struct Equippable;
  pub struct Weapon;
  pub struct Potion;

When we then register our enum using app.add_enum_filter, we are adding a system that watches for changes (additions/mutations) related to that enum component. The system will then add or remove the appropriate marker struct whenever there's a change.

The Enum! macro then takes the given enum path and grabs the corresponding marker struct from the module. So Enum!(ItemType::Potion) corresponds to the item_type_filters::Potion type.

๐Ÿ“ข: This is why you must have your generated module in scope!


Because this is basically just change detection under the hood, it's important to remember when the filter actually takes effect. By default, the system added by app.add_enum_filter runs in the PostUpdate stage. This means you will not see the filter work until the that stage is complete.

And remember that any components changed in Update would not see their filters work until PostUpdate anyway since we need to cross a stage boundary for commands to flush. This means we realistically only lose out on a single stage.

If you need it to run after a certain system or within a certain stage, you could always add the watch_for_enum system yourself.

๐Ÿ•Š Bevy Compatibility

bevy bevy_enum_filter
0.8.1 0.1.0
0.11.x 0.2.0
0.12.x 0.3.0


~198K SLoC