Ebus on GS_Play Gameplay Framework

Classifications

Mon, 01 Jan 0001 00:00:00 +0000

The interfaces layer collects exactly three kinds of cross-gem contract. Each kind has a single, recognisable extension story — the suffix tells you which one you are looking at (see the glance test). This page covers each kind in depth and shows how to author against it.

For the contract concept and why the layer exists, start at the Interfaces overview.

TypeBase — Strategy
Emit — Observance
Exchange — Mediator
Hoisting Mechanics
See Also

TypeBase — Strategy

“Inherit this and you’re plugged in.”

Contract Reference

Mon, 01 Jan 0001 00:00:00 +0000

Every contract collected under GS_Core/Interfaces/<Capability>/, the gem that produces it, and its status. For what each kind is and how to author against it, see Classifications.

✦ marks an event or contract created during the interfacing effort (a gap-fill, not a pre-existing notification).

TypeBase — Strategy Bases
Emit — Observance Buses
Exchange — Mediator Buses
Per-Gem Feature Index
Deferred / Not Yet in This Layer
See Also

TypeBase — Strategy Bases

Compiled, editor-pickable. Subclass + reflect → the subtype appears in the type-picker. All nine are shipped and build-verified.

Interfaces

Mon, 01 Jan 0001 00:00:00 +0000

GS_Core/Interfaces/ is the framework’s cross-gem contract layer. Feature gems no longer depend on each other’s internals — they depend on neutral contracts collected here in GS_Core. A contract lives in GS_Core; the feature gem that produces it owns and operates it. GS_Core holds the agreement, the gem holds the behavior.

This is the layer that lets GS_Interaction emit a “pulse received” signal that GS_Juice can react to without either gem including the other.

Ebus on GS_Play Gameplay Framework

Classifications

Contents

TypeBase — Strategy

Contract Reference

Contents

TypeBase — Strategy Bases

Interfaces