Skip to content
Project referenceDevelopmentEngine ccf7d03f
Authored
  • Shared desktop and Browser Player launch, content validation and application lifetime.

Shared desktop and Browser Player launch, content validation and application lifetime.

Start with composing a runtime host and runtime lifetime.

Platform composition provides content, metadata, adapters, storage, logs and a frame driver. Shared Player code does not read deployment files, create cache directories, depend on Build or reference a concrete content adapter. Internal GamePlayerHost is not a public extension protocol.

  1. IPlayerContentSource.ReadMetadataAsync returns owned manifest/catalog bytes, independent of an external download buffer.
  2. Validate the envelope, application ID, code closure and Pack description; the activator verifies linked static code identity.
  3. PrepareAsync returns a verified read-only content store using the same Pack protocol for file or HTTP sources.
  4. Shell creates adapters; Session reads the asset catalog and read-only Project Settings from the store. Host factories provide storage and logs.
  5. Start the selected Scene and advance the common frame driver.

The source object is borrowed; the store it hands over is Player-owned. Startup failure and cancellation clean up explicitly without fabricating a default Scene or hiding errors.

Retire the Session first, then Settings, Content, Engine and diagnostic owners. Shell finally releases devices and the platform application. Ordinary cleanup errors are aggregated; RetirementPendingException stops downstream release and retains owners still in use. Unfinished retirement is not a successful exit.

A desktop blocking entry uses OwnerThreadExecution.Run. An asynchronous host retains an owner-thread synchronization context. windowVisible=false avoids taking focus for a bounded rendered journey; it does not bypass the rendering lifecycle.

A new content source implements IPlayerContentSource and a content store without changing Session or the asset database. A new host selects a frame driver and adapters. Static Player execution includes neither a collectible loader nor a runtime compiler, and does not weaken Editor unload verification.

Supply live, explicitly owned dependencies as described above. These examples compile against the host contract; they do not initialize a complete product or verify a device.

using System.Threading;
using System.Threading.Tasks;
using Inno.Player.Runtime;
static Task<int> StartPlayer(
PlayerLaunchOptions options,
CancellationToken cancellationToken
) {
return PlayerApplication.RunAsync(options, cancellationToken);
}

The source project defines the host declarations. Source API extraction does not establish script visibility, native behavior or completed generation retirement.

Browse exact types and members.

Project: Inno.Player.Runtime
Source: src/composition/player/Inno.Player.Runtime/Inno.Player.Runtime.csproj

Type API Description
IPlayerContentSource engine Supplies deployment metadata and verified content without prescribing a physical layout.
IPlayerModuleActivator engine Activates a validated logical code deployment through the common module transaction boundary.
PlayerApplication engine Owns the common Player startup, frame execution and verified resource retirement.
PlayerCommandLineOptions engine Parses the shared Player verification and window preferences independently of publication platform.
PlayerContentMetadata engine Owns the two metadata documents required to identify and verify a Player deployment.
PlayerLaunchOptions engine Supplies resolved host services and content to the common Player lifecycle.
StaticPlayerModuleActivator engine Activates explicit linked code without probing assemblies or opening runtime code files.