Resource Update Checks

Publish the latest version of each resource you sell so installed copies can check for updates.

A product can publish the latest version of the resource it sells. Installed copies of the resource request a URL on your store and compare the answer with their own version. When you release an update, change the version in the editor and every server that checks sees it.

Requirements

Set up a product

1. Open your project in the editor and select the Product Detail page.
2. Select the product in the toolbar.
3. In the Properties panel, find Resource Updates under 5Metrics Usage.
4. Enter the Resource Name. The placeholder shows the product's Tebex slug. Use the name your resource will request.
5. Enter the Latest Version in the same format your resource uses, for example v1.2.0.
6. Save your changes, then publish the store if it is not live yet.

The Update URL field shows the address to put in your resource. It uses your verified custom domain when your plan includes custom domains, and your .taintless.store subdomain otherwise.

Name and version rules

Names are not case-sensitive in the URL: /api/versions/My-Resource and /api/versions/my-resource return the same version.

How the URL responds

The 200 body is plain text: no quotes, no JSON, and no trailing newline. Treat any other status as "no update information" and skip the check quietly.

Responses are cached. A saved version, or unpublishing the store, can take up to about 6 minutes to reach every server. A 404 can be cached for up to a minute. Errors are never cached.

Check for updates from a FiveM resource

This server-side example runs when the resource starts. It reads the installed version from fxmanifest.lua (for example version 'v1.2.0') and prints a notice when the store publishes a different one.

local UPDATE_URL = 'https://yourstore.taintless.store/api/versions/my-resource'

local resourceName = GetCurrentResourceName()
local installedVersion = GetResourceMetadata(resourceName, 'version', 0) or 'unknown'

PerformHttpRequest(UPDATE_URL, function(status, body)
  if status ~= 200 or not body then
    return -- Store unreachable or no version published: skip the check.
  end

  if body ~= installedVersion then
    print(('[%s] Version %s is available. Installed: %s'):format(resourceName, body, installedVersion))
  end
end, 'GET')

• Hardcode the URL instead of building it from the resource folder name. Server owners can rename the folder.
• Use one version format in both places. If fxmanifest.lua says 1.2.0 and the store says v1.2.0, the check reports an update that does not exist.
• Check once at start-up or on a timer of several minutes. Very frequent checks from one IP address can receive 429.

Troubleshooting