Toolset gives me errors

[Legacy_Who said that I]

               okay, now here is my problem:

I was working on scripts from the Shayan subrace engine and suddenly my toolset gives me all kinds of errors....
Now everything I do is an complete ERROR

I think that my toolset is bugged....anything I can do to fix this issue?
               
               

               
            

[Legacy_olivier leroux]

               It happens, sadly. Did you close the toolset afterwards and still get the error messages after you re-started it? If so, I have no clue what to do, sorry.

If not, close the toolset (in the worst case with your Windows (?) abort keys), DON'T save your module and when you re-start the toolset and it asks to restore your module DECLINE! Restoring your module often leads to it being corrupted. Simply load your last save state and remember to save often and pray it doesn't happen again so soon.
               
               

               

                     Modifié par olivier leroux, 16 novembre 2010 - 01:25 .
                     
                  

            

[Legacy_Balduvard]

               If you are getting these errors on compile, it could be a module size issue. If you go into your Options and disable "compile scripts on save" under the scripting section and it solves the problem, then you'll just have to use an external compiler to compile your script changes prior to saving your module.



If, as olivier mentions, you have recovered your module or had toolset crash on you in some way in the past that corrupted part of your module (the latter usually only occurring if it crashes while in the process of saving), then module corruption can result in many error messages as well.
               
               

               
            

[Legacy_Badwater]

               I save my module frequently. The backup copy cannot be relied upon for recovery from an error.

I save a rar copy of my latest known good module. I've had times where both the module and the backup became corrupted and losing 1 or 3 hours of work is preferable to days and days of building because one did not have a backup.

I've had scripting work like this go up in smoke because the toolset decided to crash, and then the module is no good. It's happened to anyone that has a server of any size. If you're diligent about saving and backing up, you can limit your losses.
               
               

               
            

[Legacy_Badwater]

               I should also mention that I save a monthly rar copy of our module, as well. That way, if I need to backtrack however many years ago to retrieve or go over something, I can do that. '>