[Request] A way to attach data to a world portal for the next world
Synergiance
I'm requesting key-value formatted data that is attached to a world portal and stored in memory for the next world to read when the player enters the portal.
This would be modifiable at runtime, and would be filterable on the receiving side.
The receiving world could have a whitelist of world id's in the scene descriptor, if they wanted to filter what worlds they allow data from.
This effectively would let you transfer data between worlds, of course this can come with limits on the amount of data that can be passed along, but it could give rise to multi-world experiences and smaller world sizes overall.
Log In
naqtn
It might be nice to have attached data as query string of world URL.
soralin
I can confirm this would not only be an extremely handy feature, but it would also lower my projects payload on the server.
At the moment my desire for this is simply just to tell a world which spawnpoint I want the players to spawn in at. My current workaround for this is to upload an identical copy of the world for each "entrance" to it, with just the spawn point moved.
This means for one of my worlds with four "entrances", I have to upload four seperate nearly identical copies of the world.
If we could simply just pass a value into the portal from World A to World B, I would estimate my project would reduce in payload to about 1/3rd its so size or so on VRC's servers, and I would be uploading (and burning bandwidth) to easily 1/3rd the amount.
This would also reduce my actual effort. Everytime I make a change to my worlds atm, I have to upload each copy, which means instead of just 2 uploads (1 for PC, 1 for android), I am on average looking at 6 or so. Which is a lot of extra time spent just to upload the world.
miner28_3
I don't think the size limit would have to be small because data is stored on client not on server but yes this is a perfect idea and I do see a lot of uses for it even for my Game-world!