Arcane-Powered/arcane-sdk
Source, releases, the Unity package and the web package. Licensed under MIT or Apache 2.0, at your option.
Pick your path
Rust
Cargo.toml
Unity
InPackages/manifest.json:
Native engines (C ABI)
Each GitHub release carries the header,arcane_sdk.h. Build the library from the repository for the platforms you ship:
target/release/ then holds the shared library (arcane_sdk.dll, libarcane_sdk.dylib or libarcane_sdk.so) and a static one.
Web (HTML5)
The package is not on npm yet. Build it from the repository and importdist/index.js from your game:
What you need from the publisher portal
The SDK needs one value from the portal: your title’s game id. Open the title in the publisher portal, and find it on the Overview tab, in the SDK card, next toARCANE_GAME_ID. If the title has none yet, click Create game id. The id is final: it does not change when the game goes live.
A shipped game never passes that id itself. The desktop app sets ARCANE_GAME_ID when it launches the game. You set it by hand only to run your build outside the app — see Local development.
The same card creates playtest accounts: accounts that own the title, so a tester can install and play it before release.
Versions and releases
The SDK follows semantic versioning. Every release is taggedvX.Y.Z, published to crates.io and listed on the releases page. While the version starts with 0., a minor version bump can carry a breaking change, so read the release notes before you update.
Found a bug or missing something? Open an issue on the repository. See Contributing to send a change.