Great to hear that you are making progress. I am happy to help you out and provide some pointers about the questions you are having for the next steps of your development.
A good starter, even if you have probably already read it, is to go (again) over:
By there I mean that even if you have already gotten the initial grasp on the concepts, a second (or further) read might give you a better feeling for some of the underlying subtleties that you will always miss when encountering SpatialOS for the first time.
That said, let’s move on some of the more detailed points you raise:
Depending off course on what you are trying to do and make the next steps can be:
- Extending the variety of entities that you have in your world, adding new components to enable different behaviours, etc.
The second worker that you connect does not receive any information about pre-existing entities if it is not itself authoritative over at least one component of one entity.
This is strongly tied to your last question: you cannot modify the position of a worker in the simulation, it is rather automatically calculated and updated by the SpatialOS runtime and a worker’s position is sort-of the barycentre of the position of the components (or rather the component’s entities) that it is authoritative over. Hence if a worker is not authoritative over anything it does not have a position and as such will not receive updates about the current state of nearby entities as what “nearby” is, is yet undefined.
Once your worker is authoritative over at least one component and thus has a position then it will start receiving updates about components of other entities nearby according to the bridge configuration of its worker type and any potential ACL settings. A long in-depth post about this was recently posted on the forums. It contains a lot of details that are of importance when scaling-up but it is never too early to read it nonetheless.
Feel free to ask any further questions that may arise. The community and Improbable will be happy to help you out!