Overview
The In-Game Application Center normally runs as a standalone experience — it fills the screen and the application is the game. You can also load it inside the Activity Tracking module, where it behaves as an optional window players open on demand. In this embedded mode it:- doesn’t take over the game — movement, camera, and the topbar stay fully usable (no lockdown);
- opens as a window by default (or full-screen if you prefer), with a close button;
- is opt-in — you point the loader at the Application Center module and it handles everything else;
- can be opened from the ReAdmin topbar, your own UI (client API), or server code (server API).
Embedding reuses your existing Activity Tracking
loaderId and the Activity
Tracking module you’ve already installed — there’s nothing extra to download or
configure in your game. Forms still flow into Forms exactly as
they do standalone — only the presentation changes.Enabling it
The Application Center is toggled from workspace settings, not your game code — exactly like Calls. Nothing changes in your loader.- Go to Settings → Downloads.
- Under In-Game Application Center, turn on Enable in your game.
- Choose how it appears (see Display options below).
The setting is delivered to your servers when they start (in the same way the
Calls toggle is), so newly-started servers pick it up automatically — existing
servers apply it on their next start.
Display options
Both options live next to the enable toggle in Settings → Downloads:| Setting | Options | Default | Description |
|---|---|---|---|
| Display mode | Windowed / Fullscreen | Windowed | Whether the panel floats over your game as a window, or fills the screen. |
| Dim the game behind it | On / Off | Off | Darkens and blocks the game behind the window while it’s open. |
Developers / testing: the loader config accepts an optional
applicationCenter field to point the tracker at a specific Application Center
build (a ModuleScript or asset id) while testing — e.g.
applicationCenter = script.Parent.ApplicationCenter. It only overrides which
module loads; whether the Application Center loads at all is still controlled by
the workspace setting above.Client API
When the Application Center loads embedded, you can open it from your own LocalScripts through the existingReAdminClientAPI BindableFunction (the
same handle used to start calls):
| Action | Options | Description |
|---|---|---|
openApplications | – | Opens the Application Center on the openings list. |
openApplication | { applicationId } | Opens the Application Center straight to that posting. |
closeApplications | – | Closes the Application Center window. |
These actions no-op when the Application Center isn’t enabled, so it’s safe to
call them unconditionally. The
applicationId is the form’s id from
Forms.Server API
The loader returns the ReAdmin table — keep a handle to it and you can open the Application Center for a player from trusted server code (a proximity prompt, an NPC, or an automated “you’ve been invited to apply” flow):| Method | Parameters | Returns |
|---|---|---|
OpenApplications | player | true, or false, errorMessage |
OpenApplication | player, applicationId | true, or false, errorMessage |
CloseApplications | player | true, or false, errorMessage |
ReAdmin.ApplicationCenter also exposes the underlying module handle for advanced
callers. All three methods return false with a message when the Application
Center isn’t enabled.
Like the rest of the server API, these are server-only — they’re not exposed
as a client-invokable remote, so exploiters can’t trigger them. Call them from
code you trust.
Good to know
- Opt-in only. Without the
applicationCenterconfig, nothing changes — the Activity Tracker behaves exactly as before, and the standalone Application Center is untouched. - Resilient. If the Application Center module can’t load, it’s logged and skipped — activity tracking keeps running normally.
- Same data everywhere. Embedded or standalone, submissions land in Forms with the same auto-grading and rank-based eligibility.