Server

Here's a description of all registered server network events.

requestInit

Is called to initialize the emote creator menu. The server will attempt to create a user if it does not exist, ensuring that the user will exist before any emote generation attempt.

requestQRCode

Is called when the client request an emote generation. The paywall methods are triggered here. The server should trigger qr_code_response or qr_core_error

requestAvailableEmotes

Is called by the client when requesting the user's emote bag. It should call the necessary route and trigger emotes_response with the API response.

requestConfiguration

Is called by the client when requesting the application's configuration (settings). It is used for example to know how many retakes per process are allowed. It should call the necessary route and trigger config with the API response. Since 0.2 it will also send to the client the list of new cached ycds since last resource restart.

requestValidate

Is called by the client when he wants to validate an emote. It will call the function DownloadYCD with refresh and notify.

requestRetake

Is called by the client when he wants to retake an emote. It will trigger retake_process with the API response.

requestEmotePreview

Is called by the client when opening a process in the process list waiting for validation. It will call the GetEmotePreview function and trigger emote_preview with the API response.

deleteEmote

Is called by the client when requesting an emote deletion in the user bag. It will call the DeleteEmote function. After getting the response it will call the GetAvailableEmotes function and trigger both emote_response and reopen_bag to refresh the player's inventory.

renameEmote

Is called by the client when requesting an emote deletion in the user bag. It will call the RenameEmote function. After getting the response it will call the GetAvailableEmotes function and trigger both emote_response and reopen_bag to refresh the player's inventory.