I have setup a domain project which is being populated with an ORM. The domain contains of different aggregates each with its own root object. My question is how properties that
You should avoid DB references across BCs - you shouldn't try to ensure referential integrity between aggregates from different BCs (transactions). Ideally, transaction should live only inside single aggregate, not even BC.
Better use simple value objects for IDs - UserId and GameId - and assign them to entity if needed. This way those "remote" entities are completely detached so you don't have to worry about their connection. Sync could be implemented using messaging platform.
If you have spare time read these valuable articles (by Vaughn Vernon):