FakeBlock
Official compatibility
| Element | Reference |
|---|---|
TypeWriter | Required. Use the official TypeWriter release supported by the extension release. |
| Related extensions | Install the related extensions listed on this page before using entries that depend on them. |
The FakeBlock Extension enables the creation of complex, virtual structures that only selected players can see. Using packet-based rendering, it delivers high-performance visual world-building without modifying the actual server world.
Features
- Client-Side Rendering — Zero server impact, instant updates.
- Schematic Support — Native
.schemfile loading and displaying. - Audience Control — Show blocks only to specific players.
- Interaction — Trigger events on "fake" block break/interact.
- Schematic Support — Native
Entries
- Actions — Schematic Block: Display a schematic.
- Audience — Schematic Audience: Regional visibility. Item Audience: Visibility by held item.
- Cinematics — Schematic Cinematic: Animated block sequences.
- Artifacts — Schematic State: Persistent block states.
User guide
- 1. Create Storage — Add artifact entries to persist data: schematic_state_artifact. → schematic_state_artifact
- 2. Trigger Actions — Use action entries to interact with the extension: schematic_block. Trigger them from commands, NPCs, events, or other entries. → schematic_block
Commands
All commands are under /fakeblock.
| Command | Description |
|---|---|
/fakeblock list | Lists active fake block IDs |
/fakeblock count [player] | Shows tracked block count |
/fakeblock reset <player> [id] | Clears fake blocks |
Permissions
| Permission | Description |
|---|---|
typewriter.fakeblock.admin | Administrate fake block displays. |
Troubleshooting
The extension is not visible
Check that the installed release matches the supported TypeWriter release and that the related extensions listed in the compatibility section are present.
An entry is missing
In the Typewriter Web panel, use the Search bar or the + button to find or create the entry with its exact identifier. Entry IDs and field names are case-sensitive; do not translate them.
The entry saves but nothing happens
Check that the entry is connected to the trigger, command, objective, event, or menu interaction required by its type. Test with optional permissions and criteria removed, then add them back one at a time.
An integration does not work
Verify the dependency and version shown in the extension card, then check the server log for the first error. Do not replace a missing dependency with a similarly named plugin unless the extension source explicitly supports it.