Heathen's API

Become a GitHub Sponsor Join our Discord Find us on the Web in the Unity Asset Store
Search…
Heathen's API
Getting started with the Heathen Steam API
Like what your seeing?
Consider supporting us as a GitHub Sponsor and get instant access to all our Unity assets, exclusive tools and assets, escalated support and issue tracking and our gratitude.

These articles are made possible by our GitHub Sponsors ... become a sponsor today!
Introduction
Heathen's Steam API is a wrapper around Steamworks.NET which is its self a wrapper around Valve's own Steam API.
Valve's Steam API is written in C/C++ has questionable documentation 😉
 and uses programming styles foreign to most Unity developers and even most C# programmers.
Steamworks.NET is a true to form wrapper around Valve's Steam API. This means that while the syntax has been updated to use C# styling the design paradigm is still very much a relic of older and more importantly unmanaged styles. One of the most obvious examples of this is the use of Callback and CallResult to handle delegates.
Heathen's API wraps around Steamworks.NET adjusting the design of the interfaces to conform not only to common C# standards but more importantly to Unity's common standards. We have wrapped every Callback with a UnityEvent, we have wrapped every CallResult with an Action, we simplify enumeration to yield .NET collections (typically arrays for sake of performance) and we have wrapped abstract data types such as CSteamID with helpers such as UserData, Clan, etc. to reduce ambiguity and reduce the required steps to access information or perform common operations.
Namespace
Heathen's Steam API is defined in the namespace
using HeathenEngineering.SteamworksIntegration.API;
Each API has a static class related to it and a sub class for Client and Server if both are supported ... for example.
HeathenEngineering.SteamworksIntegration.API.Input.Client;
The above is the full name of the Input API for the game client. you can shorten this name by using namespace aliases as described in this linked article.
using InputAPI = HeathenEngineering.SteamworksIntegration.API.Input.Client;
here is a comparison on how that would shorten your code.
Traditional using
using HeathenEngineering.SteamworksIntegration.API;
//...
//...
if(Input.Client.Initalized)
{
    //DO WORK
}
Alias using
using InputAPI = HeathenEngineering.SteamworksIntegration.API.Input.Client;
//...
//...
if(InputAPI.Initalized)
{
}
Callbacks
On any feature of the Steam API where a SteamCallback handle would have been used aka a CallResult, you will find that we have added an Action<T,bool> callback parameter.
public static void ExampleMethod(int inputData, Action<OutputType, bool> callback)
notice the signature of the action, the typical form with all Steam API call result delegates is that the first parameter is what ever the resulting requests data type is and the second is a boolean. The boolean represents an IO Failure and is pessimistic, consider the following example handler.
Using Expression
ExampleMethod(42, (result, bIOError) =>
{
    if(bIOError)
        Debug.Log("An IO error occured, responce data is unreliable");
    else
        Debug.Log("No IO error, check the result for more info")
});
Classic
ExampleMethod(42, HandleExampleResult);
​
//...
​
private void HandleExampleResult(int result, bool bIOError)
{
    if(bIOError)
        Debug.Log("An IO error occured, responce data is unreliable");
    else
        Debug.Log("No IO error, check the result for more info")
}
Static Classes
Like the native Steam API all of the "interfaces" are static classes and are wrapped up in the API namespace. To insure you do not have any ambiguous calls in your code we recommend that you use the follow Heathen namespace.
using HeathenEngineering.SteamworksIntegration;
And then in your code where you would like to access one of our interfaces you can use its namespace and interface name.
var localUser = API.User.Client.Id;
or
var clans = API.Clans.Client.GetClans();
and similar, the following articles will explain in detail each of the available interfaces and provide examples for use. You can also find samples in the asset package you install from the Unity Package Manager.
Friends
Leaderboards
Last modified 16d ago
Copy link
Outline