I was editing a mod of mine today, and out of nowhere this specific script started showing this error I've never seen before every time I tried to save/compile it.
E: 21:23:59 - spell_constants_h.nss - spell_constants_h.nss(2): Function definition missing name (while compiling spell_modal_arcarts.nss)
I have a copy of an existing script, spell_modal_arcarts, pointing to another copied script, spell_constants_h_arcarts.
Without changing anything huge inside spell_modal it suddenly just started giving that message every time I try to compile it, and odder yet it the fact that none of my scripts will export properly anymore (half of them refuse to export at all, and some will give the .nss but not the .ncs).
If I change spell_modal to point to the non-copied spell_constants the
error goes away.
I revert spell_modal back to it's old code, and the error remains. I change spell_constants to look exactly like the original, and the error remains.
I've even tried going into the file histories and reverting the two
scripts to where they were a couple days ago. Error is still there.
But I point spell_modal directly to the original and it miraculously dissappears. I've tried creating a new copy of spell_constants and it does the same thing!
If I don't point the scipt to my copy of spell_constants it won't work right, and I shouldn't have to do that anyway.
Is my toolset just spontaneously corrupted now? Do I have to re-install the toolset and recreate my mod?
Toolset Corrupted?
Débuté par
Kesaru
, mars 24 2010 01:37
Retour en haut
#2
Posté 24 mars 2010 - 06:35
Kesaru
-
- Members
- 130 messages
This is maddening. I completely uninstalled and reinstalled the toolset, then recreated the scripts from exported .nss files and the problem is still there.
I've narrowed it down though; when I delete the line "#include "ability_summon_h"" (something that has always been there), it goes away. That creates other errors though.
Another confusing thing is that the error remains even if I delete every piece of code inside the
spell_modal script past the #Include "ability_summons_h".
And to the obvious question, no, I did not alter any script with that name. Even if I had, it would have reverted when I reinstalled the whole freaking toolset.
The (2) line the error refers to looks like this;
const resource SCRIPT_SPELL_AOE_DURATION = R"spell_aoe_duration.ncs";
That's from the spell_constants script. That's what it says it's from in the error, and even if it were in spell_modal the second line in that is blocked out so it won't be read.
But if I empty out spell_constants so it's completely blank, it still says it found an error on line 2!
Any help? Seriously, this will drive me insane.
I've completely uninstalled the toolset, reinstalled it, copied back in the old scripts from a 100% stable version of my mod that did not have this issue, and still this exact script while referencing that exact other one causes this issue.
I tried renaming spell_constants, and the error remained.
I tried giving back it's old name and deleting all information from spell_constants again so it was totally blank, and the error remained.
I tried making it blank again while giving it a new name, and the error dissappears.
I try putting it's information back in, and I get the error back.
I try clearing the information back out (so it's in the exact state it was before, blank with a different name), and somehow the error remains!!
I've narrowed it down though; when I delete the line "#include "ability_summon_h"" (something that has always been there), it goes away. That creates other errors though.
Another confusing thing is that the error remains even if I delete every piece of code inside the
spell_modal script past the #Include "ability_summons_h".
And to the obvious question, no, I did not alter any script with that name. Even if I had, it would have reverted when I reinstalled the whole freaking toolset.
The (2) line the error refers to looks like this;
const resource SCRIPT_SPELL_AOE_DURATION = R"spell_aoe_duration.ncs";
That's from the spell_constants script. That's what it says it's from in the error, and even if it were in spell_modal the second line in that is blocked out so it won't be read.
But if I empty out spell_constants so it's completely blank, it still says it found an error on line 2!
Any help? Seriously, this will drive me insane.
I've completely uninstalled the toolset, reinstalled it, copied back in the old scripts from a 100% stable version of my mod that did not have this issue, and still this exact script while referencing that exact other one causes this issue.
I tried renaming spell_constants, and the error remained.
I tried giving back it's old name and deleting all information from spell_constants again so it was totally blank, and the error remained.
I tried making it blank again while giving it a new name, and the error dissappears.
I try putting it's information back in, and I get the error back.
I try clearing the information back out (so it's in the exact state it was before, blank with a different name), and somehow the error remains!!
Modifié par Kesaru, 25 mars 2010 - 12:04 .
#3
Posté 25 mars 2010 - 02:44
CID-78
-
- Members
- 1 124 messages
well the toolset is a bit flawed when it reports line 2 it can be any line 2 including the include files, so check
ability_summon_h and any includes nested in it.
ability_summon_h and any includes nested in it.
#4
Posté 25 mars 2010 - 05:23
Kesaru
-
- Members
- 130 messages
I reinstalled the toolset yet again and made absolutely sure the database was replaced through much trial and error. The issue is still there.
It's different, though. Now it just reports a "parsing variable" error on line "47", no matter what the hell I have on line 47. I've deleted half the script and it still says there's a vague error on line 47.
It's different, though. Now it just reports a "parsing variable" error on line "47", no matter what the hell I have on line 47. I've deleted half the script and it still says there's a vague error on line 47.
#5
Posté 26 mars 2010 - 05:57
Kesaru
-
- Members
- 130 messages
So as I posted on the mod's official page...
I've figured out a little more. I don't know how reinstalling the toolset fails to fix
the issue, because more and more functions keep gradually failing to
read properly when compiling.
Without changing a thing, more and more of them are getting errors.
A line that worked perfectly one day will miraculously fail to read the
next.
Kesaru wrote...
Fantastic.
The last reinstallation of the toolset broke the game itself, so I
was forced to reinstall that, which uninstalled the toolset
automatically so I had to reinstall that a third time.
Now it's back to the old error again, and similar errors are
randomly spreading to other scripts as well now.
Had fun while it lasted, but I'm thinking the toolsh** is too
screwed up for me to be physically capable of maintaining this mod
further...
Luckily it's pretty much stable, though it doesn't do nearly as much
as I'd like... just don't do anything weird with Combat Magic like
having it active before using a fade shapeshift form or whatever...
I've figured out a little more. I don't know how reinstalling the toolset fails to fix
the issue, because more and more functions keep gradually failing to
read properly when compiling.
Without changing a thing, more and more of them are getting errors.
A line that worked perfectly one day will miraculously fail to read the
next.
Modifié par Kesaru, 27 mars 2010 - 03:36 .
