SkyUI SDK for SkyUI 5.2?

[LearningNoob]

A noob asking for help from the Pros after searching for hours now 😅

 

I want to take my first steps with Papyrus scripting and I am missing the SkyUI SDK.

Actually I found this page SkyUI SDK but the latest version there is 5.1. This stuff is sooo old lol.

My installed runtime version is SkyUI_5_2_SE-12604-5-2SE which claims to be from 03 Oct 2017.

 

So I  am pretty sure that its a bad idea to compile scripts with an incompatible SDK version,

I would like to ask if anyone knows which version I should use with SkyUI 5.2 and where I can get it?

 

Many thanks ❤️

[zeelok]

I've been using the 5.1 SDK to build MCM menus that run against 5.2 ingame and it seems to work properly for that at least.

[LearningNoob]

9 minutes ago, zeelok said:

I've been using the 5.1 SDK to build MCM menus that run against 5.2 ingame and it seems to work properly for that at least.

Many thanks for the confirmation, I give that a try!

 

The next mess are the script directories:

 

Data/Scripts/              - .pex all Compiled Files
Data/Scripts/Source  - .psc CK Source Files
Data/source/scripts/  - .psc Source Files installed from Mods

 

Can I merge the files from both psc directories without overwriting different versions?

I guess vortex or mo2 will warn for conflicts.

And then I will symlink Data/Scripts/Source to Data/source/scripts/ to never worry again about this.

 

[traison]

All SkyUI SDK's that still exist (afaik). The issue is the links to them went down a long time ago. We tried to scrape together what we could but there's bits missing. Like is stated in the thread, the issue with SkyUI is that you *DON'T* need the latest one, you need the one that will work with the mod you're compiling. When you're working on an older mod, its quite likely it won't compile on a newer SDK version.

 

6 hours ago, LearningNoob said:

And then I will symlink Data/Scripts/Source to Data/source/scripts/ to never worry again about this.

 

If you want to create a mess that will bite you in the ass later, sure. The proper way to do that is to view the CreationKit.ini file and determine where the compiler expects the script sources to be. There's 2 standards, pick one. It doesn't matter which standard you pick, as mods generally are split 50-50 between the old and new standard. I use the old standard myself, as its folder structure makes more sense.

 

[Papyrus]
sScriptSourceFolder = ".\Data\Scripts\Source"

 

Edited September 28, 2024 by traison

[LearningNoob]

7 hours ago, traison said:

All SkyUI SDK's that still exist (afaik). The issue is the links to them went down a long time ago. We tried to scrape together what we could but there's bits missing. Like is stated in the thread, the issue with SkyUI is that you *DON'T* need the latest one, you need the one that will work with the mod you're compiling. When you're working on an older mod, its quite likely it won't compile on a newer SDK version.

 

 

If you want to create a mess that will bite you in the ass later, sure. The proper way to do that is to view the CreationKit.ini file and determine where the compiler expects the script sources to be. There's 2 standards, pick one. It doesn't matter which standard you pick, as mods generally are split 50-50 between the old and new standard. I use the old standard myself, as its folder structure makes more sense.

 

[Papyrus]
sScriptSourceFolder = ".\Data\Scripts\Source"

 

 

You are godsend, thank you so much for this information!

I feel like digging in ancient ruins finding more and more small artifacts from an unkown civilization in the past.

Maybe someday I will be able to construct this ancient machine of yet unknown capabilities and purpose 😅