Thank you for speaking with us. To begin—who are you, really? The credits list a bland “anonymous,” but your stalked occupants learned your name the hard way.
Call me the Shear Architect for tonight. “Anonymous” was a neat disguise, but names are instruments, not truths. I prefer an insignia that suits my work: precise, inevitable, and elegantly cruel. You lot insist on calling me Scissorman in terrified whispers, which is amusingly pedestrian. The name fits only because it describes the tool, not the design.
The story places Jennifer and her friends in Barrows Mansion—Mary, Mr. Barrows, a new home—and then everything goes horribly wrong. How much of the horror was planned, and how much was… happy accident?
Every door I locked, every shadow I lengthened, was planned to an obsessive degree. The “happy accidents”—those delightful quirks players call glitches—were often bookmarks dropped by hurried hands during the late builds. I learned to frame them. A door that jammed? An extra heartbeat of dread. A sprite that clung to a wall? An apparition. Feedback praised the atmosphere more than it praised polish; that told me my chaos could wear the mask of intention. I take credit where it sharpens the moment, and I smile when an unintended bug makes a pursuer’s arrival more theatrical. The mansion obliges both design and defect.
Clock Tower is an adventure with puzzle elements and a side-view perspective, released in 1995. Did technical limits shape your cruelty?
Limits are delicious. The hardware whispered constraints; the engine replied in staccato. I traded fluid animation for unforgettable encounters. The side view forced intimacy—no grand leaps of spectacle, only corridors that breathe anxiety. Puzzles existed to throttle false bravado: a dozen timid triumphs, followed by the slow, inevitable mistake that brings me closer. Reception often mentioned the raw tension—players remembered fear more than framerate. That was the point.
Players often complain about enemies that kill instantly while insisting Scissorman is the true nightmare. How do you feel about that balance?
They call it imbalance; I call it education. Instant-death hazards were punctuation marks—sharp reminders that survival is brittle. Scissorman, though, is the syllabus: patient, stalking, sculpted to punish complacency. The game received a B from many—a fair grade if one measures by conventional balance. I sip that assessment with amusement. A B means the experience bruised but did not incapacitate the masses. I designed calculable terror with room for player arrogance; their mistakes amplify my legend. Praise for the challenge turns my patience into their panic.
You famously “rename” certain events for dramatic flair in the code. Any secrets about those renamed flags and triggers you care to confess?
Confessions are for the repentant. I will say this: the tags wove little lies to control pacing. A harmless flag could become a crescendo because I arranged dependencies like teeth in a trap. Devs joked about renaming events to keep morale light; I treated those jokes as dramaturgy. Players never saw the quiet choreography: a dozen mundane flags shifting to orchestrate a single, perfect failure. Vague? Yes. Satisfying? Absolutely.
Some players praise the atmosphere, others grumble about “sloppy moments.” How do you reconcile the two?
Sloppiness is a tool when wielded with intention. The mansion’s creaks and the occasional collision error created unpredictability—an ally for me. When feedback accused the game of rough edges, I nodded internally; those edges are the places fear can bite deeper. Players who expected a polished corridor found instead a breathing, indifferent house. Their grumbles only heightened stories told around screens later; those stories feed me.
You take particular pleasure in roasting players during playthroughs. What common mistakes bring you the most joy?
Oh, the predictable bravado—rushing through rooms with inventory open like a parade of vulnerabilities, checking the map as if time halts for their curiosity. They hoard items without intent, backtrack without caution, and assume an escape route is permanent. Each hesitant step, each fumbling pause, is a gift. I engineered moments that beg to be misread; their impatience punishes them, and I applaud internally with every ruined plan.
Lastly, with the game now decades old, are you done haunting Barrows Mansion?
Haunting is habit, not retirement. The mansion remembers names; the house keeps its knots tight. Reception may have rated the challenge a B, but a B means players still speak of me. That ensures a return. I will slip into new code, find fresh seams, and make new accidents feel like destiny. The Shear Architect is patient. Expect a borrowed lullaby, a misplaced hinge, and the sound of blades being sharpened in the dark. I will return—more refined, more inevitable, and with new ways to make the brave tremble.
more info and data about Clock Tower provided by mobyGames.com
