Steam Callback Pump Scaffold Generator
Minimal MonoBehaviour scaffold so invites, stats, and inventory results actually dispatch.
How it works
After the pump runs, review C# for short-lived delegates and disposed objects holding Steam callbacks — common sources of “sometimes it fires, sometimes it doesn’t.”
RunCallbacks must run frequently on the thread expected by your wrapper. This emits a minimal Unity pump; adapt for dedicated server splits.
using Steamworks;
using UnityEngine;
public sealed class SteamCallbackPump : MonoBehaviour
{
void Update()
{
SteamAPI.RunCallbacks();
}
}FAQ
- Nothing happens after Steam API calls?
- Callbacks may not be pumped. Ensure RunCallbacks runs on the correct thread at a steady cadence.
Related tools
-
RestartAppIfNecessary Bootstrap Generator
Wrapper-aware bootstrap order, C# starter snippets, dual-store notes, and QA relaunch checklist.
-
Rich Presence Publish & Cache Checklist
Partner publish vs client cache vs branches — rollout and QA handoff for ‘code works but Steam doesn’t show it’.
-
Steam Inventory Schema Draft Builder
Categories, tradability, bundles/consumables — draft itemdef-oriented JSON + policy warnings.
-
Workshop Upload Error Explainer
InvalidParam and common codes — ranked causes, path checks, legal/preview metadata checklist.
-
Steam Relay vs Unity Relay Decision Helper
Storefronts, concurrency, cross-store, cost — scored recommendation and phased migration.
-
Steam Capsule Validator
Generate Steamworks-sized PNGs from one master image, ZIP export, safe-area inspector, and policy reminders.