FPK Documentation

Every panel in the First Person Kit add-on, what it does, and the features it brings. Search to jump straight to what you need.

Ask a question

Stuck on something? Ask on the questions page and Riley will answer.

Getting started

What FPK is and how to get your first project running.

Overview

First Person Kit (FPK) is a Blender add-on for building first person games. You author everything inside Blender, and a complete Godot 4.6+ project rides along inside the add-on. Tag your meshes, set a few options, and the kit wires up doors, items, radios, light switches, look cameras, level transitions, menus, save and load, and inventory for you.

The add-on lives in three places in Blender. Each one handles a different slice of your game.

The N panel3D Viewport sidebar: Global settings for the whole game and per-level settings. Create projects and levels, tune the player, set up menus, preview lighting, and publish. Press N in the viewport and pick the FPK tab.
Object Propertiesper object: Object-specific behaviour. Select a mesh, open the Object Properties tab, and you get the FPK Object Tools panel for roles, triggers, and Godot import hints.
Object Data Propertieslights: For lights, FPK adds a Light Settings panel here so your real-time Godot lighting matches the Blender preview.

NoteFPK keeps Blender synced with your game folder automatically. As you add levels, change settings, or save your .blend, it writes the right files into the project so everything just runs when you publish.

Install and first project

1Download the add-on .zip and install it in Blender from Edit, Preferences, Add-ons, Install from Disk. Install the zip itself. The Godot project template lives inside it.
2Open the FPK tab in the 3D viewport sidebar (press N). In the FPK Project panel, hit New FPK Project to scaffold a ready to run Godot project into a folder you pick.
3Set your Godot executable path in the add-on preferences so you can Play test and publish straight from Blender.
4Create a level, then press Play to drop into a playable starter level with menus, save and load, and inventory already wired up.

Heads upOpen in Godot, Play, and Publish need a Godot executable path set in the add-on preferences. Without it you can still author and create projects, but you cannot launch or build from Blender.

The N panel

Global and per-level settings in the 3D viewport sidebar.

FPK Project

The top of the FPK tab. It shows which project is active, keeps you in sync, and gives you one-click Play testing. This is your home base.

Active project: The folder name and full path of the project you are working on, with a checkmark when the folder holds a valid project.godot.
Open Folder: Opens the project folder in your file browser.
Change: Point the add-on at a different existing FPK project folder, or set your Godot executable path.
Sync status: Tells you whether everything is synced and ready to Play. A filling ring shows while a save is importing. If config-only edits (like footsteps or music) are pending, you get a Sync All Changes button to push them.
Open in Godot: Launches the Godot editor on this project.
Play: Runs the game from the main level. Available once a level exists and no import is mid-flight. If your .blend is unsaved, save first so the latest geometry syncs.
New FPK Project: Scaffolds a brand new project from the bundled template. See the next section.

NoteSaving your .blend is what kicks off a geometry sync. If you see Unsaved changes, a save is recommended before you Play so the test runs the latest version.

New FPK Project

Creates a full Godot project from the template that ships inside the add-on. You get the player, menus, save system, inventory, and all the runtime scripts, ready to open in Godot.

Project Name: The name of your game and the folder it lands in.
Location: Where the project folder gets created on disk.
Make this the add-on's active project: Switches the add-on to the new project right away so the rest of the FPK tab targets it.
Open the project folder when done: Pops the new folder open in your file browser after it builds.

Heads upIf the target folder already exists and is not empty, the dialog warns you and will not overwrite it. Pick a fresh name or location.

Level Settings: Create Level

Create Level dialog with Level Name and three checkboxes.

A level in FPK is a folder under levels/<Name>/ plus a thin Godot wrapper scene that loads your geometry. Create Level sets that structure up for you so the .blend you are working in becomes a real, playable level.

Level Name: The level's name. Creates levels/<Name>/, and a level_load value of "<Name>" will resolve to it.
Save this .blend into the level folder: Saves your current .blend inside the new level folder so it becomes the source geometry for that level.
Create Godot wrapper scene (.tscn): Builds the .tscn that Godot loads for this level. Usually leave this on.
Set as game's main level (New Game starts here): Marks this level as where New Game begins. Keep it ticked for your first level so the game has something to Play.

