Twixxel's Stalkers 2.1.0: Bedrock Horror Guide

Minecraft Bedrock · Scripted psychological horror

PnTMC's Twixxel's Stalkers turns observation into the survival mechanic. The Stalker waits at a distance, through windows or between trees, stays still while a player looks directly at it, and moves when attention slips. The premise works only if the exact project is identified and the player actively accepts its sound, pursuit, and surprise-event design.

Lock the project identity before the story

Other creators publish projects with “Twixxel,” “Stalker,” or “Stalkers” in their names. A newer date or similar thumbnail does not make them this project. Creator PnTMC, project 1567781, and file 8406408 are the identity tuple for this page; features and files from another project must not be mixed in.

Exact Bedrock labels

The release card lists twenty builds, descending from 26.30: 26.30, 26.20, 26.13, 26.12, 26.11, 26.10, 26.3, 26.0.02, 26.0, 1.21.132, 1.21.131, 1.21.130, 1.21.124, 1.21.123, 1.21.122, 1.21.121, 1.21.120, 1.21.114, 1.21.101, and 1.21.100. It does not list 26.40 or later.

The filename says “V26+,” but the discrete version list is the safer boundary. A plus sign in a name is not permanent forward compatibility, especially for a project that advertises thousands of script lines and many JSON files.

What the creator says changed

The exact release notes say the update adds more than 20 events, more appearances, and more sounds; improves chase AI; adds a book to the bonus chest; changes some creatures; and adds entity names. The short notes do not enumerate every trigger, probability, creature, audio cue, or migration rule.

Create the test world with the bonus chest enabled and read the supplied book before seeking an encounter. If the book is missing, do not wander randomly for an hour: confirm the correct file and active components first.

The core look-away loop

The project description gives the Stalker an unusual weakness: it cannot move while someone looks directly at it. When the player looks away, it advances. It can appear in forests, caves, ruins, or outside a home after sunset.

A useful baseline uses one well-lit cabin, two windows, a short tree line, and a marked escape route. Record the first appearance, distance, whether direct view stops movement, what counts as breaking attention, and how the chase begins. Repeat after saving and reopening. Do not claim perfect line-of-sight behavior from a single cinematic encounter.

Sensory safety comes before suspense

This project is designed around darkness, unsettling appearances, sounds, and pursuit. It may be a poor fit for children, players sensitive to jump scares, loud or sudden audio, paranoia themes, or sustained chase pressure. Headphones are not a default recommendation.

1. Start with device volume low and Minecraft music reduced or off.
2. Use a short daytime session before testing night, caves, or enclosed spaces.
3. Keep pause/exit controls accessible and agree on a stop signal in multiplayer.
4. Do not test alone if the player is uncertain about the premise.
5. Stop at dizziness, panic, headache, sleep disruption, or persistent discomfort.

The source does not provide content toggles, sound categories, flashing-light controls, or an event blacklist in the checked description. Their availability is unknown.

Import without assuming the internal pack graph

CurseForge presents one .mcaddon and reports no additional files. That does not prove the archive contains only one internal pack or has no script/resource dependency. MineBrush did not inspect its manifests.

1. Match the creator, project ID, file ID, filename, and one of the listed Bedrock builds.
2. Open the creator-sourced .mcaddon with Minecraft and record the import result.
3. Create a fresh world with a bonus chest; do not use the only copy of a survival save.
4. Record each behavior and resource component Minecraft exposes, plus any experiment prompt.
5. Activate only this project's components, restart the game, and verify the guide book.
6. Run one short observation/escape scene, save, restart, and repeat.

A missing book, invisible entity, silent event, or nonmoving chase can identify different broken layers. Do not fix them by importing a resource pack from another similarly named project.

Test events without spoiling the whole project

For editorial verification, you do not need to catalog every surprise. Select four evidence points: one distant appearance, one direct-view stop, one look-away advance, and one chase/escape. Add the bonus-chest book and a complete restart as setup checks.

Record coordinates, time, weather, difficulty, render and simulation distance, active packs, volume settings, and the shortest action before the event. If the trigger is random, record observation duration and failed attempts rather than turning absence into a defect.

Audio, visibility, and accessibility checks

Test speakers and headphones separately only with informed consent. Note whether dialogue, footsteps, ambient cues, and attack sounds remain understandable at a comfortable master volume. Capture peaks or missing cues with device volume and in-game categories recorded.

Darkness is part of the presentation, but an entity that becomes impossible to see for a player with low vision is an accessibility boundary, not extra difficulty. Check brightness, UI scale, subtitles if available, color/contrast, motion sensitivity, and the ability to exit safely. No universal accessibility rating is claimed.

Multiplayer changes the observation mechanic

With two players, one person may be looking while another turns away. The creator page does not explain whether line-of-sight, event state, sound, or chase target is global or per player. Test one host and one joining client in the same marked scene.

Compare what each player sees and hears, who the Stalker follows, what happens at different distances, and whether reconnecting resets or preserves the event. Realms and dedicated servers remain unverified, and a local host result should not be generalized.

Performance needs an event-density test

No benchmark was produced for this package. The project advertises 3,500+ script lines, multiple entities, JSON data, audio, and more than 20 events; those descriptors do not predict cost by themselves.

Measure a calm five-minute baseline and a controlled event/chase route on the weakest intended device. Record frame time, input response, audio delay, entity behavior, memory pressure, heat, and recovery after the event. Test again after a full restart. “No lag in the first minute” is not enough.

Conflicts and removal

Build the conflict ladder in this order: ambient audio, entity and spawn logic, player scripts, animation systems, darkness effects, bonus-chest behavior, then difficulty. Keep the Stalker-only result recorded between additions so the first changed layer stays visible.

Before removal, exit any active chase, move away from custom entities, save a world export, and work only on a copy. Deactivate every imported component, restart, and inspect the test area, sound, entities, book, and logs. Exact event-state cleanup is unknown because the archive was not acquired.

Troubleshooting by earliest evidence

Credits, rights, and media boundary

PnTMC identifies the project as heavily inspired by Twixxel's video series and credits LCrandom for designs plus MrPerkasc, OmarZuriel, SomeoneWithaName, Taquitos, and Gloriouskingavr for sounds, assets, or ideas. Inspiration and credit do not mean those people endorse MineBrush.

The project is All Rights Reserved and explicitly forbids reuploading, redistribution, or public modification without permission; private personal modifications are allowed by the creator's note. MineBrush hosts no archive or gallery media.

The workspace holds neither file 8406408 nor a MineBrush-owned or creator-supplied Stalker capture. The existing cover is editorial art and not a captured event.

Primary sources

• PnTMC's Twixxel's Stalkers project
• Exact file 8406408

Source metadata was rechecked August 24, 2026. This is a source-grounded test guide, not a claim that MineBrush ran the add-on or verified its horror events on a specific device.

Browse more carefully scoped projects in the Minecraft Bedrock add-ons hub.