Hello Unity Tech folks. Why does everything have to be an entity in your examples? Why is their not a very simple method of making a gameObject follow an entity. Don't tell me to restructure my data. It is already atomized and sitting in monobehaviour land. A land it seems forbidden to enter from planet ECS unless you know the correct open sesame secret handshake. I ain't stupid but I ain't a compsci major either. I can get all the data I need from the created entity archetypes to perform a position update to indexed positions that match indexed gameObjects which have..tada! a ParticleSystem attached. Which dies if you convert to an entity or attach it to one. But I can't get that data over to monobehaviour land..or planet ..or universe. I went from making a level every week with all new code and assets to a one month series of crashing to desktop from particles and rigidbodies in monobehaviour and moved over to ECS to see if I could get some physics going. I have that going and am impressed..except..I can't do anything with the entities without trashing everything because of one simple thing which should have been your first thought and not all the tech whiz bang. How the hell can i get a gameObject.transform.position to equal an entity Translation.. I have no problem creating the physics rigidbody entities and attaching and accessing tons of data in ECS land..trying to get a simple array over to a monobehaviour script has been a momentum crushing ordeal to say the least. That being said.. Give us some simple way to do this so we can get on to making games and not plough through loads of boilerplate that after all of that reading still has not shown me one concrete method to get the data from a query over to a mono script. All I hear is..you have to restructure your data. No..I don't..that will take months and still won't work as efficiently as it did and my designer, who has been sidelined for a month now can't do a bloody thing. What Unity needs to do is take all that brainpower and make a simple bridging method with a coherent name that does exactly what it should..send a piece of data, an int, a float, a float3, a bool or an array of them specifically to a bool, int, float, or builtin array of a monobehaviour script. Or did I miss something and because everything always skirts the issue of communication between monobehaviour and ECS land.