Setup Play-in-Editor

Setting up the common classes

When making a new project off of Origin's defaults, the following is a list of classes to consider making your own versions of, to extend the Origin functionality whilst adding your own:

Summary

Asset to overrideCopy or Inherit?Where to apply?

BP_Origin_GameMode

Inherit

Project Settings -> Default GameMode, or World Settings -> GameMode Override

BP_Origin_PlayerController

Inherit

In the Game Mode

BPM_Origin_PlayerSpawner

Inherit

World Settings -> Player Spawner Class

BPM_Origin_PlayerCharacter

Inherit

In your player spawner

BP_Origin_PlayerCharacter

Inherit

Per role's LOD Level set (see the further details)

BP_Origin_HUD

Inherit

In the Game Mode

WBP_Origin_HUD

Copy

In your HUD BP

DT_Origin_Roles

Copy

World Settings -> Default Role & Data Tables

PDA_Skin_Origin

Copy

Project Settings -> Default Skin

DT_Origin_SettingList

Copy

In your Skin

In more detail:

  • The GameMode: This configures a bunch of the classes used in your level, e.g. the player controller and HUD classes outlined below. If you want to make a new game mode, it should extend BP_Origin_GameMode

    • To apply your game mode, you can either modify per-level in your world settings, or modify the default in your project settings -> Maps & Modes.

  • The Character:

    • The PlayerController: Should extend BP_Origin_PlayerController.

    • The Morpheus Actor: The representation of a client's character that is used for replication. Should extend BPM_Origin_PlayerCharacter.

      • To make sure your correct morpheus actor is spawned, you should also update the "Player Spawner". Use BPM_Origin_PlayerSpawner as a base, and you can modify the PlayerMorpheusActorClass field in it.

    • The Render Target Actor(s): The actual character spawned in-game to represent a player. Should extend BP_Origin_PlayerCharacter

      • To make your new render target actually get used, you need to configure it in your roles table (see below):

        • For a given role, its PawnLodLevelSet controls what render target is used.

        • If you make a new pawn set asset (copying the existing one), you can swap out its Base Pawn and LOD0 Actor Class

  • The UI:

    • The HUD BP: The logic responsible for spawning the HUD, and managing our UI. Should extend BP_Origin_HUD.

    • The HUD WBP: The actual HUD widget that contains the in-game UI. To use your own HUD widget, we recommend making a copy of WBP_Origin_HUD. To use your new HUD, you can change the Game Layer Class in your HUD BP.

  • The Roles table: This controls which roles are available to your players. If you want to modify this, make a copy of DT_Origin_Roles. For more details on roles, see Roles.

  • The Skin: This is responsible for the styling of your UI etc. If you want your own skin, make a copy of PDA_Skin_Origin. For more details on skins, see How to use skins.

  • The Settings table: When you open the "Escape Menu", this table dictates what is present in the UI. If you want to change this, you should make a copy of DT_Origin_SettingList, and set your skin asset's Settings Skin Settings -> Settings Data Table field to your new table.

There are some other base classes in origin that can be used as valid starting points, such as BP_PlayerController, or BPM_M2_PlayerCharacterBase. However, these will be missing some of the expected Origin features, so only use these if you really know what you're doing.

Setting up the map

When making a new map, check the world settings, to make sure everything is as expected:

  • The Singletons: There are a number of singleton actors that are spawned when the game is started, and enable various bits of Origin functionality. For more details on these, see Singletons.

    • Of these, the PlayerSpawnerClass is one you may want to change - if you want to use a different morpheus actor, swap out the player spawner class with the one you created.

  • The Roles table: You can configure the default role, and the roles table used here

  • The GameMode Override: Make sure it points to your new game mode

Configuring to use MMLs

There are a currently a few workarounds required for full functionality (especially related to MMLs) when using Play-in-Editor functionality.

The following sections are current required to place MMLs when in Play-in-Editor mode - this requirement will be removed in a future update.

Ensure you're using the correct game mode

You need to be using the BP_Origin_GameMode (configurable via world settings), or a game mode that is a child of this.

You may need also need to add this change to the template maps: InfinitySpace and Meadow. A fix for this will be rolled out in a future release.

Configuring Authentication

Set up server credentials

In Editor Preferences, in the Sign-in settings section, change your settings to reflect the following where:

  • Offline Mode is NOT ticked

In the Editor, click on the "Editor Sign In" button on the toolbar

You will be requested to sign in with your Google Account in your main system browser. Once complete, you will be presented with a list of api keys:

The name will depend on the key your organization admin set up.

Select the key they instructed you to use and click "ok".

Set up client credentials

In Editor Preferences, in the Sign-in settings section, change your settings to reflect the following where:

  • Offline Mode is NOT ticked

  • The Per Client Sign In Settings property has the Single Sign On element

Last updated