Level Settings: Current Level

Current Level panel with Level Card, Card Sound, and Background Music sections.

Once your .blend lives inside a levels/<Name>/ folder, this panel shows the level's name and its per-level presentation: an intro card and background music.

Play card when entering level: Toggles a title card that shows when the player enters this level. Great for chapter titles and location names.
Title, Subtitle, Duration: The text shown on the card and how long it stays up. Edit Text & Duration opens a small editor. The title falls back to the level name if you leave it blank.
Card Sound: A sting that plays with the card. Use the built-in global sting, browse for your own file (copied into audio/sounds/), or clear it.
Background Music: A per-level playlist with a Volume slider. Add Music to drop in tracks. With no tracks the level is silent.

NoteIf this panel says to save the .blend first, or that it is not inside levels/<Name>/, run Create Level to put it in the right place.

Level Settings: Prep for Godot

A set of cleanup helpers that get a .blend ready for a clean Godot import. Prep Textures for Godot runs the recommended steps in one go. You can also run each step on its own.

Prep Textures for Godot: The one-button option. Tidies textures and data so they import cleanly. Save the .blend first.
Purge: Removes unused data blocks from the .blend.
Pack / Unpack: Packs resources into the .blend or unpacks them back out to disk.
Clean Unused Textures: Drops textures that are not referenced by any material.

World Environment

Per-level environment settings. These are saved to the level's environment.json and rebuilt as a Godot WorldEnvironment when the level loads. Apply to Preview pushes the same values onto the Blender world so the viewport matches what Godot will render.

Background: The flat sky / background color, plus a Background Energy brightness multiplier.
Ambient: A constant ambient light color and its Ambient Energy intensity, so nothing sits in pure black.
Distance Fog: Cheap depth and height fog. When enabled you get color, density per metre, a start height, height falloff, and how much it tints the sky.
Volumetric Fog: Light-scattering fog with density, albedo, emission, anisotropy, length, ambient inject, and sky affect. Needs the Forward+ renderer, which the project targets.
Apply to Preview / Reset: Apply to Preview matches the Blender world to these values. The trash icon resets the level back to FPK defaults by deleting environment.json.

Lighting Preview

Opens a view-only Godot window that mirrors this level's real lighting, live, while you work in Blender. It is the fastest way to see how your lights and environment will actually look in-game without leaving your scene.

Open Lighting Preview: Launches the preview window. Needs your Godot path set in preferences. The view and lights update as you make changes.
Force Reload: Reloads the preview if it gets out of sync with your scene.

NoteWhen the preview is open it tracks your edits live, and auto-syncs geometry as needed so the lighting you see matches the level.

Game Settings

Global settings for the whole game: how the player moves, what footsteps sound like, your menu branding, the game icon, and menu music. These are written into the project so they apply everywhere.

Player Settings: Walk, sprint, and crouch speed, jump force, player height, mouse and gamepad sensitivity, and footstep volume. Written to game_config.json and applied over the defaults at game start. Restore Defaults drops your overrides.
Footstep Sounds: Pick a footstep set from the built-in surface folders (concrete, wood, grass, tile, metal, carpet) or the global default. Open Footsteps Folder lets you drop in your own.
Main Menu: Set Game Logo for the title screen image and Menu Accent Color for the menu's highlight color (shown as a hex value).
Game Icon: The window, taskbar, and .exe icon, separate from the logo. A square PNG between 64 and 1024 px, 256x256 is ideal. Reset to Default restores the kit icon.
Menu Music: A global playlist for the main menu with a Volume slider. Add Music to add tracks. No tracks means a silent menu.

NotePlayer settings apply at game start. Restart a running game to see changes. Some edits here are config-only, so use Sync All Changes in the FPK Project panel to push them into the build.

Publish

Builds your finished game straight from Blender. Set the build details, pick how you want to distribute it, choose your platforms, and hit Publish Game.

Build Details: Game Name, Version, and Author / Company, plus the Output Folder the build lands in.
Distribution profile: How the build is packaged. Three options, below.

Profile	What you get
Itch.io / Direct Download (.zip)	One self-contained file with everything baked in, wrapped in a versioned .zip. Upload to itch.io or link it for download.
Steam (SteamPipe content folder)	A clean folder with the game and .pck side by side, no archive. Point your Steam depot at this folder and Steam does the patching.
Portable single file	Just one self-contained file with everything embedded. The quickest thing to send a tester.

Platforms: Windows and Linux checkboxes. Pick at least one. macOS needs signing on a Mac and is not built here.
Build: Release / Debug: Release is for shipping. Debug builds are for testing only.
Publish Game: Runs the export. Enabled once you have a main level and at least one platform selected.

Heads upPublishing requires Godot export templates installed (Godot, Editor, Manage Export Templates) and your Godot executable path set in preferences.

Object Properties

The FPK Object Tools panel and Godot import hints.

FPK Object Tools

Select any object and open the Object Properties tab to find this panel. It is where you turn a plain mesh into a gameplay object. Pick a Role and the add-on writes the right custom properties for you, then shows only the settings that role needs.

Role: What this object becomes in-game. Picking a role sets object_type and reveals that role's properties. See the Roles section for each one in detail.
Role Properties: The settings box that appears under the role, for example a door's open angle and lock, or a radio's sound. Only the relevant fields show.
Clear All FPK Properties: Strips every FPK tag off the object so it imports as plain geometry again.

NoteRoles set the object's behaviour. Triggers and Godot Import Suffixes are separate capabilities you can stack on top, each covered in its own section.

Godot Import Suffix

Renames an object with a suffix so Godot builds collision or occluders for it on import. This is for static level geometry like walls, floors, and stairs. FPK roles add their own colliders, so you do not need a suffix on tagged gameplay objects.

Suffix	What it builds
Collision (-col)	Keeps the visible mesh and adds solid collision from its exact triangles. Accurate but heavier. The standard choice for static geometry the player bumps into.
Collision Only (-colonly)	Same triangle collision as -col, but deletes the visible mesh on import. Use it when you modelled a separate, simpler collision shape.
Convex Collision (-convcol)	Keeps the visible mesh and adds a cheaper convex hull. Best for small or moving props. Not for hollow rooms.
Convex Collision Only (-convcolonly)	Same convex collision, but deletes the visible mesh. For invisible convex collision volumes.
Occluder (-occ)	Keeps the visible mesh and adds an occluder so Godot can skip drawing things hidden behind it. Put it on big solid blockers.
Occluder Only (-occonly)	Turns the mesh into an occluder only and deletes the visible mesh. A cheap stand-in used purely for occlusion culling.
Don't Import (-noimp)	Godot ignores this object completely. Handy for blockout, reference, or guide meshes.

Footstep Surface: Once a collision suffix is on, a collidable surface can override the player's footstep sound. Pick a set (concrete, wood, grass, and so on) and it plays when the player walks on it, or leave it on the global default.

NoteThe panel shows the object's current Name so you can see the suffix the add-on applied.

Roles

Pick a role to turn a plain mesh into a gameplay object.

How roles work

A role is what an object becomes in-game. Open the FPK Object Tools panel, pick a role from the dropdown, and the add-on writes the right custom properties and shows only the settings that role needs. An object has one role at a time. Clear All FPK Properties resets it to plain geometry.

Every role below has its own properties. Anything left at default can stay unticked. The detailed sections that follow cover each role's variables and when to reach for it.

Role	In one line
Physics	A pick-up-and-throw rigid body.
Inspect	Hold an object up to study it, then put it back.
Radio	A toggleable looping sound source.
Door	A hinged door, optionally locked behind a key.
Item	A collectible that goes into the inventory.
Audio Log	A voice recording with subtitles, replayable from the inventory.
Animated	Loops a Blender action forever.
Player Start	Where the player spawns into the level.
Look Camera	Blend the view into a fixed camera, like sitting at a desk.
Light Channel	Tag lights so a trigger's Light action can switch them.
Level Transition Area	A walk-in volume that loads another level.

Physics

Turns the mesh into a RigidBody3D at runtime. It falls under gravity, gets pushed around, and the player can pick it up with interact and throw it.

Weight (kg)default 1.0: Mass of the object. Heavier objects are harder to shove and land with more force. Lighter ones skitter and fly.

NoteUse case: clutter and props you want the player to handle. Barrels, boxes, cans, debris, or anything for a physics puzzle or just tactile world detail.

Inspect

On interact the player lifts the object up to study it close, rotates it freely, then puts it back exactly where it was. The object stays in place the rest of the time.

Interact Textdefault Inspect: The verb shown in the crosshair prompt when the player looks at it.

NoteUse case: story props the player should read or examine. Notes, photographs, a key with engraving, a clue, a labelled object.

Radio

A toggleable source of looping positional audio. It plays on and off SFX as you flip it, and has an emissive glow that dims when it is off. The sound is 3D, so it gets louder as you approach.

Sound: The track to loop. Browse to pick any .ogg, .wav, or .mp3 and it is copied into audio/sounds/ for you, or type the name of one already there (the extension is optional).
Start On: Whether the radio is already playing when the level loads.
Interact Textdefault Listen: The crosshair verb shown when the player looks at it.

NoteUse case: diegetic music and world building. A radio in the corner, a humming machine, a TV, a record player, any in-world sound the player can switch.

Door

A hinged door that swings away from the player. Set the pivot at the hinge edge in Blender (move the object origin to the hinge). It can be a plain door, or locked behind an inventory key.

Open Angledegrees, default 90: How far the door swings open.
Open Speeddefault 3.0: Animation speed multiplier for the swing.
Open Sound / Close Sound: Optional SFX for opening and closing, by filename from audio/doors/.
Locked: Whether the door starts locked. Turning this on reveals the key and lock-sound fields below.
Item IDLocked only: The inventory item the player must be carrying to unlock this door. The key is kept, not consumed. Match this to an Item's Item ID to make that item the key.
Locked Sound / Unlock SoundLocked only: SFX for rattling a still-locked door and for the moment it unlocks.
Interact Text: Optional override for the crosshair verb.

NoteUse case: doors, gates, hatches, and lockers. Pair a locked door with an Item somewhere else in the level to gate progress behind finding the key.

Item

A collectible. On interact it adds its Item ID to the global inventory and disappears. Items show up in the inventory menu and can be used to unlock doors.

Item ID: The id added to the inventory on pickup. Use the same id on a door's Item ID to make this item that door's key.
Display Name: The friendly name shown in the inventory UI, for example A Gold Key. Falls back to the Item ID when left blank.
Interact Text: Optional override for the crosshair verb, for example Take.

NoteUse case: keys, quest items, and any pickup. A keycard for a locked door, a fuse for a broken panel, a collectible the player needs to find.

Audio Log

A collectible voice recording. On interact it plays as a 2D voiceover with subtitles that appear in time with the speech, registers itself in the inventory's Audio Logs tab so the player can replay it anytime, then despawns.

Audio Clip: The voice file. Browse to pick a clip and it is copied into audio/logs/ on sync.
Interact Text: Optional override for the crosshair verb.
Title / Speaker: Shown with the log in the inventory and on screen, so the player knows what they picked up and who is talking.
Transcript & Subtitles: Play the clip right in Blender and hit Capture Line at the moment each subtitle should appear, building the timed spoken lines in order. Reorder lines with the arrows, then Save. An offline auto-transcribe can fill the lines in for you to fine tune.

NoteUse case: exposition and lore without cutscenes. Diaries, voicemails, recovered recordings, a character narrating the backstory of a place.

Animated

Plays a Blender animation in-game on a continuous loop. Animate the object in Blender, tag it Animated, and it keeps animating in Godot with no export step. Each animated object runs independently.

Action: The Blender action to play. Pick one from the list, or leave it on Auto-detect to let the importer match an action by the object's name.
Anim Speeddefault 1.0: Playback rate multiplier. Negative values play the animation in reverse.
Loop: Replays the clip from the start each time it finishes.
Ping-Pong: Plays the clip forward then backward, back and forth, instead of restarting.
Sound: An optional sound that plays when the animation starts. It loops while the clip loops or ping-pongs, and plays once otherwise. Browse to pick a file, copied into audio/sounds/.
Play Sound At: Whether that sound comes from the object's location (positional) or from the player (always full volume).

NoteUse case: ambient motion. Ceiling fans, spinning signs, flickering screens, scrolling conveyor belts, idle machinery, anything that should feel alive in the background.

Player Start

The spawn point for the level. On entry the player is teleported to this object's position and facing (yaw), then the marker deletes itself. It is best applied to an Empty so it does not show up as geometry.

No properties: Position and rotation are the settings. Place and aim the Empty where you want the player to land and look.

Heads upOnly one object per .blend can be the Player Start. If you set a second one, the add-on moves the spawn to the new object.

NoteUse case: every level needs one. Also handy for moving the start point while you iterate on a level's opening.

Triggers

What an object does when the player interacts with it or walks in.

Trigger general properties

Trigger panel with Interact/Volume activation, a Prompt, Fire/Toggle mode, and an Only if section.

A trigger is a stackable capability you can add to any object, on top of its role. Make this object a trigger, choose how it fires, optionally gate it behind conditions, then stack the actions it runs. There is one trigger per object, and all its power lives in the action stack.

Interact: Fires when the player looks at the object and presses the use button. This is the choice for things the player deliberately operates: levers, buttons, switches, examining a panel.
Volume: Fires when the player walks into the object's bounds, no button needed. The mesh becomes an invisible trip volume sized to itself. Great for ambushes, scripted moments, and entering an area.
PromptInteract only, default use: The verb shown in the crosshair prompt while the player is looking at the object, for example pull lever or open.
Re-fireVolume only: Every Entry fires the trigger each time the player walks in. Once fires a single time per playthrough then disarms, and that is remembered in saves.
Fire: Runs the action stack top to bottom on every activation.
Toggle: Alternates on each activation: it runs the stack, then reverses it next time, then runs it again, and so on. Perfect for a switch that turns something on, then off.

Only if (conditions)

Conditions gate a trigger behind named game states. With no conditions the trigger always fires. Add one or more and the trigger only fires when they all pass. States are set by Set State actions elsewhere, which is how objects talk to each other and how you build puzzles and progression.

State name: The named state to check, for example power_on or has_seen_intro. The plus button adds a condition, the X removes one.
Operator: How the state is compared. The options are listed below. Equals and not equals also show a value field to compare against.
Show prompt even if conditions are not metInteract only: Keeps the crosshair prompt showing while the conditions fail, so the object still looks interactive. It will not actually fire until the conditions pass. Off means no prompt appears until they pass.

Operator	Passes when
is on	The state is true, non-zero, or non-empty.
is off	The state is false, zero, empty, or unset.
equals	The state equals the value you type.
not equals	The state does not equal the value you type.
is set	The state has been set to anything at all.
is unset	The state has never been set.

NoteUse case: a locked terminal that only works after power_on is set, a door that opens once you have flipped three switches, a one-time scare that checks it has not played yet.

Trigger actions

The stack of things a trigger does, in order, with delays as needed.

How actions stack and chain

The Add Action menu listing Animation, Sound, Look Camera, Light, Set State, Level Transition, Auto Save, Death, Game Win, and Delay.

Actions are where triggers get powerful. A single trigger can hold as many actions as you like, and they run top to bottom in the order they are listed. Reorder them with the up and down arrows on each action's header to control exactly what happens first.

Drop a Delay action into the stack and everything below it waits that many seconds before running. Stack several delays and you have a simple timeline: play a sound, wait half a second, swing a door, wait a second, switch the lights, then transition to the next level. No scripting required.

•Add actions with the Add menu. Each one gets a collapsible header showing a one-line summary.
•Reorder with the up and down arrows. Order is the order they fire.
•Animation and Sound actions can target the trigger object itself (Self) or another object.
•A Delay pauses the stack before the actions beneath it, so you can stagger and sequence events.
•If the trigger's mode is Toggle, the whole stack reverses on every other activation.

NoteBecause conditions, Set State, and these actions all share the same named states, you can chain objects together: one trigger sets a state, another checks it, and a third reacts. That is how you build real puzzles.

Animation

Plays a Blender action on the target object when the trigger fires. The target needs an animation assigned in Blender so it can export.

Self / Object: Whether to animate the trigger object itself or another object you pick.
Action: The Blender action (clip) to play. Auto-detected by name when left blank.
Speeddefault 1.0: Playback rate multiplier.
Loop / Ping-Pong: Loop replays from the start. Ping-Pong plays forward then backward. Leave both off for a one-shot play.

NoteUse case: a lever that pulls down, a drawbridge that lowers, a machine that powers up, a trap that springs.

Sound

Plays a sound when the trigger fires, either positionally at an object or flat at the player.

Self / Object: Which object the sound is associated with when played positionally.
Sound: Browse to pick a file, copied into audio/sounds/, or type the name of one already there.
Object / Player: Object plays the sound at that object's position in 3D space. Player plays it flat at the player, always full volume, good for stings and UI feedback.
Loop: Whether the sound repeats until something stops it.

NoteUse case: a button click, a distant explosion at a location, a whoosh as a door opens, a music sting at a key moment.

Look Camera

Blends the player's view into a fixed camera, then hands control back when they exit. Use it for curated framing: sitting at a desk, lying on a bed, peering through a window, focusing on a scripted moment.

Camera: The camera object to blend the view into.
Transition (s)default 0.2: How long the blend into the camera takes.
Can Look Around: When on, the player can nudge the view within a clamped glance range while in the camera.
Exit when: Press Interact lets the player leave on the use button (with its own prompt). Timer leaves automatically after a set time.
Leave After (s)Timer exit, default 3.0: How long the view stays in the camera before returning to the player.

NoteUse case: sit-down moments, security camera views, framed reveals, a forced look at something important across the room.

Light

Switches lights on, off, or toggles them. Each time the trigger fires, the light or group toggles. This is the modern replacement for the old light switch, and it works with the Light Channel role for grouping.

Light / Collection: Target a single light object, or a whole collection of lights to switch together.
Light / Collection picker: Which light object or collection this action controls.
Starts: On means the light is on at level load and the trigger turns it off first, then on, and so on. Off means it starts off and the trigger turns it on first.

NoteUse case: a wall switch for a room's lights, a breaker that powers a whole collection, a flickering light you toggle as part of a scare.

Set State

Sets, toggles, or clears a named game state. States are the memory that ties your world together. Other triggers read them through Only if conditions, so this is how you build cause and effect across objects.

State: The name of the state to change, for example power_on or switches_flipped.
Set: Sets the state to the Value you type below.
Toggle: Flips a true/false state to the opposite of what it is now.
Clear: Removes the state, so an is unset condition would pass again.
ValueSet only: What to set the state to. Type true or false, a number, or text, and it lands as the right type for conditions to compare.

NoteUse case: flip power_on when a generator starts, mark visited the first time the player enters a room, count progress toward opening a gate.

Level Transition

Travels to another level in your game when the trigger fires, running the loading screen and title card on the way. This is the action behind a door that leads to the next area, or a volume the player walks through.

Level: Pick the destination from the levels in your project. If the list is empty, create another level first so it can be picked.

NoteUse case: pair with a Volume trigger at a doorway for a seamless walk-through transition, or with an Interact trigger on an elevator panel. Stack a Delay before it to let a door finish swinging first.

Auto Save

Quietly saves the game to the autosave slot and shows a brief Saving indicator in the bottom-right. It has no settings, just drop it into a stack.

NoteUse case: checkpoint the player at key moments. After a boss, at the start of a new area, right before a risky section, or just inside a Level Transition's stack so progress is never lost.

Death (Game Over)

Fails the player and shows the game-over menu, where they can continue from the last save or quit to the main menu.

Fail Messagedefault YOU DIED: The line shown on the game-over screen.

NoteUse case: a hazard volume the player walks into, a trap that springs, a monster's attack. Set the message to fit the moment.

Game Win

Ends the game with a victory screen. It rolls the credits with your credits music, both set in Game Settings.

Win Messagedefault THE END: The line shown as the game wraps up.

NoteUse case: the final objective. Reach the exit, defeat the last threat, or pick up the last item, then roll credits. Set the credits text and music in Game Settings.

Delay

Pauses the stack before the actions below it run. This is the key to sequencing: place delays between actions to time out a whole chain of events.

Secondsdefault 0.5: How long to wait before the actions beneath this one fire.

NoteUse case: stagger a sequence. Play a click, wait, open a door, wait, switch the lights, then auto save. Build a moment beat by beat without writing any code.

