The difference is the same as between Bevy’s regular triggers and events. We aim to mirror the Bevy API and simply make it networked.
Events are buffered and pull-style, while triggers are called on commands flush and can target entities and components. Triggers were introduced in Bevy 0.14. Generally, you should use triggers for events that happen rarely and events for things that need to be processed in batches.
I have a special trait that generates a reverse command. And store a stack of commands. Here is the source.
No, I do a full despawn. Just remember it’s data to spawn again thanks to the mentioned trait.