# Glossary Welcome to the **Game Launcher Cloud Glossary**! This page contains definitions of all key terms, concepts, and features used throughout the platform. {% hint style="info" %} **Quick Navigation**: Use the table of contents on the right to jump to any letter, or use `Ctrl+F` (Windows) / `Cmd+F` (Mac) to search for specific terms. {% endhint %} *** ## A | Term | Definition | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Addon Service** | Additional paid features or services that can be added to a subscription plan, such as extra storage, additional team seats, or premium support. | | **Angular** | The modern TypeScript-based web framework used to build the Game Launcher Cloud frontend. Provides reactive programming, component-based architecture, and signals for state management. | | **API** | Application Programming Interface - A set of protocols and tools that allows different software applications to communicate with each other. Game Launcher Cloud provides a RESTful API for programmatic access. | | **Application** | A game or software project registered in Game Launcher Cloud. Each application can have multiple builds across different environments (Development, Staging, Production). | | **Analytics** | Data tracking and reporting features that provide insights into launcher downloads, user engagement, news views, and player behavior. | | **Authentication** | The process of verifying user identity. Game Launcher Cloud supports email/password authentication and Google OAuth. | | **Auto-Update** | Feature that automatically checks for and downloads new game versions when a launcher is opened, ensuring players always have the latest content. | *** ## B | Term | Definition | | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Backend** | The server-side infrastructure built with .NET that handles data processing, API requests, authentication, and business logic for Game Launcher Cloud. | | **Build** | A compiled and packaged version of your game or application. Builds are uploaded to Game Launcher Cloud and associated with specific environments and versions. | | **Build Number** | A unique identifier assigned to each build version. Typically follows semantic versioning (e.g., 1.0.0, 1.2.5). | | **Build Pipeline** | An automated process that handles build compression, validation, distribution to CDN, and deployment across environments. | *** ## C | Term | Definition | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Calendar Event** | Visual representation of time-based events in the dashboard calendar, including build releases, news publications, scheduled maintenance, and promotional events. | | **CDN** | Content Delivery Network - A distributed network of servers that delivers content to users based on their geographic location. Game Launcher Cloud uses Cloudflare R2 for global distribution. | | **CLI** | Command Line Interface - Text-based tools that allow developers to interact with Game Launcher Cloud through terminal commands for automation and scripting. | | **Cloudflare R2** | Object storage service used by Game Launcher Cloud for storing and distributing game builds, launcher files, and media assets globally. | | **Collaborator** | A team member invited to work on a workspace or project with specific permissions and role assignments. | | **Compression** | The process of reducing file sizes to optimize download speeds and storage. Game Launcher Cloud automatically compresses builds during upload. | | **Custom Domain** | The ability to use your own domain name (e.g., launcher.yourgame.com) instead of the default Game Launcher Cloud URLs. | *** ## D | Term | Definition | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Dashboard** | The main administrative interface where users manage applications, launchers, builds, news, and settings. | | **Deployment** | The process of making a build available to end users through a launcher. Can be done across different environments (Development, Staging, Production). | | **Development Environment** | A testing environment where developers can test new builds before releasing them to staging or production. | | **Download Manager** | Component within launchers that handles file downloads, progress tracking, pause/resume functionality, and integrity verification. | *** ## E | Term | Definition | | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Endpoint** | A specific URL path in the API where clients can access a particular resource or function (e.g., `/api/applications`, `/api/launchers`). | | **Environment** | A deployment stage for your application. Game Launcher Cloud supports three environments: Development (testing), Staging (pre-production), and Production (live). | | **Event** | A time-based occurrence tracked in the platform such as build releases, news publications, scheduled maintenance, or promotional campaigns. Events can be displayed in calendar views and linked to specific entities. | | **Event Status** | The lifecycle state of an event: Draft (being created), Scheduled (planned for future), Published (currently active), Completed (finished), or Cancelled (not happening). | *** ## F | Term | Definition | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------- | | **Feature Flag** | A configuration toggle that enables or disables specific platform features, allowing controlled rollout and A/B testing. | | **Frontend** | The client-side user interface built with Angular that users interact with. Includes the web dashboard and launcher interfaces. | | **File Integrity** | Verification process that ensures downloaded files are complete and uncorrupted using checksums and hash validation. | *** ## G | Term | Definition | | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | **Game Build** | See **Build** - A packaged version of your game ready for distribution. | | **Google OAuth** | Authentication method that allows users to sign in using their existing Google accounts, eliminating the need for separate credentials. | *** ## H | Term | Definition | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Hash** | A unique fingerprint generated from file contents used to verify file integrity and detect changes. Common algorithms include MD5, SHA-1, and SHA-256. | | **Hotfix** | A quick patch or update deployed to fix critical bugs or issues in production without going through the full release cycle. | | **HTTP Status Code** | Standardized numerical codes returned by the API indicating the result of a request (e.g., 200 = Success, 404 = Not Found, 500 = Server Error). | *** ## I | Term | Definition | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **i18n** | Internationalization - The process of designing software to support multiple languages and regions. Game Launcher Cloud uses ngx-translate for i18n support. | | **Integration** | Connection between Game Launcher Cloud and external services like Discord, Slack, or webhooks for notifications and automation. | *** ## J | Term | Definition | | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **JWT** | JSON Web Token - A secure method of transmitting information between parties as a JSON object. Used for authentication and authorization in Game Launcher Cloud's API. | *** ## L | Term | Definition | | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Launcher** | A desktop application that players use to download, update, and launch your game. Can be a Single Launcher (one game) or Multi-Launcher (multiple games). | | **Launcher Appearance** | Customization options for your launcher including branding, colors, logos, backgrounds, and UI themes. | | **Launcher Build** | A compiled version of the launcher application itself (separate from game builds), distributed to end users. | | **Linked Entity** | A reference connection between an event and other platform entities like apps, launchers, news posts, or builds. | | **Load Balancing** | Distribution of network traffic across multiple servers to ensure reliability and performance. | | **Localization** | Adapting software to specific languages, regions, and cultural conventions (see **i18n**). | *** ## M | Term | Definition | | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | | **Multi-Launcher** | A launcher that can host and manage multiple games or applications in a single interface, useful for game studios with multiple titles. | | **Manifest** | A configuration file that describes the contents, versions, and metadata of a build or launcher. | | **Metadata** | Additional information about files, builds, or resources including version numbers, descriptions, tags, and timestamps. | *** ## N | Term | Definition | | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------- | | **News** | Announcements, updates, patch notes, or promotional content pushed directly to launchers to engage players. | | **News Analytics** | Tracking data for news posts including views, clicks, engagement rates, and conversion metrics. | | **Notification** | Alert or message sent to users about events like build completions, updates available, or news published. | | **Notification Preferences** | User settings that control which types of notifications they receive and through which channels (email, in-app, etc.). | *** ## O | Term | Definition | | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | **OAuth** | Open Authorization - An open standard for access delegation, allowing users to grant applications access to their information without sharing passwords. | | **Object Storage** | Cloud storage architecture for unstructured data (files, images, videos). Game Launcher Cloud uses Cloudflare R2 for object storage. | *** ## P | Term | Definition | | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | **Patch** | An update that modifies existing game files rather than replacing everything. More efficient than full downloads for small changes. | | **Permissions** | Access control settings that determine what actions users or team members can perform within the platform. | | **Plan** | A subscription tier that defines the limits, features, and pricing for using Game Launcher Cloud (Free, Starter, Pro, Enterprise). | | **Production Environment** | The live environment where stable, tested builds are deployed and made available to all players. | | **Progressive Download** | Download technique that allows games to start playing before the entire download is complete. | *** ## R | Term | Definition | | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | | **Referral Program** | System that rewards users for inviting others to the platform, often with credits or discounts. | | **REST API** | Representational State Transfer API - An architectural style for designing networked applications using HTTP requests to access and manipulate data. | | **Release Notes** | Documentation that accompanies a new build or update, describing changes, new features, bug fixes, and known issues. | | **Rollback** | The process of reverting to a previous build version if issues are discovered in a newer release. | | **Role** | A set of permissions assigned to users defining what they can access and modify (e.g., Admin, Developer, Viewer). | *** ## S | Term | Definition | | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------- | | **Seat** | A license for a team member to access and collaborate on a workspace, with quantity limits based on subscription plan. | | **Semantic Versioning** | A versioning scheme using three numbers (MAJOR.MINOR.PATCH) where each number indicates different types of changes (e.g., 2.1.3). | | **Session** | An authenticated user's active connection to the platform, tracked for security and used for session management. | | **Single Launcher** | A launcher dedicated to a single game or application, ideal for indie developers or single-title studios. | | **Staging Environment** | A pre-production environment that closely mimics production, used for final testing before public release. | | **Storage** | Cloud space allocated for storing builds, assets, and files. Plans include different storage limits. | | **Subscription** | A paid plan that provides access to platform features with specific limits and pricing (Monthly or Yearly billing). | | **System Config** | Global platform configuration settings that control feature availability, authentication methods, and build management options. | *** ## T | Term | Definition | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | **Team Collaboration** | Features enabling multiple users to work together on projects, including role assignments, permissions, and shared access. | | **Token** | A secure credential used for API authentication. Can be temporary (JWT) or long-lived (API key). | | **Torrent** | Peer-to-peer file distribution protocol that can reduce server load by allowing users to share downloads with each other. | | **Translation** | Converted text strings for different languages, managed through JSON files in the i18n system. | | **TypeScript** | Strongly-typed programming language that extends JavaScript, used throughout Game Launcher Cloud for type safety and better developer experience. | *** ## U | Term | Definition | | -------------------- | ---------------------------------------------------------------------------------------------------------------------- | | **UI** | User Interface - The visual elements and controls through which users interact with the platform or launchers. | | **Upload** | The process of transferring game builds or assets from your local machine to Game Launcher Cloud's servers. | | **User Management** | Administrative features for handling user accounts, authentication, permissions, and team organization. | | **User Preferences** | Customizable settings for individual users including language, theme, notification preferences, and UI layout options. | | **User Profile** | Personal account information including avatar, display name, email, security settings, and subscription details. | *** ## V | Term | Definition | | ------------------- | ------------------------------------------------------------------------------------------------------------------------- | | **Validation** | Process of checking form inputs, data, and file integrity to ensure correctness and security. | | **Version Control** | System for tracking and managing different versions of builds, allowing rollbacks and historical comparisons. | | **Versioning** | The practice of assigning unique identifiers to different iterations of software or builds (see **Semantic Versioning**). | *** ## W | Term | Definition | | ------------- | -------------------------------------------------------------------------------------------------------------------------------- | | **Webhook** | Automated HTTP callbacks triggered by specific events (e.g., build completed, news published) that can notify external services. | | **Whitelist** | A security feature that restricts access to specific approved users, IP addresses, or domains. | | **Workspace** | A logical grouping of applications, launchers, and resources belonging to a user or organization. | *** ## Related Resources
📚 API ReferenceComplete REST API documentationhttps://github.com/GameLauncherCloud/GameLauncherCloud-Gitbook/blob/main/docs/API-Reference.md
🏗️ ArchitectureTechnical overview of the platformhttps://github.com/GameLauncherCloud/GameLauncherCloud-Gitbook/blob/main/docs/Architecture.md
🚀 Getting StartedQuick start guide for new usershttps://github.com/GameLauncherCloud/GameLauncherCloud-Gitbook/blob/main/docs/broken-reference/README.md
*** {% hint style="success" %} **Missing a Term?** If you encounter a term not listed here, please let us know at or in our Discord community! {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://gamelauncher.cloud/help/reference/glossary.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.