> For the complete documentation index, see [llms.txt](https://pmc-docs.gitbook.io/pmc-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pmc-docs.gitbook.io/pmc-docs/prophunt-interaction-phi/introduction.md).

# Introduction

Prop Hunt Interaction Component (PHI) is a Blueprint-only gameplay interaction system built on top of the Physics Movement Component (PMC).

PHI handles prop-based gameplay features such as player transformation, visual feedback, and interaction effects, while PMC provides physics movement, replication, and authority handling.

***

> <mark style="color:$warning;">**Important:**</mark>\
> PHI requires Physics Movement Component (PMC) to function properly.\
> PMC does NOT depend on PHI and can be used independently.

***

### <mark style="color:blue;">What PHI Provides</mark>

PHI enables common Prop Hunt–style interactions, including:

* Prop-to-prop transformation
* Outline and highlight effects
* Interaction VFX
* Randomized transformation visuals

All interaction logic is designed to work directly with PMC’s replication framework.

***

### <mark style="color:blue;">Modular by Design</mark>

PHI acts as an optional interaction layer on top of PMC.

Movement and physics remain fully handled by PMC, while PHI focuses exclusively on gameplay interactions.

<mark style="color:$warning;">This allows developers to:</mark>

* Use PMC alone for physics-based movement
* Extend PMC with PHI for Prop Hunt gameplay
* Customize interaction logic without modifying PMC

***

### <mark style="color:blue;">Multiplayer Ready</mark>

PHI follows PMC’s authority model and supports <mark style="color:blue;">Client Authoritative</mark>, <mark style="color:blue;">Server Authoritative</mark>, and <mark style="color:blue;">Custom replication setups</mark> (including external plugins), ensuring consistent interaction behavior across all clients.

***

### <mark style="color:blue;">Blueprint-First</mark>

PHI is implemented entirely in Blueprint and exposes all core features through simple, modular events and variables.

<mark style="color:$info;">No custom C++ code is required.</mark>