Publish, select downloads and update
Upload one complete V4 ZIP; recipients choose modules after review.
In questa pagina
V4 is the current protocol. New works may include launch screens alongside app artwork, palettes, reader themes and fonts. Legacy V1/V2/V3 packages remain readable. Import saves a copy; application is explicit. Current manifest · Historical V1.
Upload one complete package
Use V4 for new works, run the creator checker, sign in to the workbench, upload one complete ZIP and confirm artwork/font publication rights. Put promotional images in packaged media.images. Legacy V1 submissions retain their promotional-upload interface. Only approved works become public.
After choosing a ZIP, review the automatically filled theme name, author, version and description. Edit any corrections, then select “Confirm and send for review”. Choosing a file alone does not submit it. The theme ID and protocol version stay fixed. Confirmed details are saved in the download package; publication still requires approval. Names and authors allow 60 characters, descriptions 300 without line breaks, and versions must be positive integers above previous submissions when updating.
V4 permits 128 MiB compressed and 192 MiB expanded, subject to resource-specific budgets. Each static launch image is limited to 2 MiB and 2048 pixels on its longest edge. Legacy packages retain their schemas and are not silently rewritten. Identity, version, paths and licensing must be accurate.
Select modules for download
Details use the shared ten-module catalogue under App appearance, Reading appearance and Fonts. Users can select all, clear, or choose any author-provided module supported by that protocol, then download one standalone ZIP. skin, palette, reader and fonts are four internal storage containers, not the selection granularity; one container can project several independent modules. Comment cards independently carry chapter-discussion (本章说) and god-comment (神评论) styling. Information bar styling independently carries bounded style and content presets and is off by default when applying. Multiple font files in the Fonts module travel together; arbitrary ZIP-file selection is unsupported.
All selected uses the original complete ZIP. A subset is compressed on its first request and cached by source SHA, schema and canonical selection. Users and selection order share the same result. A new source revision creates a new key. Withdrawn works stay unavailable even when cached. Capacity eviction can require a later rebuild.
Versioning and application
The current protocol schemaVersion is 4; the author's version increases independently. Shared catalogue catalogVersion: 3 adds the launch-screen row and does not change the package protocol. Verify the highest submitted version, retain the original archive, identity, attribution and unchanged assets. Never overwrite published bytes or SHA hashes. Download saves a copy; application remains explicit. Older clients request compatible V1/V2/V3 history or require an update.
Common errors
| Problem | Fix |
|---|---|
| Legacy package relabelled as V4 | Restructure components and media, then validate |
| Missing font license | Package redistribution terms or use a system font |
| Missing/corrupt reference | Correct actual path, case and file bytes |
| Unreferenced files or scripts | Remove drafts and OS junk |
| Byte, pixel or frame budget exceeded | Reduce real resource cost; ZIP compression cannot reduce decoded pixels |
| Older client cannot read V4 | Update the App; preserve legacy compatibility |
Temporary sharing is separate from publication: six hours maximum and 32 MiB before/after normalization; imported copies remain usable. Withdrawal stops public access while retaining records. Permanent deletion removes every version and permanently retires the ID.
Copyright and reports
Themes are uploaded and shared for free by users. Uploaders must confirm their rights to use and share the package, fonts and promotional images, and retain required licenses and attribution. The platform reviews infringement reports; publication review does not grant rights to third-party assets. Use Report on a theme’s detail page, sign in, and provide a reason, specific details and optional contact information. Only authorized administrators can access reports for review. Do not include passwords or unrelated personal information. A confirmed issue can result in the entire theme being taken down; downloaded offline copies cannot be recalled.
Hai trovato un problema in questa guida? Suggerisci una correzione