Online integration (PulseBuildOnlineBridge)
The bridge PulseBuildOnlineBridge gives the party of an owner the owner’s building rights: the members of its Pulse Online party may build in the owner’s claims and change, remove and repair the owner’s pieces, also while the owner is offline. Enable PulseBuild, PulseOnline and PulseBuildOnlineBridge.
Setup
Set Up in the Pulse window adds the step Pulse Build Online Party: it turns on the automatic component of the bridge (Project Settings > Pulse > Build > Online > PartyComponent), which every player controller gets. Or add UPulseBuildOnlinePartyComponent to your player controller yourself.
How it works
- The client of each player reports the player ids of its party members (the net ids of the Pulse Online party) to the server: when the player joins the game and on every party change.
- The server keeps the last list per owner. The rights stay while the owner is offline; a player who left the party keeps them until the owner’s client reports again (its next login).
- Claims, decay in claims and the permission Owner and Team (
bAllowGroup) ask the group of the owner (Pulse::Build::OnCheckOwnerGroup); the bridge answers with the party lists. For the zone rule the group is asked once per claim owner around the piece before the (pure) rule runs, also where the rule stops earlier, so the answer must stay cheap and free of side effects. The server sends every player the owners whose party it is in, so the preview on the client shows the same. - The lists are saved with the building world (an extra of
FPulseBuildSaveData, saved with the bytes of the building world).
The list comes from the owner’s client: an owner can only give rights to others, never get rights from them. Pieces of players without the component (or without party) stay theirs and their team’s.
| Setting | Default | Description |
|---|---|---|
bEnabled | true | Whether party members count as the owner’s group |
PartyComponent | off | Automatic party component on every player controller |
MaxPartyMembers | 32 | Most members a client may report |
Games with a party system of their own
Call UPulseBuildOnlineSubsystem::SetParty(OwnerId, MemberIds) on the server, or ReportPartyMembers of the component on the server. The ids are FPulseBuildOwner::PlayerId (the net id of the player state, or its name without online subsystem). IsInOwnerParty and GetPartyMembers read the lists.
Testing
PulseBuildParty <ids|all|none> reports a party as the client does (all: every other player of the game); PulseBuildPartyInfo prints the player’s id, its party and every party on the server. With two players: the first places a claim (PulseBuildSpawnZone claim), reports PulseBuildParty all, and the second builds inside.