Freggel.Doe wrote:there seems to be a problem with wing commands. even though it was in my t-file, exscriptor never noticed this and always called it {COMMAND_WING_TYPE_SPECIAL_17}. the ise recognized the name in my t-file.
I apparently missed some wing command handling when I updated everything to cope with X3TC - in this case, wing commands used in expressions. It should be fixed now. While I was there I also went over the loading so it should (hopefully) load your user-defined wing command names too.
s9ilent wrote:And the script I'm loading does, but the other one (.jumpcheck) does not, and the reason why I'm trying to open it, is to rename it. Short of notepading the line I'm trying to rename, I don't suppose you can improvise a solution? (i.e. let it open any way, but just high light it red or something)
If I'm understanding the error message correctly, then it seems to be failing while checking the parameters of a script call inside your script. Is that right? If so I think I may have fixed it in the latest version (it should just ignore the check if it doesn't work). Test it with your problem scripts and let me know how you get on.
MutantDwarf wrote:I don't know why, but it still compiles if you just put {Advanced Satellite} or {SQUASH Mine}, etc.
I figured it out - those are the object classes (which means something like "SQUASH Mine" has upto three possible meanings). I've added additional text to make the distinction plain, but unfortunately there's no simple solution to this problem in general; even context-sensitive knowledge (e.g. "[THIS]->add 100 units of {SQUASH Mine}" is not talking about an object class) can be foiled if you use a variable instead. Hopefully I've managed to make everything sufficiently distinct for the time being though, at the expense of making it impossible to guess what the right name without looking.
ScRaT_GER wrote:Mh, I reinstalled the Version 3.5 (already had it installed seemingly), but the errors remain the same.
Hope you can come up with a better idea.
If not, nevermind - I can add arguments in the internal script editor aswell.
Unfortunately I haven't come up with anything better as I don't know what might be causing it. Therefore, in honour of your seemingly undiagnosable bug, I have created - just for you! -
your very own version of the Exscriptor. It's the same as V1.2.11 except the interface is deliberately spaced out a lot more. Give it a try and see what happens; also check out the error log and see if anything is in there. Finally, if you could post a screenshot of how it looks in this new version, it might also help me figure out what's going wrong, but even if I can't sort it out, hopefully it will at least be more usable for you.
For those of you without bizarre user interface bugs, the normal V1.2.11 can be found
here.