Not sure whose mistake this is. Filter dont working

[Gavolot]

Bevy version

0.12.1

I'm sure that the input works. I checked if it works without entity iteration.

I tried to do a lot. But I don’t understand why the filter simply doesn’t seem to find my essence... It’s like it doesn’t exist. I don't understand.

I cant move player...
I just want the player to move 150 units somewhere =)
But I do everything as in the textbooks, but the component seems to be missing. However, the "sprite" will spawn.

I've already gone crazy searching.

[pablo-lua]

Can you maybe query the Player too with &Player, just so we can know that the problem is indeed the Filter?
Maybe something like:

query_player: Query<&Player>
// the function here...
for player in query_player {
   println!("{}", player.input_id);
}

[Gavolot]

Unfortunately it didn't work.
Now I move on to check the answer below, which says that I may be "duplicating a type or content".

But I don't understand how I can "duplicate" the type itself if it checks "by type".

[pablo-lua]

The problem is that you are using The Player from two different mods, and the compiler is saying, "Hey, that's a different type."
You must assert that you are using the Player from the same mod (at least that is what I got from the answer below)

[akimakinai]

You seem to be dealing with many different Player types, as multiple path attributes to the same file duplicates the content.

Example:

#[path="player.rs"]
mod a;

#[path="player.rs"]
mod b;

fn main() {
    let a = a::Player;
    a == b::Player; // error: mismatched types
    // ^note: `b::Player` and `a::Player` have similar names, but are actually distinct types
}

#[path] is a niche feature to manually tackle special file structures. See the book or the by-example for how you usually can split files in Rust, if the above is not what you wanted.

[akimakinai]

If that was not clear, the code above is simply expanded to this (IIRC):

mod a {
    // content of `player.rs`
    pub struct Player;
}

mod b {
    // content of `player.rs`
   pub struct Player;
}

What compiler actually sees is you declared two different types, which coincidentally have the same name.

You need only a single mod for the player module. If you have mod player; in your crate root, then you can refer to it from anywhere using crate::player::.

[Gavolot]

I still don’t understand why it’s different if I literally wrote down the path to these files.

Those. I understood what happened, but I still don’t understand how to “bypass duplication”. And just add the component.

[Gavolot]

I'm trying, but none of this works, including the generation of cargo boxes))

How was it possible to make such a complex import from folders? I've never seen anything like this before.

[pablo-lua]

You should go back to where you were before, in the first prints, and maybe just try to use the same mod. Maybe defining the Player mod upper in the main file, then doing use crate::player::Player; (something like this)

[Gavolot]

I have now “calmed down” and sat in another empty project. I think I realized a few things. But I will note when it works here that “I decided”. And I'll tell you what happened.

It’s been a long time since I simply stopped being “nervous” during searches. Sorry if I pressed you. These are very new tools for me. It seems I just forgot to register the dependencies in order to load the boxes at all =)

[Gavolot]

You were right! But I just couldn’t understand “what exactly do you mean” because I didn’t add the dependency to “Cargo.toml”

[Gavolot]

Thank you all for your help, with perseverance I finally found what was going on.... This was a real test for me “considering that I am an experienced programmer,” but on all other tools, it was very difficult for me for the last 8 hours.