SPRITEFORGE / DOCUMENTATION

Asset delivery

A short control request and an image download have different needs.

Choose the right path

Traffic	Use
Small JSON responses	Read a manifest or check that the docs endpoint responds.
Texture / archive downloads	Fetch the complete asset, verify its digest, and reuse the cached revision.
Local WebSocket	Keep an editor-to-engine session alive while sending incremental updates.

HTTPS transport

This site serves the same guides and assets over HTTP/2 and HTTP/3. HTTP/3 uses QUIC over UDP 443; browsers can use TCP when UDP is unavailable. The certificate names docs.spriteforge.online on both transports.

Download checks

curl -fLO https://docs.spriteforge.online/downloads/fireball-frames.zip
shasum -a 256 fireball-frames.zip

Compare the digest with the manifest. ZIP and PNG responses support range requests, so a client can resume a partial transfer.

Cache behavior

Documentation is revalidated after a short cache window. Samples can be cached longer; the manifest carries content digests so tooling can identify changes. The connection-check response is not cached.