I hadn't thought about it before, but now I'm rather interested in exactly they'll handle this. It also provides thousands of plugin-specific messages, such as usage notes and bug warnings, to help keep your game healthy. I suppose they can somehow add in native SKSE-awareness to Steam like NMM has (possible, but unlikely IMO), host SKSE mods with a disclaimer on them about requiring a third-party download, or not allow SKSE mods on the Workshop at all. But I'm not sure how far Valve and Bethesda will go into supporting SKSE more than it already is, considering SKSE is a third-party tool (it works fine as is as long as you're willing to download it, install it, and run it yourself.which is just like how Oblivion, FO3, and FO:NV are). They may not always want to download a new SKSE, and just want what they have. Some less saavy users may still find this information pertinent into the future. But Valve was nice enough (after a bit of an outcry from the Oblivion modding community) were nice enough to work out a fix in conjunction with an updated build of OBSE at the time (I forget the specifics on how they did it). SKSE already got updated for what was literally a 500kb update to change the UI on CC for the Creator Content Bundles. For most other games, encrypted executables won't matter too much because most games don't have something like OBSE that hooks directly to the EXE.

Then again, from what I remember, the OBSE situation was a little different in that when Steam first started selling Oblivion, OBSE didn't work *at all* with the Steam version of Oblivion due to the Steam version of Oblivion.exe being encrypted (as are all games bought on Steam part of how Steam's DRM works). Maybe they'll help out again once the SKSE is farther along? Well, Valve helped get OBSE working with Steam via hooking it into the overlay.

Skse download steam