en:toolworks:docs:apparatus:networking [Turbopedia]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== Networking ======

While the manual is being written, here is a quick-start guy.

===== Quick-Start Guide =====

  - Create your own Player Controller Blueprint.
  - Add our built-in Network Bearer component to it. This will be the network mediator and must be present in order to push traits to the plain non-Subjective Subjects.
  - Possibly add an additional Subjective component to the same player controller, to push some controlling input Traits from the client to the server. Also make sure this component is set to be replicated via standard Unreal Engine's 'Component Replicates' property (in the Details panel). Also make sure the Subjective has the Traitmark Pass property set correctly. This is a security whitelist for the server to receive only some certain types of traits from the client.
  - Set your custom Player Controller Blueprint as the active one for the current game mode.
  - The custom Player Controller instances for the players will be made online automatically by Apparatus internals.
  - Bring some additional Subjects online on the server via the 'Bring Online' API call.
  - Push the Traits from the client to the server via the dedicated 'Push' API calls on the custom Player Controller.
  - Push the Traits from the server to the clients via the Subject-based 'Push' API calls.