Quick Guides

1 - Feature List

Introduction

Index of Features!

GS_Core

GS_Managers

• GS_GameManager
• GS_Manager

GS_Save

• Save Manager
• Savers
• List of Savers
• Record Keeper

GS_StageManager

• GS_StageManager
• GS_StageData
• Stage Exit Point

GS_Options

• GS_OptionsManager
• GS_InputOptions
• Input Profiles

GS_Random

GS_Actions

• GS_Action

Utilities

• Physics Trigger Volume
• Springs Utility
• Curves Utility

GS_AI

GS_Audio

GS_Cinematics

GS_Environment

GS_Interaction

Pulsors

• GS_UIManager
• GS_UIManager

Targeting

• Targeting Handler
• Senses Targeting Fields
• Targets
• Interaction Input

World Triggers

• Trigger Actions
• World Triggers

GS_Item

GS_Performers

GS_PhantomCam

• GS_CamManager
• GS_CamCore
• GS_PhantomCamera
• First Person Cam
• Orbit Cam
• Static Orbit Cam
• Camera Influence Fields

GS_RPStats

GS_UI

• GS_UIManager
• GS_UIHub
• GS_UIWindow
• GS_UIPage
• GS_UIButton
• GS_UIAnimationSystem

GS_Unit

• GS_UnitManager
• GS_Controllers
• GS_InputData
• Input Reactor
• Player Input Reader
• GS_Unit
• Mover Context
• Movers
• Grounders

GS_World

2 - Templates List

Template Definition

As described in “Templates”

List of templates

3 - Patterns

Patterns Outline

Patterns

4 - Powerful Utilities

Powerful Utilities Outline

Powerful Utilities

5 - Glossary

GS_Play Definitions

Extensible

tags/extensible/

Extensible means able to be inherited from to augment and expand on the core functionality. Extensible classes and components, identified by the “extensible” tag in the documentation are those that are available on the public Gem.API build target and usable across the lines of gems and projects. Extensible classes usually have Templates to rapidly create child classes, use those to quickly build out your toolset.

Modular

Modular means a system or feature isolated with clear lines between it’s internal structure and the external structure. Furthermore, the base functionality has no outside dependencies. This assures that when you interface with it, you do not require any additional features for it to work innately. This is the common behaviour except for GS_Core, which all other gems are dependent on. This is to assure common and reliable functionality that links all GS_Play systems and allows them to thrive on a common backbone of funtionality and utilities.

Some Modular features are dependent on common O3DE source code featuresets, this is only present when the featureset is to augment and expand on the core functionality. You’ll see this with GS_UI depending on the source LyShine UI system.

O3DE Source Definitions

Class Wizard

The Class creation utility build natively into the O3DE codebase. Use the Class Wizard to create many common classes needed for O3DE project development.

Templates

Templates are pre-designed packages that allow the generative creations of Gems, Components, Classes, and filetypes based on copying and modifying template files to meet systemic needs. Using the Class Wizard