Jump to content

Bug? Terminals no longer compile scripts. Ouch...


Nexusmodsaccountno2

Recommended Posts

Ok I heavily invested time into using terminals and the handy script box to get a variety of things working but for some unknown reason my terminals don't want to compile any new scripts. They are stuck on my old scripts with old message boxes that I have subsequently deleted.

 

I have put in new messages, additem scripts, created new terminals and nothing makes a new script compile, like I mentioned I can completely remove a script from a terminal, compile the empty script window and the terminal does the same thing it always did message box and all.

 

It is as if the compile button does not function anymore.

 

I have tried to search for a similar bug elsewhere but so far nothing. I am going to try reinstalling stuff and making a new mod to see if I can fix the issue but I thought someone might have encountered something like this?

 

Possible issue? I have recently started transferring scripts from fnv geck to fo3 geck so have been opening and closing both gecks often. Cannot think of anything else obvious that I did differently to cause this problem...

Link to comment
Share on other sites

You have to be getting an error when attempting to compile the script, that will leave the old script working since it can't replace it with the newly compiled script. If it keeps asking to save this is a sure fire cause. I use cipscis (outdated but can still help) and NotepadPlusPlus Syntax Highlighter to check for things I am overlooking. Geck Extender for FNV should have a separate window telling why the line or the reference causing the error. No idea about FO3 geck.

Link to comment
Share on other sites

That is the weird thing. I tested an old backup and put in a script in the terminal, no problem it works fine but I try using the same copy pasted script on the mod version with the issue, a showmessage or additem, and it keeps on using the same script I compiled before that I have deleted and replaced.

 

I would love to fix this issue with my most recent mod version but I can just use a backup and fill in all the updates I have made, annoying but doable the issue is if this recurs, if the terminals scripting box has some sort of bug I don't want to have to reenter all my updates over and over.

 

If someone has encountered this bug and can explain why it occurred it would be much appreciated.

Link to comment
Share on other sites

Try toggling "ArchiveInvalidation" off-and-on-again before testing. This (for unknown reasons) has sometimes resolved some scripting issues with altered scripts.

 

Are you testing using a "New Game" (or at least a different one which did not have the mod whose text you keep seeing) instead of a saved one? As pointed out in aghjax's reply: if your edit fails to compile, the previously compiled existing script remains intact.

 

Are you certain your copy-and-pasted script contains all the definitions of variables it uses? It doesn't depend upon inheriting any from other (e.g. quest) scripts?

 

Everything points to your altered script (even though copy-and-pasted) failing to compile. You aren't confirming that it DOES compile. That is what you need to pin down. Are you getting any error messages at all when you attempt to do so or to exit the script editor?

 

-Dubious-

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...