Skyrim SE Creation Kit on Linux (Proton)

Intro

I ended up wanting to do some map edits in Skyrim SE during a recent playthrough, and the only reasonable way to do that is via the Skyrim Special Edition: Creation Kit. I hadn't had much trouble getting Skyrim mods working on Linux/Proton, but Creation Kit took me a bit of doing before I actually got it up and running. So, I figured a brief little guide here might not go amiss. Perhaps someday this page'll get picked up among all the AI Slop; who knows.

I'm writing this in early March, 2026. Depending on when you read this, it's possible that this information could be out of date to varying degrees of severity. So beware of that! And of course, your mileage may vary regardless, even if you stumble across it shortly after publishing.

Installation

Software Selection

First off: one thing that tripped me up is that I didn't realize that there's a "Skyrim Special Edition: Creation Kit" which is separate from "Skyrim Creation Kit." I'd had the latter in my library from ages ago and had started to try and get that working at first, since it was just already there in my Steam library. Since I was using the Special Edition on this playthrough, though, obviously wouldn't end up working out too well. So make sure you're using the one that matches the game version you're actually using.

It's possible that Proton version could be important. At time of writing the most recent non-Experimental Proton is 10. In my experience, Proton 9 often ends up working a lot better than 10 for "real" Windows GUI apps (ie: not just games), so I ended up going with that. (That was also just coincidentally the version I'd had installed once I figured out some of the tricks below, so don't take that to mean that it doesn't work well in Proton 10 -- I've honestly not really tried it out in anything but 9.) It's possible you could use a generic Wine version to run it, but since Creation Kit is a Steam-aware app, I figured it made sense to just stick with Proton.

Run it on top of Skyrim itself!

The main hangup I ran into is that it turns out that Creation Kit needs to be installed in the same directory as Skyrim! If you try to run it without, you'll get various kinds of immediate crashes. The first will be that it can't find steam_api64.dll (or steam_api.dll for the non-Special-Edition version), but even if you copy just that DLL in place, it won't work. Needs to have the Skyrim data right there and available.

This poses some interesting challenges when running things on Linux via Proton, since apps with different Steam IDs get run under different sandboxed prefixes. I did do a couple cursory attempts to get CK to run under Skyrim's prefix, but it seemed like the binary had its Steam ID hardcoded and even though I was setting the environment variables and such properly, it kept launching via its own prefix.

There are probably some very elegant ways to handle this. What I did in the end was rather stupid (but it works): by literally copying over all my Skyrim install dir content into the Skyrim Special Edition 1946180 where CK gets installed. Skyrim's disk requirements aren't notable by today's standards (and I don't use mods which significantly affects that), so that seemed fine to me. It means I'm not actually writing out files to the Skyrim directory itself (and would thus have to manually copy an edited .esp over) but whatever. This approach does have the benefit of being able to use totally separate Proton configs between Skyrim and CK, while not having to fight through sandboxing issues. And it's honestly a little nice that you've got an inherent buffer to prevent accidental file overwrites and such. Anyway: probably not ideal but whatever, it works.

At this point, I was able to launch CK just by launching it from my Steam library as I would with anything else in Steam, though there's one more hurdle to overcome:

Dealing with Script Unpacking

During the initial runs of Creation Kit, it'll throw up a dialog asking about unpacking Scripts. Ordinarily you'd want to do this, as it lets you edit+compile Papyrus scripts while inside Creation Kit, but it looks like it probably calls out to the OS to do this unpacking, and that seems to fail on Proton/Wine (or at least it resulted in crashes for me).

What I did instead was just manually unzip the scripts, and hit "No" when that dialog comes up. The file is located at Data/Scripts.zip, and will extrtact a bunch of data into Source/Scripts and DialogueViews. I actually have no idea if unzipping manually and hitting "No" to the dialog leaves CK in a state where you can work with scripts effectively -- for what I was doing, I didn't need to poke at any. So buyer beware on this one!

Post-Install Configuration

Now we're heading into some territory which is a bit more generic "How to use Creation Kit." First up, there's a couple of edits to CreationKit.ini to make. First up, in the [General] section at the top, add these two lines:

bAllowMultipleMasterFiles=1
bAllowMultipleMasterLoads=1

And then, down below in the [Archive] section, you need to add the Dawnguard, Hearthfire, and Dragonborn .bsa files to the list in SResourceArchiveList2. It'll look like this:

