Of course, no two events are exactly alike, but we wanted to highlight these few because they accomplish several important communication goals:[list] [*]The event's theme comes through clearly for customers, even after a quick glance. [*]Customers get a quick sense of kinds of games the Sales Page will include, even before they click the banner. [*]The event's host is clearly presented, or, in the case of Franchise Sales and Publisher Sales, it's implicit. [*]If the event has a livestream component, the asset communicates when it begins. …
The failure reasons are typically out of your control and tend to not be very important. Just keep retrying your API Call until it works. [b]Returns:[/b] [apitype]ISteamUtils::ESteamAPICallFailure[/apitype] [b]See Also:[/b] [api]ISteamUtils::IsAPICallCompleted[/api], [api]ISteamUtils::GetAPICallResult[/api] [b]Example:[/b] [code=cpp]void CHTMLSurface::OnBrowserReady( HTML_BrowserReady_t *pBrowserReady, bool bIOFailure ) { if ( bIOFailure ) { SteamUtils()->GetAPICallFailureReason( handle ); // handle must be stored separately. …