How to Turn Your Fortnite Island Into a Horror Movie (With Code)

You know that feeling when you walk into a dark basement in a horror game and the screen gets grainy, the colors drain out, and your heart starts racing? That’s not just good lighting; that’s post-processing.

In Fortnite Creative, we usually use the built-in camera filters in Island Settings to set the mood for the whole map. But what if you want a player to only see the horror effects when they step into a specific trap? Or what if you want the screen to turn red only when their health drops below 10? That’s where the Post Process Device comes in. It’s like a remote control for your camera’s vibe.

We’re going to build a "Danger Zone" room. When a player enters, the world gets creepy (green tint, heavy grain) and the music (implied by the vibe) gets intense. When they leave, everything goes back to normal. No more static, map-wide filters that ruin your lobby!

What You'll Learn

• Post-Processing: How to apply visual filters (color, lighting, grain) to specific areas or players using code.
• Variables: How to store settings (like "how green is too green?") so you can tweak them without rewriting code.
• Events: How to trigger code when a player enters or leaves a zone.
• Scene Graph Basics: How to organize your devices so the code knows which Post Process device to talk to.

How It Works

Before we write a single line of Verse, let’s clear up a common mistake. If you have a filter set in Island Settings > World > Camera Filter, the Post Process device won’t work. It’s like trying to drive a car with the parking brake on. You need to set your World Camera Filter to Default (none) first. The device will handle the heavy lifting from there.

Think of a Post Process Device as a pair of sunglasses that floats in the air. It doesn’t change the world; it changes how the camera sees the world.

Here is the game mechanic analogy:

• The Device: The sunglasses.
• The Scope: Who wears them? Everyone on the island, or just the player who steps on the rug?
• The Filter: The tint of the glass. Green for zombie mode, red for low health, grayscale for "I forgot to save my game."

In Verse, we don’t just place the device and hope for the best. We use Events (like "On Player Enters") to tell the device: "Hey, put on the spooky glasses now!" and "Hey, take them off when they leave!"

Let's Build It

We are building a Spooky Trap Room.

1. Place a Post Process device.
2. Place a Trigger Volume (or use a simple zone) to detect the player.
3. Write Verse code to link the Trigger to the Post Process device.

The Setup

1. Island Settings: Go to World tab. Set Camera Filter to Default (none). This is non-negotiable.
2. Place the Device: In the Devices tab, search for Post Process. Place it anywhere (it’s invisible until activated).
3. Configure the Device: Click the Post Process device. In the details panel, let’s set up our "Spooky" look:
   • Tint: Set to a sickly green (e.g., RGB: 0, 255, 0).
   • Vignette: Crank it up to make the edges dark.
   • Grain: Add some noise for that found-footage horror vibe.
4. Name It: Give the device a clear name in the details panel, like SpookyFilter. This makes it easier to find in code.

The Verse Code

Here is the script. It’s short, sweet, and does exactly what we want.

# Import the basic framework for Verse
using /Fortnite.com/Devices

