mcc-chatbot-authoring

To create an MCC chat bot, use the bundled authoring-reference and script template to ensure correct lifecycle hooks like Initialize, AfterGameJoined, and Update, plus proper metadata for standalone /script bots that load and register correctly.

MCC script bots break on premature SendText calls in Initialize because the connection is not fully established yet; move chat logic to AfterGameJoined or later hooks and validate lifecycle compliance using the bundled authoring-reference patterns.

To wire a compiled built-in bot into MCC, apply the required config and registration edits at the Settings.cs and McClient.cs insertion points, following Brigadier command practices and the bundled cookbook patterns for proper lifecycle integration.

To fix unreleased movement locks and inventory mutation errors in MCC chat bots, use the repair guidance to ensure missing unregisters are addressed in OnUnload and that inventory operations follow validated pattern-cookbook practices.

Yes, you can port existing chat bot scripts to MCC without a local checkout because the bundled reference, cookbook files, and templates serve as the source of truth for metadata, lifecycle hooks, and registration wiring.

Authoring standalone MCC /script bots requires familiarity with C# scripting syntax to implement chat handling, event hooks, and movement logic, but the bundled templates and authoring-reference provide structured patterns to guide the process.