Not sure of the best way to solve this problem: I have multiple threads (from a single job) which all might need to set the same component on the same, target entity. In this case, the data of the component being set doesn’t actually matter. It can be an empty component. I just want to assign it, to increment its “changed” version, so that that component will be picked up by an EntityQuery (with a change filter) in the next system. (Imagine 10 assassins seeing the same target, and the target just needs to know that it was “seen”, to be worked on by the next system.) But I’m pretty sure that having several threads assign the same component value in parallel, even if that component is empty, is dangerous if not unsupported. And even if it is, it sure smells bad. Would you have any advice on how I should be approaching the problem? Thanks for any help.