[RumbleFrog]

Originally Posted by psychonic Since it internally uses a callback instead of a callresult, it's possible that something else is eating the callbacks before the SteamWorks extension can see them, like the SteamTools extension or the game itself.

Any workaround in the case of this?