|bevy vewsion:|0.9 |(outdated!)| |---|---|---|

As this page is outdated, please refer to Bevy's official migration guides while reading, to cover the differences: 0.9 to 0.10, 0.10 to 0.11, 0.11 to 0.12, 0.12 to 0.13, 0.13 to 0.14.

I apologize for the inconvenience. I will update the page as soon as I find the time.

weact to changes with asset events

if you nyeed to pewfowm specific a-actions when an a-asset is cweated, modified, (ꈍᴗꈍ) ow wemoved, ^•ﻌ•^ you can make a-a system that weacts to AssetEvent events.

#[dewive(wesouwce)]
stwuct mymapimage {
    handwe: h-handwe<image>, mya
}

f-fn fixup_images(
    m-mut ev_asset: e-eventweadew<assetevent<image>>,
    m-mut a-assets: wesmut<assets<image>>, nyaa~~
    m-map_img: wes<mymapimage>, (⑅˘꒳˘)
) {
    f-fow ev in ev_asset.itew() {
        match ev {
            assetevent::cweated { handwe } => {
                // a textuwe w-was just woaded ow changed! rawr x3

                // wawning: this mutabwe a-access wiww cause anothew
                // a-assetevent (modified) to be emitted! (✿oωo)
                wet textuwe = a-assets.get_mut(handwe).unwwap();
                // ^ unwwap i-is ok, (ˆ ﻌ ˆ)♡ because w-we know it is woaded nyow

                if *handwe == map_img.handwe {
                    // it is ouw speciaw m-map image! (˘ω˘)
                } ewse {
                    // it is some othew image
                }
            }
            assetevent::modified { h-handwe } => {
                // an image w-was modified
            }
            a-assetevent::wemoved { h-handwe } => {
                // a-an image was unwoaded
            }
        }
    }
}

note: if you awe handwing Modified events and doing a mutabwe access t-to the data, XD the .get_mut wiww twiggew anothew Modified event fow the same asset. OwO if you awe nyot cawefuw, 🥺 this c-couwd wesuwt i-in an infinite w-woop! òωó (fwom events caused by youw own system)