BepInEx Interop Patcher is a startup patcher for interop-generation conflicts, not a player-content mod. Its recorded role is limited to resolving conflicting internal type names while BepInEx prepares interop code during startup. This page keeps validation focused on that recorded conflict rather than treating it as a general startup remedy.
Startup purpose
The patcher works during startup when interop generation encounters conflicting internal type names. Its purpose is to address that recorded conflict so the affected loading path can continue. It does not add a player-facing feature or a gameplay change.
The recorded description places the patcher in the startup path rather than in a content workflow. Treat it as relevant only when the observed issue matches the interop-generation conflict described here. Other startup failures remain outside this page's conclusion.
Patcher versus plugin role
A startup patcher acts before normal plugin loading reaches its usual role. A normal plugin directory is for plugin files, while this patcher has a separate startup responsibility. The two locations should not be treated as interchangeable.
Keep the patcher distinct from player-content mods in your own change record. That separation makes it easier to review the role you are testing. It does not establish a broader loader arrangement.
Use the recorded patchers directory
Place the recorded patcher in BepInEx/patchers/. This is the directory stated for this startup patcher in the captured material. This page does not confirm another placement.
Record the directory together with the patcher's identity before testing. That supports a focused review of the startup path you changed. It does not turn the patchers directory into a plugin directory.
Validate the recorded conflict only
Launch the game and check only whether the recorded interop-generation conflict no longer blocks the relevant loading path. Record the result for the startup condition you actually observed. Do not use that result to make a claim about unrelated startup behavior.
If the same conflict remains, keep the result limited to the current setup. Recheck the recorded directory and the observed condition before changing anything else. An unclear result is To be confirmed.
Historical requirements to confirm
The captured material includes historical capability and loader requirements. Their current applicability is To be confirmed. This page does not state a fixed required version.
Compatibility can vary with the BepInEx build in use. The captured record does not prove permanent behavior across arbitrary BepInEx builds. Keep any current compatibility conclusion To be confirmed until it is independently established.