Special K

It is an internal file that you do not have in your installation but that goes into Saved Games. At least that was the case. When MT was new, one could fine-tune stuff in there, but that was for the developers, not for the general public. Now, MT is much more advanced and stable than it was in the beginning.

I don't know where that chap got that from. I would not recommend tampering with mt.lua. It is an internal file, which is subject to change and not meant to be set by users unless advised differently by support. I can not even tell if it is a thing at all anymore. Windows seems to agressively enter eco mode on AMD for whatever reason. You can try and launch your DCS.exe with --disable-features=UseEcoQoSForBackgroundProcess and see if that fixes it.

He? I don't think you're understanding the change mate. I told people to NOT open up everything but to create a file which works for their solution. I provided one which opens the minimum for server owners, mission and server, which in fact is very secure and not the issue for the casual user anyway. The problem lies at a different place. But if you know it better, I'm all ears how you would go with the scripts that use net.dostring_in() now.

Just put it in Saved Games, that should do it.

You don't need to fix anything in your scripts. People that use it just need to amend their autoexec.cfg like people need to amend MissionScripting.lua since ages already. As said I have provided one in here, costs you 2 mins to share it.

Would need to see the script to tell. Would wonder why any slot blocker needs that. Mine does not. Look a bit up, I posted a sample that should work for 99% of all cases. Goes into Saves Games\DCS\Config

This is what the closed beta is. If it would not be easily accessible and servers would not show up, who should run that and who should play on it?

I am using exactly that in my bot, which is running on some 550 servers these days. And there is no issue at all in doing it, people just need to add the 2 lines. If your server is either using my bot or running on one of the big hosters like Fox3 or MasterArm, you are good already also. So it will affect self-hosted servers, yes, but again, just add 2 small lines and you are happy.autoexec.cfg There would be the need to do it at 2 places, because you need to either do it in the GUI for clients or in the WebGUI for servers. And yes, that is an option. We do not have this option for anything in MissionScripting.lua also since ever (which does not make it better, but just as a reference). The majority of people will just not need it at all.

No issues with MIST and Moose AFAIK. I don't know the EW script but as long as it's not passing information between Hooks and the mission, then it will not be affected. LotAtc is, DSMC, DATIS and from the looks of it DML. I'm still in contact with the Tacview guys about it, can't tell there yet.

Understood. Yeah, I fear you need to add that autoexec.cfg to the mission downloads now. At least that would be the most convenient way for people. I did my best to tell the support guys what to do if they see these errors also, they have a sample autoexec.cfg in place if a user reports it.

Yes, it puts the burden on those who developed the scripts to tell people how to run them / what to do to run them. I agree that this is not great but it is how it is now. My message was meant to the guy who seemed to be a starter in regards of DCS scripting.

So you mean you're using net.dostring_in in all possible contexts with all possible scopes? I doubt that. Unfortunately, the documentation is a thing. There's not "the" source and what we get from ED is very limited. I am on vacation rn, so I can not write up an essay about it. If you just started scripting it is quite unlikely that you need this specific API. You can use it for instance to call a function from your Hooks environment inside of the running mission. Or you can now read values from your mission from the Hooks. That can be useful for persistency frameworks, statistics etc.

But that's the same argument you could have for MissionScripting.lua. People do not just blatantly open up all gates, just because some mod might need it. It's like always, we need to get used to it. And we will.

I understand your frustration but the reality is different. It's not to add any more security for mission builders or scripters or to make the world of server admins more difficult. It's to add security to the casual DCS user that does not need any of that but that loads a mission from anywhere and runs it. These people need to be protected and that's the obligation of ED which they took responsibility of here.

Not sure how a change that adds security ruins whatever you had done as you don't even have access to where these changes were made. AFAIK you guys use my bot? At least you did in the past. If you do, all you need is make sure you're using the latest version. If you don't know what they do, you probably don't need them. For the guys that are building mods and script stuff it should be very obvious what is what. Any mod that needs to pass information between the different secure zones.