Skip to content

Connection Endpoints & Settings

To prevent automated AI scraping and unauthorized distribution, the specific custom connection endpoints, server hostnames, and binary offset hash values are not published in this public documentation.

If you are a member of our community and need these values to configure your client (such as server hostnames or custom script offsets), please ask within the official user community channels.

To successfully connect your client to a custom Sparkle server, you will need to obtain and configure the following three key components:

Required Configuration Table

Component Description Format / Example
API Endpoint The primary domain or URL for handling game logic, API requests, and player authentication. Hostname or full URL path.
Original baseline: krr-prd.star-api.com
Example: https://custom-api-server.com/api/
Asset Endpoint The server address where game asset files (graphics, audio, bundles) are hosted and served. Hostname or full URL path.
Original baseline: asset-krr-prd.star-api.com
Example: https://custom-asset-server.com/[bundleHash]/
Asset Version (Bundle Hash) The unique MD5 hash identifier representing the target asset bundle version. A 32-character hexadecimal MD5 hash.
Example (Last official version): 321d1767653ccfd106384a7aeac5be75
Example (Previous version): 8a3c0aa387299a8f1136e248067c0e7b

When setting up your connection method (whether via Host redirect, PyDroid3 script, or custom client launcher), ensure you have these values ready!