Hard Light Productions Forums
Modding, Mission Design, and Coding => The Modding Workshop => Topic started by: diamondgeezer on September 11, 2002, 02:51:13 am
-
OK, here's the pitch (if I can remeber how to spell):
Much time was devoted to the crafting of a mission, and the result was both pleasing to the eye and apparently bug-free.
The problem arose when I substituted Dark's Apollo conversion for the Lokis I had been using. Now, when ever I load the mission, it pops up a pathetic error message about 'argument count is illegal in sexpression "when"', and telling me that 'when' is an illegal argument. Anyway, I have seen this error before, on a mission that had grown unstable due to its size, but this mission is neither huge nor otherwise resource-stressing. Apart fomr the error message, the mission runs fine if you hit the continue button.
I immedietely replaced the Lokis, but the error remains. Assuming the Apollo caused the bug (the ship worked fine when I made some test missions), why has hte error not disappeared?
One point that may be relavent is that the Apollo's description does not appear in the tech database, even though I have tripple-checked the tbl entry. Are these two facts indicative of some deeper problem with the Apollo (I don't think it is, since removing the tbl entry had no effect on the mission error), or is my mission simply screwed.
If the mission is screwed beyond repair, how best to salvage it? The code is otherwise fine, so what's the quickest way to transfer everything to a new mission file? And if anybody suggests redoing it from scratch, I'll cry :nod:
Standing by...
[EDIT] Just so there's no confusion, I'm not knocking Dark's work. His stuff is consistently superb, and no doubt the fault is at my end.
-
*Sesquipedalian painfully rubs temples and tries to remember*
Are there any ships that start docked with another ship or that have initial orders to dock? I had a mission do this one time, and I think in the end it turned out that the bug was related to a bunch of freighters who were either docked or docking at the start of the mission. Of course, that was most of a year ago, and I may be talking utter gibberish now.
-
Nope, nowt like that.
Continuing to standby...
-
Well, I dunno about how to undo what yuo did, but for 'salvaging' purposes... Make a new wing of fighters (or wings of fighters if it was more) and make them Loki's.
Now bounce back and forth copying data from what you have the other wings doing.
Leave sexp's alone.
After the payloads and waypoints and ai goals and whatnot are finished and identical to the other ones delete the old wings.
Rename the new wings to replace them.
This shouldn't break any sexps since they're name driven or type driven (fighter bomber cruiser) and not class (loki perseus). And any other ships who have orders to attack that wing will still have a wing to attack.
And, any chance it's not an is-iff sexp issue?
-
whats wrong with is-iff?
-
The Is-iff sexp has been buggy for the longest time.
If you search this forum you'll probably find a few different posts about mission errors and how they break down to 'is-iff' being to blame.
I don't know why, it's just screwed up.
-
Its broken...like is-tagged (I think). It may work in a very particular circumstance, but I haven't figured it out.
If worst comes to worst...remove the Loki's/Apollo's whatever...and see what happens.