Zync AuthDocumentationDashboard

Writing scripts

Source privacy

Keep your own copy before uploading.

Original source is deleted after successful compilation. The private server vault retains the protected custom instruction program and loader. Explicitly marked native callbacks retain their function bodies as encrypted source constants inside that program.

Failed builds refund obfuscation credits and retain source for retry. Uploads are limited to six per minute, retries to three per minute. Total protection attempts, including retries, are limited to five times your subscription’s obfuscation allowance, with a minimum of 50. Unlimited obfuscation plans have no total credit or protection-attempt cap; upload and retry rate limits still apply. Redeeming more credits increases the cap for finite plans; resetting usage does not. Contact support if repeated failures reach it.

Editing and rebuilding

Upload your own source again to edit a script or rebuild its program. The site cannot return burned source. Loader updates can refresh the public loader without rebuilding the customer program.

Authenticated delivery

The public script URL serves an authentication bootstrap. The interpreter and customer program are delivered together only after authorization, with a fresh execution key and a server signature binding the complete packet to that request. The interpreter is compressed to reduce download and startup work. The signing key stays on the server. Device binding identifies the software runtime; it is not hardware attestation.

Standalone files provide static obfuscation and ship the material needed to execute them. Use authenticated delivery when you need license checks and fresh session programs. An authorized client can inspect either form during execution.

Current Zynx loaders specialize internal runtime selectors per session and use separate function and record key domains. Maximum keeps small instruction windows per invocation and clears them on return or error; Balanced retains larger caches for speed. Explicit LPH_JIT, LPH_JIT_MAX, and LPH_NO_VIRTUALIZE annotations retain their documented execution modes in every preset. Maximum suppresses client startup diagnostics.

Current loaders require client loadstring, getfenv, and setfenv support to prepare the delivered interpreter. The authentication print appears after startup preparation, immediately before customer code starts. Fetch a fresh loader to use this change; re-uploading the original source is not required.

Maximum and Balanced make verified instructions, function metadata, and constant descriptors immutable after decoding. Customer tables, captured variables, and coroutine state remain mutable. Compatibility retains authenticated delivery with fewer client integrity checks. Fetch the latest loader to use runtime improvements; existing protected programs do not need to be re-uploaded for these changes.

Runtime compatibility

Output targets Luau with buffer support; it does not run unchanged in stock Lua. Scalar programs do not require a vector constructor. Programs containing vector constants require vector.create, Vector3.new, or a constructor supplied by the embedding runtime. Maximum and Balanced can reject replaced or wrapped runtime primitives; Compatibility reduces those checks while retaining authenticated delivery.