You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that this crate is now compatible with Bevy 0.12, so I increased Bevy's version number in my Cargo.toml and ran cargo check. However, my code uses TileStorage, TilemapSize, TileTextureIndex and TilePos in many queries, and apparently, I cannot do that anymore, for they no more are Components. What is the rationale for this change? Is there a workaround?
The text was updated successfully, but these errors were encountered:
There hasn't been a crate.io release of bevy_ecs_tilemap that supports Bevy 0.12 yet. See #488.
The error you are seeing (random things no longer being components) is often indicative of there being multiple versions of Bevy in your dependency tree. A Bevy 0.11Component is a different type than a Bevy 0.12 component.
Unless you're specifying this git repo in your Cargo.toml, bevy_ecs_tilemap is still pulling in Bevy 0.11.
I noticed that this crate is now compatible with Bevy 0.12, so I increased Bevy's version number in my Cargo.toml and ran cargo check. However, my code uses TileStorage, TilemapSize, TileTextureIndex and TilePos in many queries, and apparently, I cannot do that anymore, for they no more are Components. What is the rationale for this change? Is there a workaround?
The text was updated successfully, but these errors were encountered: