Collision Settings Debugger

Diagnosing Primitive Component Collisions in Real Time

Setting up collision responses across actors and primitive components frequently leads to situations where physics interactions, hit events, or overlap traces fail without an obvious visual cause. Primitive components rely on precise channel responses, object types, and collision enabled states. When an interaction fails in the middle of gameplay, verifying which specific primitive component holds the incorrect profile often turns into a tedious process of opening actor blueprints, checking individual component details panels, and guessing where the mismatch occurred.

Collision Settings Debugger addresses this breakdown by placing collision verification directly inside the runtime environment. Instead of stopping execution to sift through static settings in the editor viewport, the plugin provides immediate insight into the active configuration of primitive components while the project is running. The tool exposes whether a component is set to block, overlap, or ignore specific channels, giving developers a direct window into the actual values running in memory.

The Gameplay Debugger Collision Category

The core interface of the plugin attaches directly to the engine's built-in gameplay debugger framework. Collision Settings Debugger introduces a dedicated "Collision" debug category that can be activated on the fly during gameplay sessions.

Once toggled, the Collision category prints collision settings for primitive components directly on the screen. Because the data renders within the gameplay debugger overlay, developers can move through a scene, target specific entities, and review the exact collision states assigned to individual primitive components without cluttering standard viewport view modes. This provides immediate visual confirmation of how components are configured relative to surrounding actors, eliminating the guesswork when traces pass through geometry or overlaps fail to register.

Blueprint Nodes for Querying and Printing Collision Setup

In addition to the visual HUD integration provided by the gameplay debugger, Collision Settings Debugger includes a collection of Blueprint nodes created specifically to query and print collision setups programmatically. These nodes expand debugging workflows beyond manual observation by allowing developers to integrate collision checks into their game logic.

Using the provided Blueprint nodes, developers can:

• Query the exact collision setup of a primitive component at runtime to evaluate active responses in script.
• Print collision setup information to the log or on-screen output when specific gameplay conditions or testing triggers are met.
• Inspect dynamic changes when actors change their collision presets during runtime events, stance adjustments, or state shifts.

Having dedicated nodes to query collision data allows teams to script diagnostic routines into test levels. When a test character fails an interaction test, a Blueprint graph can execute the query node to isolate whether the primitive component was set to the wrong channel response before passing the data to the print node for immediate review.

Built from Practical Production Needs

Collision Settings Debugger was created directly out of practical frustration encountered during active project development. When collision configurations do not work as expected, tracking down which component carries the offending flag slows down implementation. The developer developed this toolset specifically to solve that issue within their own game project, ensuring the tool answers genuine testing requirements rather than theoretical use cases.

Because the utility originated in a live game workflow, its functions focus on fast, direct data retrieval. The integration with the gameplay debugger keeps the profiling lightweight and instantly accessible via existing debug inputs, while the Blueprint nodes allow rapid verification without writing custom C++ diagnostic helpers. The plugin maintains verified compatibility with State Component - Organize Any Game Logic, allowing teams organizing their architecture around state components to cleanly debug collision transitions as game states change.

Targeted Troubleshooting Workflows

Projects featuring multi-component actors—such as characters with separate hurtboxes, interaction volumes, and physics hulls—frequently suffer from overlapping collision definitions that conflict with each other. By running Collision Settings Debugger, developers can isolate each primitive component on an actor to verify that interaction volumes are strictly querying the intended channels while structural meshes maintain appropriate blocking rules.

The combination of an on-screen gameplay debugger category and runtime Blueprint nodes provides both passive and active verification pathways. Whether monitoring primitive components during live traversal or printing collision setups from scripted test routines, Collision Settings Debugger turns silent collision failures into clearly readable data.

Explore Similar Assets

• Auto Settings
• Cinematographer PRO - A Cinematic Photorealistic Camera System
• Did it hit - Trace Detection Plugin
• Physics Collision Sound
• ProInstance Tools Plugin