SResourceArchiveList2=Skyrim - Voices_en0.bsa, Skyrim - Textures0.bsa, Skyrim - Textures1.bsa, Skyrim - Textures2.bsa, Skyrim - Textures3.bsa, Skyrim - Textures4.bsa, Skyrim - Textures5.bsa, Skyrim - Textures6.bsa, Skyrim - Textures7.bsa, Skyrim - Textures8.bsa, Skyrim - Patch.bsa, _ResourcePack.bsa, Dawnguard.bsa, Hearthfires.bsa, Dragonborn.bsa

If you're working with mods which have their own .bsa files, you may need to add those to the list too. For instance, I had been working with Elysium Estate SSE and needed to add in ElysiumEstate.bsa as well.

SSE CreationKit Fixes / Creation Kit Platform Extended for Skyrim

I'd highly recommended that you additionally install Creation Kit Platform Extended for Skyrim (a continuation of SSE CreationKit Fixes). You basically just unpack it right on top of the Creation Kit install, and it'll do its thing. For Proton on Linux, though, you do need to make sure to alter Creation Kit's startup command (via Steam, in General -> Launch Options to this:

WINEDLLOVERRIDES="winhttp.dll=n,b;d3d11.dll=b,n" %command%

Technically d3d11.dll is only be necessary if you're also using ENB, which I'm not, so I can't help much with that in specific. The winhttp.dll override is what allows CKPE to load in properly.

This addition greatly improve the Creation Kit experience. The app starts up much more quickly, loads data and enters cells much more quickly, doesn't have endless "warning" popups while doing anything, has a more polished UI, and is just generally great all around. You can do without, but I highly recommend it! It'll be quite obvious that the install has worked once it loads up.

Potential Linux-Specific problems

Scene / Dialogue View Editor

I haven't actually tried this myself, but it seems as though Scenes and the Dialogue View Editor might not work under Linux/Proton. I believe that those components might make use of some kind of flowchart-like application which gets registered separately, outside of Creation Kit, or something. Anyway, as I say: I haven't looked into that myself, but be aware of it!

Object Linking

One crash I did experience consistently which I'd seen reported elsewhere is while trying to link objects. Here's a related thread at Nexus, for instance.

The solution recommended in that thread does work great, though, and honestly feels like it may even be a lot nicer once you're used to it (or at least it was for me while creating bookshelves from scratch). Basically click on the object once and then View -> Reference Batch Action Window. The object you clicked on will be in the lefthand list (if you're in a position where you want to do the same thing to a bunch of objects, you can presumably add more). Select Set linked ref on the options list on the right, and then hit the Select Reference in Render Window button to choose what to link to (note that it's a double-click to choose the object out in the render window). There's still the "Keyword" dropdown once you've done that, and then you hit "Do" to actually set up the link.

The awesome thing about that is that the dialog stays put exactly as it was after you do it. If you are (for instance) setting up a new bookshelf from scratch, and have eighteen DefaultBookShelfBookMarkers to link up, each with a different numeric keyword, this is IMO far nicer than the usual way, because that keyword dropdown stays on the value you just selected, so it's trivial to just move one more down for the next book marker. Using the "regular" ref-linking dialog, it's a new dialog each time, so you're selecting that keyword totally from scratch. So yeah, not too shabby!

Note that the "Ctrl-Space" thing in the post I linked to doesn't actually seem to exist in Skyrim's Creation Kit -- that might be something specific to the Fallout 4 version (which is what that post actually talks about).

Other

One thing that actually works great for me is using copy+paste to duplicate working bookshelves between cells in the game. I'd been diving into Creation Kit specifically to add bookshelves to various places, and I'd run across a ton of posts saying that copying bookshelves tended to crash CK. I actually basically didn't run across that at all. I did have one crash which could've been related, but it was quite early on and maybe even prior to installing Creation Kit Platform Extended. Anyway, if you too are looking to work with bookshelves, I'd say feel free to try copy+paste from "warehouse" type setups and see how it goes. Just save your work first, just in case!

Then, finally, one really handy thing I came across was a interface cheatsheet for Creation Kit. There's a ton of other information out there which can help you figure things out, of course, so search around and you should be able to find tutorials for practically anything you want to do in there, be it text or video.

Changelog