> For the complete documentation index, see [llms.txt](https://docs.sefiraat.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sefiraat.dev/crystamae-historia/tools/block-veil.md). # Block Veil A Block Veil (also call a Cover) is a magical tool that envelops a selected block in a thin film of magic that resonates with the energy of another block. This simple device will allow you to hide more mundane things within your base. To apply a cover, simply hold it in your main hand while holding the block you wish to imitate in your off-hand. Assuming the block in the off-hand is valid (solid, breakable and a full occluding block) then the cover will weave itself over the existing block. Breaking a covered block will return the original block without the cover. Covers are consumed on use and cannot be taken off other than breaking the original block. ### Cargo The **Block Veil - Cargo** allows you to cover Cargo Connector Nodes only. ### Energy Net The **Block Veil - Energy Net** allows you to cover Energy Net Connectors only. ### [Networks](https://github.com/Sefiraat/ScribbledNotes/blob/main/crystamae-historia/tools/broken-reference/README.md) The **Block Veil - Networks** allows you to cover [Network Bridges](/networks/network-nodes/network-bridge.md) and [Network Monitors](/networks/network-nodes/network-monitor.md) by default and there is a Slimefun ItemSetting for the veil to allow players to cover every Networks block. This is disabled by default as this can make it difficult for admins/owners to triage potential problems with a players setup. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sefiraat.dev/crystamae-historia/tools/block-veil.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.