Execute HOUSE 13 Scripts

Executing a Roblox script always means the same three objects: a running HOUSE 13 session, an executor that can attach to that session, and a Lua paste. HOUSE 13 does not currently have a verified paste, so this page is a dry run. Use it with the scripts hub and script safety. If you only wanted lights and a clean Easy clear, go back to the beginner guide instead.

What an executor is

An executor is third-party software that injects Lua into the Roblox client. It is not a Roblox setting. It is not the Codes box. It is not a Dread Forge feature. Using one can violate Roblox rules and cost the account. If you still proceed, use an alt you can afford to lose. Do not inject on the account that holds limiteds, gift cards, or the friends you co-op with.

Executors come and go after every Roblox client patch. A name that worked in August can be dead in September. This wiki will not rank injectors or link downloads. If your tool cannot attach, the script is irrelevant.

The attach order

1. Start Roblox and join HOUSE 13 on an alt.
2. Wait until you can walk and see the door HUD. Injecting during teleport can miss the data model.
3. Open the executor and attach / inject when the client is stable.
4. Paste one script. Do not stack three hubs.
5. Execute once. Wait five seconds. If nothing appears, do not spam Execute.
6. If a key system opens, close HOUSE 13. A key page in a “no key” script is a bait chain.

Never paste a script into Roblox chat. Chat does not run Lua. Never paste into a browser console on roblox.com. The executor editor is the only place a loadstring belongs.

HOUSE 13-specific timing

The house is busy. A GUI that opens over Let In / Close Door can make you accept an Impostor by misclick. Execute in the lobby or during a quiet Easy night, then learn the menu before Medium. If your GUI covers windows, you will miss The Reacher. If it dims the world incorrectly, you may think you have light when The Hitcher still counts darkness.

Fullbright scripts fight the lighting mechanic. Even if one appears, it can desync other players’ night state in a 32-player server and flag you. Auto-verify scripts will be wrong often: HOUSE 13 visitors copy clothes and voices on purpose. A false green is a lost house.

When execution “works” but the game is unplayable

• Noclip through the door skips the check and often teleports you outside the playable hull.
• Speed hacks make closet clears sloppy, which feeds The Nester.
• ESP that highlights every dummy as hostile trains you to Close Door on real survivors, which can fail a help objective depending on how the night is scored.
• Multiple scripts fighting the same highlight instance crash the client mid-knock.

If the client hitchs after Execute, leave. Rejoin without the script. Then play a clean night with the verification checklist. That tells you whether the hitch was the injector or a HOUSE 13 patch. After a Roblox update, assume every executor is broken until its own community says otherwise.

Mobile notes

Mobile executors are their own ecosystem and go stale faster. A phone paste that claims HOUSE 13 support in the first week of a game is almost always a renamed universal hub. Keyboard overlay plus a GUI plus the door buttons is a misclick factory. PC is the only setup where you can even see what you injected.

Aftercare

Close the executor when you are done. Change your Roblox password if the paste asked you to log in anywhere. Do not keep the same cookie logged into a random GUI. Then go read identify Impostors so the next night does not depend on a highlight color.

Official progress still lives in nights survived, not in a floating window. The updates hub will note when the client patches. The codes hub stays separate. If a real HOUSE 13 script is ever verified, the scripts hub will describe its buttons without pretending it is part of Dread Forge.