ODEFEAT - REFORGED - BETA 1.6.0

1.6 — Guard defeats now go to jail

New

• Lose to a hold guard and you are arrested. Instead of rolling one of ODefeat's random outcomes, the defeat is handed to Skyrim's own crime system: you are taken to that hold's jail, your gear goes to the evidence chest and you serve the sentence, exactly like a vanilla arrest.
• Any prison mod you have installed takes over from there. ODefeat uses the same native call the vanilla "go to jail" dialogue uses, so it raises Skyrim's Jail story event — the hook every prison overhaul listens to. ODefeat then stops touching your character, so your prison mod stages the imprisonment its own way instead of fighting ODefeat for control.
• Only the guard who actually beat you counts. A guard who merely joined the brawl does not arrest you, and a guard with no hold behind them (some modded or quest guards) falls back to the normal outcome roll.
• The arrest is not part of the outcome weights, so it also takes precedence over third-party outcomes such as Simple Slavery. Turn it off in the MCM if you would rather keep the roll.
• New MCM section, Guards:
  • Guards Arrest You — the whole feature, on by default.
  • Guards Confiscate Your Gear — inventory to the evidence chest, on by default.
  • Serve the Sentence — a real sentence with the bounty cleared, on by default. Off simply drops you in the cell with your bounty intact.
  • Minimum Bounty on Arrest — Skyrim derives your sentence from your bounty, so a beating with no bounty attached would jail you for nothing and release you instantly. Defaults to 100; set it to 0 to keep your current bounty.
  • Let Prison Mods Take Over — on by default; leave it on if you run any prison mod.

Fixed

• An empty outcome table no longer indexes past the end of the list while picking a random outcome; it falls back to the safe wakeup as intended.

Note for existing saves

New settings read as zero in a save made before 1.6, which would look like "disabled, confiscate nothing, no bounty". A one-shot migration applies the intended defaults the first time you load, so nothing has to be reconfigured.

1.5 — Free camera, and the G-key crashes

Fixed

• Attacking with G could crash the game. Four separate causes, all on the player-as-aggressor path, all fixed:
  • The struggle animation parented the two actors to each other — victim to attacker and attacker to victim. That cyclic vehicle graph can hard-lock the engine, and with the player inside the cycle it took the camera with it. The animation is now held by movement locks alone, with no actor parenting.
  • Pressing G on someone already in an OStim scene destroyed that scene's thread. ODefeat never terminates a thread it does not own any more; the attempt fails cleanly instead.
  • Repeated or rapid G presses could build two scenes for the same pair. Presses are now serialized with a short debounce, so one press can only ever produce one scene builder.
  • Scenery, dead, disabled, unloaded or distant crosshair targets went straight into native movement and scene lookup. Every entry path now validates the actor pair, and the alignment coordinates, before touching anything.
• Ragdoll state is no longer wiped unconditionally at scene start.
• Strip state is reset per minigame, and dropped-item array accesses are guarded.
• Save/load during a struggle cancels the stale attempt, hides the bar and returns control and camera instead of leaving the player locked down.
• Corrected the OsexBar signatures and normalized the starting percentage.

New

• Free camera during the pre-scene struggle, on by default (Free Camera During Victim Struggle in the MCM). It starts once the surrender animation is playing and before OStim owns the scene, using OStim's own free-camera speed so it feels like the camera you already know.
• It only engages when you are the victim, never when you are the aggressor.
• It never fights another mod for the camera: if OStim already owns the scene, or free camera was already running, ODefeat leaves it alone — and it only ever restores the camera state it turned on itself, including on aborts, escapes and after a save/load.

Planned for future updates

• Gang rape — one victim, several aggressors. Today a scene is strictly two actors, so the extra enemies stand around. The plan is a cast of N aggressors with a 3 → 2 → 1 fallback: ask for the largest group the free aggressors and the installed animations allow, and step down until a scene is found.
• A queue. Whoever did not fit joins in when a scene ends, instead of being discarded.
• A choice of how aggressors are shared when you have followers with you: concentrate them on the player, or split them between everyone.
• Followers already get their own scene when Followers are Assaulted is enabled in the MCM — if you only ever see one scene, that setting is off.