bis_resistance error

[DUX -SH- 0]

Getting it on a mission that was re-pbo-ed. Anyone else ever seen it. I don't know what is causing it. Worked fine before the update.

[Placebo 29]

Does Avon's answer here apply?

[DUX -SH- 0]

Her answer does address the issue, up to a point. I have figured out the solution to this problem and it does not entail all that complicated procedural mess. Just put "bis_resistance" into the mission.sqm manually and resave. No need to mess with sifting thourgh all your addons trying to remember what is what before creating a new folder to edit from. You can use whatever you want, whenever you want and your creative impluses are not stymied. Just throw in the call and be done with it. Easy.

[Placebo 29]

@ Mar. 22 2005,16:29)]Just put "bis_resistance" into the mission.sqm manually and resave.

Yep that's what Avon said in the thread I linked to "they must be declared in the Mission.SQM file's Addons section(s)."

My point was mainly that a solution to this problem would have been found by searching

[DUX -SH- 0]

I know but there are so many threads on this forum now. After looking it up a couple of times it makes no sense to search for hours to find the answer. For those of us who haven't been on this board since it's inception it becomes a little rediculious to sift through everything. You have to draw the line between policy and practicality somewhere.

[Placebo 29]

Editing missions is the domain of "mission editing & scripting, searching in there for "bis_resistance" from the beginning finds 6 results, the 2nd of which is the one that had the answer that I linked to Either way your problem is solved so there's no longer a need for this thread