Chain moves
When a moderator moves one part of a chain to a different forum, the add-on has to decide what to do with the rest of the chain. The behaviour is configured at AdminCP > Setup > Options > [MC] Thread Split > Thread move behavior.
| Mode | Behaviour | When to use |
|---|---|---|
| Detach the moved thread from its chain (default) | The moved part is removed from the chain. The chain continues without it; the moved thread becomes a standalone thread in its new forum. | Treat each chain as belonging to a single forum. Moves to a different forum are explicit acts of taking a part out of the conversation. |
| Allow the chain to span forums | The moved part stays in the chain. Subsequent splits read the configuration of whichever forum the current part is in. | The chain is the unit of conversation, not the forum it lives in. Acceptable when forum overrides are similar across the relevant forums. |
| Move the whole chain to the new forum | All parts of the chain are moved to the new forum together. | The chain belongs to its forum and a manual reorganisation should keep it intact. |
Why the default is detach
Detaching is the lowest-impact choice: it leaves both the chain and the moved thread in defensible states. The chain keeps its remaining parts and continues splitting under its forum's rules; the moved thread is now an ordinary thread that any moderator can re-merge or re-link if they want.
Allowing the chain to span forums is technically supported but produces edge cases (mixed permissions, mixed thresholds, mixed continuation templates) that benefit from explicit moderator judgement.
What does NOT happen on a move
- The continuation post of any part is not rewritten when its predecessor is moved or deleted. Links inside continuation posts can become stale; this is an accepted trade-off.
- Watchers are not re-migrated when a part is moved. Existing subscriptions follow the part to its new forum; new watchers added after the move follow the normal rules for the target forum.