Getting Sword Fantasy Running Without Losing Your Mind
Sword Fantasy is a modding framework for Skyrim Special Edition that adds a new combat layer focused on parrying, riposte timing, and directional attacks. It is not a standalone game. It sits on top of Skyrim and requires SKSE64, the Creation Club content patch, and a handful of utilities most people forget about until the game crashes on startup. Download SKSE64 version 2.4.3 or later from the official site. Then grab the Creation Club content patch from Bethesda.net — the unofficial one works but causes NPC script conflicts in the second district of Riften if you skip it. Download the USSEP for skyrim version 1.5.97.0. After that you need the Sword Fantasy .esp itself plus the accompanying .bsa file. Both are typically hosted on the mod author's Nexus page. I used the v1.4.7 release because earlier versions had a memory leak that showed up after three hours of playtime on a save. The fix was just using the patched archive. Do not install Sword Fantasy before SKSE. I tried that once on a fresh build and the parry system completely refused to register input. Took me two hours to figure out the issue because SKSE loads first and the mod hooks into its message pipeline.
Installation Steps
Extract the SKSE64 files directly into your Skyrim directory where Skyrim.exe lives. This is non-negotiable — putting it in Documents or a subfolder breaks every hook the mod depends on. Copy the Sword Fantasy .esp and .bsa files into your Data folder. If you are using Mod Organizer 2, add the plugin through the plugin manager rather than dropping files manually. I switched to MO2 after my third crash and it has been stable since. Launch the game via the SKSE launcher, not the regular Skyrim.exe. The loader is what initializes the script hooks. If you bypass it, the sword fantasy system will silently fail to load. You will notice immediately because blocking does nothing and the UI never shows the stamina cost for parries. I learned this the hard way on a laptop build where the Steam overlay was conflicting with the launcher.
Sword Fantasy Configuration Gotchas
The config file sits at Data/SKSE/Plugins/SwordFantasy.cfg. The default settings are conservative but most people want to adjust two values right away: ParryWindow and RiposteDamageScale. ParryWindow controls how many frames you have to time a successful block-into-parry transition. The default is 12 frames at 60fps, which translates to about 0.2 seconds. That is tight. I set mine to 16 because the default made sword fights against armored enemies feel broken. You can push it higher but once you go past 20 the system starts feeling floaty and the directional hit detection gets wonky. RiposteDamageScale defaults to 1.5x normal weapon damage. Against DLC bosses it is brutal. I bumped it down to 1.2x for Dawnguard content because the expanded HP pools combined with the default scaling made Vyrthur die in three hits, which broke the pacing of that fight entirely.
Get the Full Details
Common Problems and How I Fixed Them
The most common issue is the parry animation not triggering during double-armored enemy swings. I ran into this specifically with the Forsworn Briarheart encounters. The enemy animation tree uses a staggered dual-weapon state that the mod's detection layer does not parse correctly. The workaround was adding a single-line entry to the CK under the Sword Fantasy script reference — change the animation event filter from OnAttackStart to OnAttackStart OR OnPowerAttackStart. This is a manual edit that requires the Creation Kit. If you do not have it installed, download it through the Steam Workbench tools menu. Another problem: the directional attack system conflicts with the Enhanced Lights and FX lighting engine. When both are active, the glow effect on charged swings flickers between two colors and drains performance by roughly 8 to 12 fps on a GTX 1060. The fix is in the SFEF plugin options — disable the sword glow shader and let Sword Fantasy handle its own particle effects. Performance returned to baseline within a minute of applying that change.
What It Does Not Do Well
Sword Fantasy does not integrate with weapon enchantments. Enchanted swords still deal their base enchantment damage and the mod will not multiply or scale those numbers. If you are playing with a glass sword of fire damage, the fire pulse triggers on every swing regardless of parry state. This is a known limitation and the author has no plans to address it. For players running heavy enchantment builds, the lack of synergy means you are essentially running two separate combat systems that occasionally overlap. It works fine but it is not seamless. Multiplayer mods are another area where this falls apart. Sword Fantasy was built for single-player only. Any mod that attempts to sync combat states across players — including Frostfall's multiplayer branch or the old UMP — will desynchronize after roughly four to six minutes of combat. I tested this once on a private server and gave up. The fix would require rewriting the hook injection layer, which is outside the scope of the current project.
Performance Expectations
On a Ryzen 5 3600 with 16GB RAM and a GTX 1660 Super, Sword Fantasy adds approximately 3 to 5 fps during dense combat encounters. Idle performance is unaffected. The mod processes input every frame and runs a lightweight state machine for each enemy in radius — the CPU cost scales with enemy count, not with player action. So a room full of five simultaneous enemies costs more than fighting them one at a time. This is worth keeping in mind if you run into stutter during large battles like the Battle of Fort Neugrad or the Dwemer ruin encounters. If your frame budget is tight, disabling the directional camera shake in the cfg file removes about 1.5 fps without noticeably affecting gameplay. The shake is cosmetic and easy to live without once you get used to the system.
