Hey.

I'm a little confused as to what goes where and how scripts work right now.

Basically, I modified one of the existing quests, tested it and it all works fine and everything. The issue comes in when other people are using it, it puts the source of the script in an archive automatically but it doesnt seem to work for anyone but me. I have also tried creating an archive with the compiled script inside of it too and it still refuses to work without the original compiled script in the data/scripts folder.

I have had totally mixed results though so far, and I dont know if it is an issue with Steam workshop or what, because sometimes it seems like its half working for people even though it fully works for me (Some stuff in the script obviously executes, but then it screws up) other times, it works for some people and not others, but all of the time it works 100% for me. I'm not sure what the fault could be, since a lot of people who have tried it have fresh installs also.

Thanks.

The source (.PSC), for others, won't do anything. You need to manually include the compiled version (.PEX) into your .bsa (doesn't happen automatically for pre-existing scripts), then it should override the vanilla code whether or not they have loose .PEX files.

My problem is that I tried that and it just didnt seem to work, people were still having the exact same issues as before. Are there any specific boxes in the archive tool that need to be ticked?

I'm including the PEX file in my archive and deleting the one in my /scripts folder, and the game just runs with the default script.

You sure the modified .PEX was in there? You can drag/drop stuff into the archive box, but there aren't any boxes to tick or anything in the CK's archive window.

Oh, I was just using the archive tool in the Skyrim folder, I wasnt aware you could drop stuff in the CK window.

There we have it I'd wager, with the required stuff in there, your plugin/bsa will override the default code for others.

Still no luck, I used the CK window to put the .PEX in the archive, its definitely in there, and it still refuses to override the default script.

I feel like I'm doing something wrong, when I browse my archive, the filename of the script is still intact, yet when I browse the archive of loads of other addons I have downloaded, they have scrambled filenames.

Bump, no ideas?

Well, after testing I can confirm the .PEX in a plugin's BSA will not override either the default .PEX in Skyrim - Misc.bsa or a loose (Data\Scripts\) default .PEX.

Using this http://www.mediafire.com/?97d0bks27wrwy7n, I was able to override AchievementsScript.pex when and only when the loose original was replaced. Start a new game without doing so, and there will be no message box.

*is glad they didn't specify what they'd wager*

Given one who edits the script is going to have a loose, modified version of the PEX, it would appear to them that their BSA is working when playtesting as it's actually the loose version that takes precedence, invalidating the BSA(s). A way around this would be to alter the QUST form to include either add a separate script or *replace the vanilla script, then the override to the QUST form when the plugin is loaded would ensure the desired changes are applied. Pretty sure the BSA's PEX is intended to 'win', though.

*Bad idea, generally

Wait, so how are you supposed to be able to distribute modified scripts over Steam Workshop? They only accept a .bsa, seems kinda silly if it is impossible to distribute modified .PEX scripts that way.

Will I have to create a new script and put it in place of the old one?

Yeah, loose files are the only way, currently, to make your override work. I've raised the issue elsweyr and am pretty sure that the BSAs' PEXs are intended to 'win'. Might be a bug that gets fixed with the next TESV.exe iteration.

Don't loose files normally come out on top? It seems to me more likely to be an issue with BSA loading, as the original compiled scripts are in another BSA, not loose files, so if they're not overridden then it's because Skyrim isn't loading files from BSAs in the right order.

I imagine this isn't an issue for entirely new scripts, right? Sorry, unable to test at the moment.

Cipscis

Nah, it isnt an issue for new scripts.

I renamed the script under Quest Stages, then pasted the entire source of the old one into a source for the new one. Now it works perfectly when loading from a BSA.

Today has certainly being a learning experience, considering I have never looked at any tutorials or used any creation kit for TES/Fallout games before, and decided to jump right in to make a quickstart mod

It is all working fine now anyway, thanks for the help.