tehdaryl Posted September 28, 2016 Share Posted September 28, 2016 Hi guys I'm decently versed in CK but very new to papyrus which i've finally had to use and i'm getting compile errors on even the simplest of fragments.my idea is to use a quest linked to the SM node increase level to track player level and set 5 globals based around the players level. So far so good i've made the globals (under "miscellaneous") but whenever I try to add them to the fragment through the property table thing i getPapyrus Compiler Version 2.8.0.4 for Fallout 4Copyright © ZeniMax Media. All rights reserved.Starting 1 compile threads for 1 files...Compiling "Fragments:Quests:QF_MUS_Trackplayerlevel_01001739"...C:\Users\Tehdaryl\AppData\Local\Temp\PapyrusTemp\Fragments\Quests\QF_MUS_Trackplayerlevel_01001739.psc(18,24): script property pMUS_Playerlevel already definedC:\Users\Tehdaryl\AppData\Local\Temp\PapyrusTemp\Fragments\Quests\QF_MUS_Trackplayerlevel_01001739.psc(18,24): script variable ::pMUS_Playerlevel_var already definedC:\Users\Tehdaryl\AppData\Local\Temp\PapyrusTemp\Fragments\Quests\QF_MUS_Trackplayerlevel_01001739.psc(18,24): script property pMUS_Playerlevel already has a get function definedNo output generated for Fragments:Quests:QF_MUS_Trackplayerlevel_01001739, compilation failed.Batch compile of 1 files finished. 0 succeeded, 1 failed.Failed on Fragments:Quests:QF_MUS_Trackplayerlevel_01001739Why is this? Is it because i already created the global under the misc tab? But other fragments are able to call previously defined globals? I've tried deleting the global from the misc tab and readding it through properties but not luck. Any help would be appreciated, and please go easy on me for my possible dumb mistake(s) Link to comment Share on other sites More sharing options...
EveningTide Posted September 28, 2016 Share Posted September 28, 2016 It's saying you already added those globals as properties to the fragments. Link to comment Share on other sites More sharing options...
tehdaryl Posted September 28, 2016 Author Share Posted September 28, 2016 Yea i was just about to say i fixed it simply by recreating the quest..Glad that's sorted.. Link to comment Share on other sites More sharing options...
Recommended Posts