Maksymilian Mozolewski

I just bumped into this problem, this is inconsistent to the other SIMD types and a consistent implementation should really be chosen.

It would be nice to have some sort of "hook" or multiple subscribers indeed

I was thinking some sort of run condition which checks if there are outstanding console events, before running the possibly many console systems would be preferable, albeit it would be...

Okay I think a possible solution would be creating a system which users can opt-in for which "consumes" all keyboard events after the [`console_ui`](https://github.com/RichoDemus/bevy-console/blob/a1b223aaeea33e0af2e4f4591d0048f9483a9900/src/console.rs#L522) system runs. (I believe egui processes...

I've looked into it a bit, something might have broke upstream: https://github.com/rust-lang/rust/issues/100242

Fixed by #27

This would benefit from: https://github.com/jakobhellermann/bevy_mod_js_scripting/issues/5

So out of the box, scripts state is not serialised at all, since state is stored inside the `ScriptContexts` resource and afaik resources are not touched by the scene system...

I've done some more work in the area and I am confident currently the script components will persist a save/load cycle but none-of contexts will so I need to improve...

I am going to split this into two issues. Serializing script variables can be handled by external plugins, you'd just need an `on_serialize` hook which would tell the script to...