[SW3] [MOD] - The SW3.Expansion Mod - 0.5.3G

[nocalora29]

Thanks for the save file Zekito, im going to look into it asap. The combination of the save files (2) and the log is just perfect and everything I need.
This should be a example of how to do a good job sending out error reports.

EDIT: I see what the problem is. It has to do with the unconsistent GetQuestLabel variable receivement. In this case a Number has turned into a String. Which caused the game to crash while doing an arthimetric comparison.

It is easily fixed, since its a frequently executed Script it will fix itself when replaced with another file.
Download: http://www92.zippyshare.com/v/7WLjfCKG/file.html (Cant access ModDB ATM)

[Zekito]

Thank you for your quick reply and fast fix, but, it did not work. I`ve downloaded the file, extracted it, copy+pasted data folder into my main game folder, overwrote all folders and files when asked, and, tried both of my saves. In both cases it still gives the error message.

Do I need to start a new campaign, or, delete some additional file to make it work? I don`t want to start a new campaign, if not necessary.

[nocalora29]

Try to reload lua via the compatability menu, or additional try to configure the auto save plugin again.

[Zekito]

Just tried to reload lua via compatibility menu ,and it still crashes. tried to configure autosave interval, and it still crashes.

Only difference now is that it crashes inside the current system where I was prior to jumping to any other system (that is happening after reloading lua).

Do you want another fresh log file and save game?

Edit: Here is another log file along with two new saves, and, my profile files which you can use to reload my save game ( Just creat a folder named Zeki in your Profiles folder, and put inside profile.info and Zeki.cfg files). https://drive.google.com/file/d/1OoG...ew?usp=sharing

I had deleted my old Main.cfg file, and copy+pasted yours which you had uploaded, and the game does not crash while in the current system, only when I jump to any other system.

[nocalora29]

Try this: http://www70.zippyshare.com/v/0ySYntpE/file.html
I've added a new option to the ASAS Menu, try the Fix SQL Config option.

If nothing happens, try reloading LUA prior to executing the option (If you pressed on it before doing that, reload the save file)

This is pretty much the only thing left to try, other than reloading the First-Time-Configuration which may result in unknown things.

[Zekito]

It works! I`ve tried the Fix SQL Config option, and jumped to Golconda system, where I already had two crashes, and it worked.

I think the problem was the autosave interval, since at an approximate time of the previously encountered crashes, now the game autosaved successfully.

[nocalora29]

The problem was the game tried to do a number comparison with a string (which was a number prior) and a number Which results in a crash.

But im glad the fix works now. It basically resets the important SetQuestLabel config to actual numbers + Adds proper conversion from SQL to Number SQL.
Im going to update the ModDB page with the update once I can access it again.