huhh, interesting how would that be possible?

anyways, changed the component match search, it should find engines in 1.17.

Does anyone have such a problem or is it just me.?

i have just upped 1.18 which auto recovers from 2.6 to 3.x versions. tested with old 2.6 save and didn't get errors. regarding the no-shooting issues, i really have no clue as this script is not doing anything that could prevent it. perhaps it's related to some other issues?

I will do some more checks.

upgrade from 2.6 in 1.18 will need a fix. hopefully Soon.

ok, 1.19 fixed. basically what happened in my 2.6 save when i loded to 3.0 one ship lost its blackboard variable (not sure how, but become null), so had to add checks not only to check the existance of the variable, but also to it's being zone class... the magic of X-Scripting. wihtout that it was constant spam (returning to zone null)

Do it for 2.60 and 3.0.

https://www.egosoft.com:8444/confluence/pages/viewpage.action?pageId=39387176

I seem to have found the problem. A couple more tests.

I have found a reason. MRS has nothing to do with it.

thanks!