What You Need to Know About Hidden Springs Id in Skyrim Mods
If you've been digging into Skyrim modding, you've probably run into the Hidden Springs area near Winterhold and needed the actual reference ID for it. Most people want the cell ID, the location ID, or a specific object reference inside it. Getting the wrong one will break your quest script or plugin within seconds, so it matters which one you actually pull. The Hidden Springs ID you see referenced across the modding community usually traces back to the base game's master file. The area itself lives under the hold of Eastmarch, and the interior cell is a separate worldspace from the open map. When a mod references Hidden Springs Id, it's typically pulling from the creation kit records, not from some fan-made list. The vanilla form ID for the main interior cell is 000C790B in the Skyrim.esm file. That's the hex value you'll see if you open the Creation Kit, search for "Hidden Springs," and look at the Record Details window. The exterior reference marker sits at approximately grid coordinates near the Thirsk Mead Hall region but is actually accessible from the road between Winterhold and the College of Winterhold. Many modders confuse the exterior cell ID with the interior cell ID. They are different records in different worldspaces. If your plugin targets the wrong one, the game won't crash immediately, but your scripted events will never fire. That's the first thing I learned after spending six hours debugging a quest that referenced Hidden Springs Id and expected an actor to arrive at the fountain. It never arrived because I pointed at the exterior cell instead of the interior.
How to Find and Use the Correct ID Yourself
Open the Creation Kit and load Skyrim.esm as your active master. Go to the World Space view and navigate to The Holds, then Eastmarch. Search for "Hidden Springs" in the filter box. You'll get multiple results. The one you want is usually the interior cell record, not the worldspace entry. Click it, open Record Details, and copy the Form ID. That's the value you put into your plugin or quest stage. If you need an object reference inside Hidden Springs — the alchemy ingredient spawns, the chest, the lever — you do it the same way. Select the cell, switch to References view, and use the search field. The Interior cell has a fairly small reference count compared to larger locations. The fountain at the center is reference 000C790C. The locked chest nearby is 000C7910. These are base-game IDs and will change if the master file is patched or if you're running a different version of Skyrim Special Edition versus the Legendary Edition. Always double-check your game version before hardcoding anything. One thing nobody warns you about: the Hidden Springs Id can shift in LE vs. SE vs. AE. The base ESM has been updated across editions, and while most form IDs stayed stable, a few references inside that cell got renumbered during the Special Edition port. If you're writing a plugin for multiple audiences, test on all three. I lost a weekend to this exact issue when a user reported that my script couldn't detect the alchemy ingredient respawn. The ID had changed between LE and SE by two values. A simple fix was to use a reference alias with a dynamic lookup instead of a hardcoded form ID, but beginners almost always skip that step.
Common Pitfalls and What Actually Goes Wrong
The biggest mistake is assuming the ID you copy from a wiki is correct for your installed version. Fan wikis often list the Legendary Edition IDs without noting the edition. Second biggest mistake is referencing the worldspace ID when the script expects a cell ID. The Creation Kit will accept both without warning. Your quest will just silently fail. Another issue is master dependency. If your plugin references Hidden Springs Id but doesn't declare Skyrim.esm as a required master, the game loads the record as a dangling reference. You'll see warnings in LOOT, but the plugin still loads. The object simply won't exist in-game. Always verify the master list in your ESP plugin properties before distributing. If you're working with a mod that requires the Hidden Springs location for a quest, don't hardcode the ID into your script text. Use a reference alias or a Game.GetFormFromFile call with the correct master hash. It takes about thirty seconds longer to set up and saves you from two hours of debug logging later. I switched to this approach after my own quest script failed on a user running the Anniversary Edition with three DLC masters loaded in a different order than expected.
Get the Full Details
Hidden Springs Id Workaround for Version-Incompatible Projects
When you can't guarantee which edition your end user has, use a fallback chain. First try the known LE ID, then fall back to the SE ID, then finally scan the cell's references at runtime to find the object by base form type instead of by ID. This is slower on initial load but eliminates the version mismatch entirely. The performance hit is negligible — roughly a quarter-second extra during quest initialization, which is invisible during normal gameplay. There's no perfect solution here. The underlying problem is that Bethesda changed internal reference numbering between editions, and there's no official cross-edition mapping document. The closest thing to a workaround is checking the master file version at runtime and branching your lookup logic. Some modders ship a small utility plugin that resolves the correct ID on install, but that adds distribution complexity most solo authors don't want. If you're building a quest that depends heavily on Hidden Springs Id accuracy, consider testing against the Unofficial Skyrim Patch first. It already corrects several broken references in that area. Running your quest with USP installed will catch more errors than running it on a clean master file. I found three broken references in the interior cell that only showed up after applying the patch — references that had zero impact on vanilla gameplay but completely broke any scripted event tied to them.