Object Data Properties

Light settings that make Godot match your Blender preview.

FPK Light Settings

Select a light and open the Object Data Properties tab to find this panel. Blender's glTF export only carries a light's type, color, energy, range, and spot cone. Everything that makes real-time lighting look right in Godot (shadows, soft-shadow size, attenuation, specular, indirect and volumetric energy) gets dropped, and Blender Area lights are not exported at all. This panel closes that gap.

It writes snake_case custom properties onto the light so they ride through to Godot on import, and Apply to Blender Light pushes the same values onto the Blender light so your viewport preview matches the game. Energy is expressed in Godot units and used as the single source of truth, so the panel value, the Blender preview, and the in-game light all agree.

Light type: Omni (point), Spot, Directional (sun), or Area (rectangle). Area lights become a Godot 4.7 AreaLight3D, which FPK rebuilds on import since Blender cannot export them.
Light: Energy (brightness in Godot units), Color, Specular strength, Indirect Energy for GI contribution, and Volumetric Energy inside fog.
Shape & Falloff: Per type. Range and Attenuation for omni, spot, and area. Cone Angle and Cone Softness for spot. Width, Height, and Normalize Energy for area. Attenuation of 2 is physically accurate inverse-square.
Shadows: Cast Shadows, Source Size for soft penumbras (Angular Size on the sun), Shadow Bias and Normal Bias to fight acne, Shadow Opacity, and the sun's cascade Shadow Mode.
Apply to Blender Light: Pushes these values onto the Blender light datablock so the viewport preview matches Godot as closely as Blender can.
Clear FPK Light Settings: Removes the FPK light tags from the object.

NoteArea lights and several of these controls target Godot 4.7. Volumetric energy needs the Forward+ renderer, which the project uses.

Still have a question?

Ask on the rileyb3d questions page and Riley will answer personally. Answers stay public so they help the next builder.

Ask a question Contact Riley

Loading…

Profile

What you get

Itch.io / Direct Download (.zip)

One self-contained file with everything baked in, wrapped in a versioned .zip. Upload to itch.io or link it for download.

Steam (SteamPipe content folder)

A clean folder with the game and .pck side by side, no archive. Point your Steam depot at this folder and Steam does the patching.

Portable single file

Just one self-contained file with everything embedded. The quickest thing to send a tester.

Suffix

What it builds

Collision (-col)

Keeps the visible mesh and adds solid collision from its exact triangles. Accurate but heavier. The standard choice for static geometry the player bumps into.

Collision Only (-colonly)

Same triangle collision as -col, but deletes the visible mesh on import. Use it when you modelled a separate, simpler collision shape.

Convex Collision (-convcol)

Keeps the visible mesh and adds a cheaper convex hull. Best for small or moving props. Not for hollow rooms.

Convex Collision Only (-convcolonly)

Same convex collision, but deletes the visible mesh. For invisible convex collision volumes.

Occluder (-occ)

Keeps the visible mesh and adds an occluder so Godot can skip drawing things hidden behind it. Put it on big solid blockers.

Occluder Only (-occonly)

Turns the mesh into an occluder only and deletes the visible mesh. A cheap stand-in used purely for occlusion culling.

Don't Import (-noimp)

Godot ignores this object completely. Handy for blockout, reference, or guide meshes.

Role

In one line

Physics

A pick-up-and-throw rigid body.

Inspect

Hold an object up to study it, then put it back.

Radio

A toggleable looping sound source.

Door

A hinged door, optionally locked behind a key.

Item

A collectible that goes into the inventory.

Audio Log

A voice recording with subtitles, replayable from the inventory.

Animated

Loops a Blender action forever.

Player Start

Where the player spawns into the level.

Look Camera

Blend the view into a fixed camera, like sitting at a desk.

Light Channel

Tag lights so a trigger's Light action can switch them.

Level Transition Area

A walk-in volume that loads another level.

Operator

Passes when

is on

The state is true, non-zero, or non-empty.

is off

The state is false, zero, empty, or unset.

equals

The state equals the value you type.

not equals

The state does not equal the value you type.

is set

The state has been set to anything at all.

is unset

The state has never been set.