public static abstract sealed class Sandbox.Global
Utility info for tools usage.
Related Guides
Broader workflow and conceptual references connected to this API.
Your game can record stats for each player that plays it. Here are some examples of things stats can record.
If you add a UnitTests directory to your project folder, we will automatically generate a Unit Test project for you. In order for the project to be generated you need to restart your editor if you have it open.
Your game can have multiple achievements for players to unlock.
Editor Events are events that are broadcast globally throughout the editor and can be listened to/fired from any Editor Project. These are useful for creating your own custom Editor Tools and making sure they can work in tandem with existing systems.
The global namespace has a bunch of useful variables.
The "Model Editor", also known as "ModelDoc", is where you can create and edit model (VMDL) files. This is the modern equivalent of Source 1's .QC files. You can find it under the "Tools" menu.
Properties
Showing 6 properties
public static string Sandbox.Global.BackendTitle { get; set; }
Front facing identity for the backend
public static string Sandbox.Global.BackendUrl { get; set; }
Url for the backend
public static string Sandbox.Global.GameIdent { get; set; }
Identity of the gamemode the local client is currently playing.
public static bool Sandbox.Global.InGame { get; set; }
Is the local client in game or not.
public static bool Sandbox.Global.IsApiConnected { get; set; }
Are we connected to the API? (If not, offline mode. Requires Steam Servers to be online to connect..)
public static string Sandbox.Global.MapName { get; set; }
Name of the map the local client is on.
No results match this filter.
Metadata
| Field | Value |
|---|---|
| Namespace | Sandbox |
| Type | class |
| Assembly | Sandbox.Tools |
| Doc ID | T:Sandbox.Global |