RuntimeMeshComponent VS ue5-multiworld-demo

Are you using the RuntimeMeshComponent

Searching for ue4 and modifying a meshes vertex buffer, one quick result was this: https://github.com/TriAxis-Games/RuntimeMeshComponent which seems like a good place to start for modifying meshes at runtime in ue4.

Maybe you could get a better idea of what it does with the pre-built demo: https://github.com/UNAmedia/ue5-multiworld-demo/releases

Secondary Worlds are not network replicated, but you can send RPCs from them. We have an example of it in our sample project on GitHub (https://github.com/UNAmedia/ue5-multiworld-demo), where the changes in the client inventory (a Secondary World) are sent to the server to network-replicate them to all the clients.

The technique you mention is used in the demo application (https://github.com/UNAmedia/ue4-multiworld-demo - there’s also a build ready to download) to showcase a possible use in a multiplayer game: the main world is network-replicated, while a secondary world is used as an “inventory” scene to change the player attributes. While the secondary world is technically not network replicated, it simply calls methods on the actors in the main worlds to take advantage of network replication, replicating the player changes to all the connected clients (using the standard replication system of UE4). I thin in the demo there’s a better description :)