How to use #include in a description.ext

[Mr.Peanut]

No. Why the idea? Never tested?

Why the idea? Because in addons I have looked at paths start with a backslash. You may have noticed also that my comment ended with a question mark. This was to indicate that it was a question.

My next statement will not end with a question mark because it is not a question. text deleted

[faguss]

Because in addons I have looked at paths start with a backslash.

Then I guess you were checking addons for the wrong game because in OFP if you'll start include path with backslash then the game will crash.

text deleted

[Mr.Peanut]

Not an addon for the wrong game, but extrapolating from the path required for everything else in addons, but now obviously excluding include statement paths.  Hence the question mark at the end of my original comment.
text deleted

[bedges]

Okay gents, this thread has fallen below OFPEC's usual standard. Please drop the bickering tone, and stay on topic.

[dr. seltsam]

is there a reason it has to be in the mission?

No, i only want to make an easy to use script module. I don´t want to force the mission designer to merge different description.ext

I was able to use the #include statement this way:

Code: [Select]

#include "Users\myName\missions\Demo_Zombie.Intro\Zombie\Zombie_Config.hpp"
... This works in the editor, and.. after i exported the mission to multiplayer (it was in the folder MPMissions then) it still worked !!! Very nice. My guess is that it will also work on a dedicated server then. So the preprocessing of the description.ext is done when i load a mission into the editor?

Well.. the drawback is.. i cannot have class cfgSounds or class rscTitles twice. I can have it in the Zombie_Config.hpp or in the main description.ext

I may think about the suggestion of haroon1992... but it is only a mission script, and it doesn´t need to become more difficult as it is by now...

[Walter_E_Kurtz]

I feel you still ought to double-check by either deleting or renaming the un-exported version.

Yes, pre-processing of description.ext is performed on loading the mission in the editor and only on loading - if you make any changes to description.ext you have to re-load to see them, you cannot just preview.

[haroon1992]

if you make any changes to description.ext you have to re-load to see them, you cannot just preview.

For me, I just "Save" the game to make the game reconize the changes in the description.ext.
And its a better and safer way, in case you've done something stupid in the description.ext and the game has crashed.


Regards,
Haroon1992

[Mr.Peanut]

I am forever indebted to this thread and Faguss' answers. Helped me solve a broken addon cross-dependency on a linux ded server.