Skip to main content

​
Usage

Usage is measured for the active workspace. It is not combined across every workspace that belongs to the same developer account.
Always confirm the active workspace in the top navigation bar before reviewing limits or usage.

​
Main usage categories

​
Where usage appears

Usage can be shown in several parts of Launcher Forge:
  • Current-plan indicator in the top bar.
  • Subscription and plan pages.
  • Branch overview storage card.
  • Team member count.
  • Game and launcher counters.
  • CLI Account / usage view.
  • Add-on pages for additional capacity.

​
CLI usage summary

After authentication, the CLI can display:
  • Current plan.
  • Storage used and total.
  • Bandwidth used and total.
  • Games used and allowed.
This confirms the active account and capacity before publishing a build.

Launcher Forge CLI

Review the CLI account summary and publishing menu.

​
Storage usage

Storage is consumed by workspace artifacts such as published build files and their associated data. Before uploading a build, review:
  • Current storage used.
  • Total plan capacity.
  • Build size.
  • Remaining capacity.
  • Active storage add-ons.
A full STABLE release can require more uploaded data than a PATCH or HOTFIX, depending on the manifests and file hashes.
Never remove required runtime files only to fit a storage limit. Test the final packaged build locally before publishing.

​
Bandwidth usage

Bandwidth represents data transferred to players through downloads and updates. Consumption can be affected by:
  • Number of active players.
  • Build size.
  • Frequency of updates.
  • Number of files changed.
  • Repeated downloads.
  • Public or private testing groups.
Additional bandwidth can be provided by an applicable add-on.

​
Games and launchers

Game usage increases when a new Catalog game is created. Launcher usage belongs to the workspace. Launcher Forge currently uses one launcher for the workspace. When a plan limit is reached, the dashboard can prevent the creation of another resource.

​
Team members

Accepted workspace members count toward the team-member capacity shown by the active plan. Review:
  • Active members.
  • Pending invitations.
  • Members who no longer need access.
  • Role assigned to each account.
Removing a member frees workspace access without deleting that person’s account.

​
Branch usage

Plans can limit:
  • Number of branches per game.
  • Availability of private branches.
Before creating a new branch, review the game’s existing channels and remove obsolete non-default branches only when their builds and access are no longer required.

​
Add-on capacity

Add-ons can increase a specific usage category. Examples:
Add-on capacity:
  • Applies to the workspace.
  • Does not change the base plan name.
  • Can expire separately.
  • Is managed by the Owner.

​
When usage reaches a limit

Launcher Forge can restrict actions such as:
  • Uploading another build.
  • Creating another game.
  • Inviting another member.
  • Creating another branch.
  • Enabling a feature not included in the plan.
Possible actions:
  1. Remove or archive unused resources when supported.
  2. Reduce unnecessary packaged files.
  3. Remove unused team members.
  4. Delete obsolete non-default branches when appropriate.
  5. Upgrade the plan.
  6. Purchase an applicable add-on.
  7. Contact support for a custom entitlement when available.

​
Usage after changing plans

After an upgrade, the workspace receives the new plan capacity and features when the plan becomes active. After a downgrade, compare current usage with the new limits. A workspace above the new limit may be prevented from creating additional resources until usage is reduced.

​
Role access

Review usage:
  • Before publishing a large build.
  • Before inviting another member.
  • Before creating another game or branch.
  • Before downgrading.
  • Before a public launch or large update.
  • When storage or bandwidth notifications appear.
Usage is under control when the workspace has enough capacity for the next build, update, team invitation, and expected player traffic.

Plans and limits

Understand which capacity is included in the plan.

Subscription

Upgrade the plan or review Owner-only billing actions.

Builds

Understand how build artifacts and updates affect storage and bandwidth.