Server library

Server library and player exchange

English | Русский

Updated 31 October 2026. Issued private alpha: 0.19.328. This is not a public beta or a Thunderstore package. Version and limits.

The internal 0.19.329 candidate has passed eight bounded native data checks. Four direct producer-profile checks (.blueprint/.vbuild) have passed independent review. Acceptance of 2.17 covers codec/profile data only in the internal 0.19.329 candidate. Strict player-state endpoints differ; the cause is not established. Inventory, source files and catalogue content hashes were preserved; the ordinary-save comparison covered metadata only. This run does not establish UI, world construction, new visual frames, networking or a cold-process test. The next requirement is 2.18; the 2.16 HOLD is unchanged. The .280 examples and 23 October captures describe their historical version; they do not validate 0.19.328 or the 0.19.329 candidate.

Home · File sharing

Validation boundary: the panel and in-process checks exist; host+remote, live permission refusals, reconnect, and restart are not yet accepted. New offer/receipt foundations in source do not mean direct player transfer is connected. Use Share files for ordinary exchange.

Purpose and starting point

An administrator prepares a library visible to all players or administrators. A connected library is required, and BuildWorks must be present on the server. A personal copy does not grant permission to republish another author's work.

Player: obtain a personal copy through the panel

1. Select Server in the exchange panel, then Refresh.
2. Choose an available entry and inspect its name, category, part count, revision, and publisher.
3. Select Get a personal copy… and wait for verification.
4. Review missing parts and contents, then confirm Save personal copy.
5. Find it in your personal catalogue. This does not start construction, change resources/world objects, or replace an unsaved editor document.

Expected result of the implemented path: a personal document with its own ID and provenance. Delivery/persistence over a real connection remains a separate acceptance check.

Administrator: prepare publication

1. Save and select the local blueprint before opening a server operation.
2. Use Publish selected local or Update selected server. Choose visibility and review the document/revision.
3. Confirm the server operation after review. Cancelling preparation before submission publishes nothing.
4. Refresh after the response. Stopping the wait does not undo an already committed server request: refresh before deciding to retry.

Delete from server requires server permission and confirmation; personal copies and built objects remain. A local role cannot grant server authority. These are existing controls for prepared QA, not a claim that a public server deployment has passed acceptance.

No connection: close the window and check server installation/versions with its administrator. After a timeout or error, refresh before repeating a modifying command.

The peer endpoint in source323 remains CPU-only; runtime/client/UI are not connected. This chapter does not promise working direct player transfer or a recipient interface.