[Segually]

Summary

Adds InteractableManager, which lets mod items act as chairs, beds, crafting stations, containers, or run custom behaviour when interacted with.

The game has no generic interaction system. Behaviour is hardcoded in two layers, both keyed on the object's item_name: the GameController.player_interact dispatch switch, and the InventoryUtils.IsChairObject / IsBedObject / etc. classification predicates. A modded object is inert because neither layer recognises its id. This manager patches both:

• a prefix on player_interact runs the registered behaviour for known ids and falls through to vanilla otherwise
• one shared postfix over the InventoryUtils.IsXObject predicates forces true for ids registered under that type (it never flips true to false)

InteractableManager.Instance.RegisterChair("MyMod:MyChair");
InteractableManager.Instance.RegisterBed("MyMod:MyBed");
InteractableManager.Instance.RegisterCraftingStation("MyMod:MyOven", "Crafting - Oven", "Oven");
InteractableManager.Instance.RegisterContainer("MyMod:MyChest", "Chest", pages: 2);
InteractableManager.Instance.RegisterCustom("MyMod:MyThing", ctx => { /* ctx.Controller / Target / Interactable */ });

Containers come with UI support.

Changes

• New Items/Items.Interactables.cs (InteractableManager, InteractableRegistration, InteractableType, patches).
• New Items/INTERACTION_SYSTEM.md documenting how the game's interaction dispatch works and how the API hooks into it.
• Base.GamePlugin.cs: initialize InteractableManager.

Notes

• Split out of a larger set of changes; the other PRs (assets, creatures, .gitignore) are independent of this one. The only overlap is a small init registration in Base.GamePlugin.cs, which may need a trivial conflict resolution depending on merge order.
• Builds cleanly on its own against current main.

🤖 Generated with Claude Code