put a lua file inside the .miz file...

Hello,

I probably already asked this in the past. I'm able to save custom .lua files inside the .miz archive by script using DAWS, but those file are deleted once I open the miz file into the mission editor and then press the save button. I think that there is a "check" or something that allow the presence only of files that are also loaded by a trigger.

Is there a way to got my custom files to be retained inside the miz archive?

This could be a very important step for me to go on in the dynamic ground war project.

thanks!

PS

I don't care about saving the files somewhere else: I need them inside the miz archive.

Could you put it on a trigger with a condition that will never be true as a do script action? Probably any lua not referred to by something in the mission gets scraped off by the editor when you open it.

negative, cause I would have to create a custom trigger by script, which 1) is a mess 2) I don't want that to be accessible by mission designer.

Anyway I believe that there is something that remove "unnecessary" files like you said.

Ah ok sorry. Only other thing maybe at a long shot would be something like here https://forums.eagle.ru/showthread.php?t=178895 where call back is used to load an lua at mission startup. Still probably not what you want though by the sound of it.

I already use a GameGUI file for the DAWS Code (version 2.x.x). But what I need is this:

Me, that have DAWS, created a mission that work as a campaign. Inside the miz file you will have some .lua file which are the campaign informations tables with the "current" situation ongoing. I send the file to someone else which do NOT have DAWS. He play the mission, nothing happen campaignwise (the file is not updated as DAWS isn't there). Anyone of us send the .miz file to a third person who load on a server which use DAWS. The DAWS code of this third people should be able to use the custom .lua code that is inside the .miz archive.

I want it to work as it is, no setup or mission designer required, as all DAWS code is. And the only thing I think should be done is to put those lua files inside the .miz archive.

Probably there are rules that "acknowledge" certain files to be there, else even the dictionary file would be deleted. I only need to understand which are those rules.

any possibile solution yet? :)

thanks anyway

negative, cause I would have to create a custom trigger by script, which 1) is a mess 2) I don't want that to be accessible by mission designer.

 

Anyway I believe that there is something that remove "unnecessary" files like you said.

As long as the LUA file that you are including (which it sounds like) is the same filename all the time then this is the way to go. You do it once and that is it. Your users don't need to edit the mission. This is the same way people use to include sound files that are not used within the mission editor but used within a running script. Those sound files are deleted if they are not referenced by a trigger that is never actually fired. As long as it is referenced it won't be deleted. Same with a .lua file.

I need to put those file in whitout any references in the trigger. I can't understand if you are trying to explain how to do that. Where I can write the file reference?

I need to put those file in whitout any references in the trigger. I can't understand if you are trying to explain how to do that. Where I can write the file reference?

I am trying to understand why you can't have it defined in a trigger ahead of time. If it is a dynamically generated LUA filename you have to include then I can see why. But it doesn't sound that way.

Because It's not a single mission. It's a mod, that I want to be applicable anytime anywhere whitout having to set up triggers or else, and it should work in any mission used.