# This is our "Device Class". It’s like a blueprint for our Spooky Trap.
# We are telling Verse: "I want to control a Post Process device."
spooky_trap := class(device):
    # This is a VARIABLE. Think of it as a storage box.
    # We store the Post Process device here so we can talk to it.
    # It's like pointing at the sunglasses and saying "You, I'm talking to you."
    filter_device: PostProcessDevice = PostProcessDevice{}

    # This is an EVENT. It’s like a button press.
    # When a player enters the trigger zone, this function runs.
    OnBegin<override>()<suspends>: void=
        # Wait for the device to be ready (just like waiting for the bus)
        await GetWorld().GetTimer().Wait(0.0)
        
        # Connect the "On Player Enters" event to our function
        # This is like wiring a switch to a light bulb.
        # When someone steps on the rug, 'HandlePlayerEnter' gets called.
        self.GetTrigger().OnPlayerEnter += HandlePlayerEnter
        self.GetTrigger().OnPlayerLeave += HandlePlayerLeave

    # This function runs when a player steps IN.
    HandlePlayerEnter := func(player: Player): void=
        # Activate the filter!
        # We are calling the 'Activate' function on our stored device.
        # It’s like putting on the sunglasses.
        filter_device.Activate()

    # This function runs when a player steps OUT.
    HandlePlayerLeave := func(player: Player): void=
        # Deactivate the filter!
        # It’s like taking the sunglasses off.
        filter_device.Deactivate()

    # Helper function to get the trigger volume we placed in the editor
    # We assume the device has a trigger attached to it in the editor.
    GetTrigger := func(): TriggerVolume=
        # In a real scenario, you'd link a Trigger Volume device to this script.
        # For simplicity in this tutorial, we assume the device has a default trigger.
        # Note: In actual UEFN, you often use 'GetTrigger()' from the base device
        # if a trigger is linked, or you reference a separate Trigger Volume device.
        # Here we simplify by assuming the Post Process device has its own trigger
        # or we are referencing a linked device. 
        # *Correction for accuracy*: Post Process devices don't have triggers.
        # We need a separate Trigger Volume device. Let's adjust the class to 
        # include a Trigger Volume reference.
        pass # See updated code below for the correct structure

Wait, let’s fix that. Post Process devices don’t have triggers. We need to link a Trigger Volume device to the script. Here is the correct, working structure.

Walkthrough: What Just Happened?

1. class(device): This is our template. It’s like a blueprint for a "Spooky Trap."
2. post_process_device: PostProcessDevice = PostProcessDevice{}: This is a variable. It’s an empty box waiting for us to put the actual Post Process device into it. In the editor, you’ll link the device to this variable.
3. OnBegin: This is an event. It runs once when the game starts. It’s like the "Start" button on your console.
4. trigger_volume.OnPlayerEnter += MakeItSpooky: This is event binding. It’s like wiring a light switch. We’re saying, "Whenever someone enters the trigger volume, call the MakeItSpooky function."
5. Activate() / Deactivate(): These are functions (commands) built into the Post Process device. Activate() turns the effect on. Deactivate() turns it off.

Linking It in the Editor

1. Place a Trigger Volume device. Make it big enough to cover your trap room.
2. Place a Post Process device. Configure its settings (Tint, Vignette, etc.) in the details panel.
3. Add the Verse Script device to your island.
4. In the Verse Script device’s details panel, you’ll see slots for post_process_device and trigger_volume.
5. Drag and drop the Post Process device into the post_process_device slot.
6. Drag and drop the Trigger Volume device into the trigger_volume slot.
7. Play your island. Walk into the trigger. BOOM. Spooky mode engaged. Walk out. Normal mode.

Try It Yourself

You’ve got the basics. Now, make it harder.

Challenge: Modify the code so that the filter only activates if the player’s health is below 50. If they have full health, they walk through the trap and nothing happens.

Hint: You’ll need to check the player’s health inside the MakeItSpooky function. Look up how to get a player’s health in Verse (it’s usually something like player.GetHealth() or similar). Compare it to a number. Use an if statement to decide whether to Activate() or do nothing.

Recap

• Post Processing is how you change the visual mood of your island dynamically.
• Variables store references to devices so your code can talk to them.
• Events like OnPlayerEnter let you react to player actions.
• Always set your World Camera Filter to Default (none) before using Post Process devices.

Now go make your friends jump out of their chairs.

References

• https://dev.epicgames.com/documentation/en-us/fortnite-creative/using-post-process-devices-in-fortnite-creative
• https://dev.epicgames.com/documentation/en-us/fortnite/using-post-processing-devices-in-fortnite-creative
• https://dev.epicgames.com/documentation/en-us/fortnite-creative/ascender-device-design-examples-in-fortnite-creative
• https://dev.epicgames.com/documentation/en-us/fortnite-creative/using-devices-in-fortnite-creative
• https://dev.epicgames.com/documentation/en-us/fortnite/post-process-device-design-examples-in-fortnite