Identica

engine.yml

Every setting of engine.yml.

engine.yml sets how each scenario runs: whether Identica or the player picks how it gets done, and how long a login that waits for the player is kept. How logins work and Provider choice explain them.

behavior

Timers that apply to every scenario. The defaults suit every network; they only need to be longer than the slowest join.

bridgeTtl

Advanced

Takesa positive duration

Default"10m"

Affectshow long Identica keeps what it found out about a connecting player until their login starts, and a finished login until the player reaches their server

handshakeInstructionTtl

Advanced

Takesa positive duration

Default"10m"

Affectshow long a provider's decision to ask a connecting player for its own login, such as Premium's premium login, stays valid

scenarios

authentication, registration and migration each have these settings.

pipelineTtl

Advanced

Takesa positive duration

Default"5m"

Affectshow long a login that waits for the player is kept

It is also how long a pending move to another provider waits for the player's next join, and how long a username stays held for a connection that is logging in. See Leaving during a login.

allowResume

Warning

Takestrue or false

Defaulttrue

Affectswhether a player who leaves while logging in or registering continues where they stopped when they join again within pipelineTtl

With false, such a player starts over. A reconnect the login asks for itself, such as the rejoin after choosing Premium, always continues. Whether a resumed login may pass an active join restriction is set in join restriction settings.

choice

Takes"AUTOMATIC" or "PROMPTED"

Default"AUTOMATIC"

Affectswho picks how the scenario gets done when several providers, or several methods of one provider, could do it: Identica or the player

A player is never disconnected for having to type something: whatever the choice, they are asked for a password or a code when the picked provider needs one. See Provider choice.

behavior:
  bridgeTtl: "10m"
  handshakeInstructionTtl: "10m"
scenarios:
  authentication:
    pipelineTtl: "5m"
    allowResume: true
    choice: "AUTOMATIC"
  registration:
    pipelineTtl: "5m"
    allowResume: true
    choice: "AUTOMATIC"
  migration:
    pipelineTtl: "5m"
    allowResume: true
    choice: "AUTOMATIC"

On this page