Hey, everyone! If you'd like to quickly help without reading this entire post, I would love it if someone who uses for example Notepad++ to write Papyrus could take the file in the Google Drive-link below and send back a readable text file or image or something to me, so that I can debug it properly, as the CK's error messages aren't giving me enough information. I haven't been able to get Notepad++ working with Papyrus myself. If you have the time though, I'd really apreciate it if you'd read the entire post, in case you have any insight into my problem.
So, where to even start? I'm making a quest mod, and I have written a script (we'll call it the Scavenger script) to make some enemies aggro at a certain point, and in the Quest Stages tab I've written a bunch of Papyrus fragments. At some point, the compiler started throwing up this error:
Papyrus Compiler Version 18.104.22.168 for Fallout 4
Copyright © ZeniMax Media. All rights reserved.
Starting 1 compile threads for 1 files...
C:\Users\fredr\AppData\Local\Temp\PapyrusTemp\Fragments\Quests\QF_FieldDayQuest_0100CF18.psc(130,22): cannot name a variable or property the same as a known type or script
No output generated for Fragments:Quests:QF_FieldDayQuest_0100CF18, compilation failed.
Batch compile of 1 files finished. 0 succeeded, 1 failed.
Failed on Fragments:Quests:QF_FieldDayQuest_0100CF18
This happened while I was changing some completely unrelated things in the Scavenger script. Everything had worked perfectly before, it had compiled everything smoothly, and I wasn't changing any names of any variables or properties. Just to make sure, I still changed all my property names to more distinct names, but the problem persisted. The error seems to be in the script-file which holds all of the given quest's Papyrus Fragments. I've been over all of my fragments, both in the Quest data tab and in the Scenes, over and over again and found nothing that could cause this error. I even deleted the Scavenger script and all references to it in the quest stage fragments, and the error still happened. So I decided to try to open the fragment script that the CK was pointing to, but obviously most of the letters are messed up when you open it with a text editor. Still, some letters were intact, and I could see the OLD names of my functions, from before I changed them to try to make them more unque.
Again, these functions never caused any problems at first, but they're called MakeHostile and MakeFriendly, so I thought maybe they conflicted with some known type or script. The point is, the script file that the CK was complaining about seems to be bugged, or hasn't been updated to reflect what I've actually written in the fragments in the CK. I tried deleting it from the Scripts-folder in the directory, but nothing changes. As you can see, the error message is pointing to some Temp-folder in AppData, and when I open that folder it is always completely empty.
So, yeah. What do I do? Has anyone run into this before? Is there anyway I can force the CK to create a new fragment script for my quest? If no one knows any solution, I'd still be very appreciative if someone could run the file I linked to through Notepad++ or something and either send me an image or a text file or something, if possible with proper line spacing so that I can use the error message to find the source of the problem, but I really don't know what's possible. Either way, any help is much appreciated!