Prevent multiplayer mission trk script sharing

[philstyle]

Is there a way to prevent clients from downloading the "l10n" folder containing mission images and scripts when they join a server?

 

 

It thought this used to be possible or even default?

[Maverick87Shaka]

Is there a way to prevent clients from downloading the "l10n" folder containing mission images and scripts when they join a server?

 

 

It thought this used to be possible or even default?

It's not possible, the client on connection download the entire .miz file content.

Even if it's not recommended ( especially if you use your server also for RUN third person mission ) you can "hack" you server installation, and take something outside your mission file, typical used to take the scripts outside. I don't think the same tricks can be used to store outside images and all other contents of l10n folder.

BTW on clean and standard installation, you can't do it since this "function" is disabled for security reason by ED.

Edited March 12, 2020 by Maverick87Shaka

[=475FG= Dawger]

Is there a way to prevent clients from downloading the "l10n" folder containing mission images and scripts when they join a server?

 

 

It thought this used to be possible or even default?

 

What is your motivation here?

 

Sharing and modifying missions is part of the community.

 

One of the features I really like is the ability to crack a track file of a mission and modify it to suit my needs.

[Grimes]

For better or worse it is possible for scripts. You make a do script with a dofile() call and point to wherever the script is on your computer. Just realize it has to be an actual location otherwise it can error out if not found.

[=475FG= Dawger]

For better or worse it is possible for scripts. You make a do script with a dofile() call and point to wherever the script is on your computer. Just realize it has to be an actual location otherwise it can error out if not found.

 

You can also encrypt the contents of the miz. Easier and more reliable than dynamic file calls.

 

Not that I recommend either. Sharing your end product should be the goal considering all the work that folks put into the tools we have access to and the help we provide each other free of charge.

[Pikey]

I've found most of the things I've shared over the years, people improved on, and the rest, people just wanted to know how they could change it so it worked the way they wanted it. I've never seen anything that original or decent that wasn't shared already.

 

 

Having said that, for our server we do call the files off the network, because it's easier to change them and share on a dev box. One mess up and you can change it in flight and the next reboot its done, whereas embedded scripts require repacking them and cannot be done to a live server whilst running, requiring downtime at the reboot or stopping it completely, neithe rof which you want to do from a phone when you are out. I could easily precompile and pack them to keep idiots away, but I find people ignore it more if you actually put it up on Github. Go figure.

 

 

There's nothing worth hiding these days. Fame and fortune is for the greedy.

[philstyle]

What is your motivation here?

 

 

The motivtion is to prevent players taking the mission offline, learning where all the targets are and how the scripts are workig the mission, then jumping back online an using that info to game the mission/ get ann unfair advantage

[Maverick87Shaka]

The motivtion is to prevent players taking the mission offline, learning where all the targets are and how the scripts are workig the mission, then jumping back online an using that info to game the mission/ get ann unfair advantage

I got your point ..... and I think everyone is free enough to do what they prefer. I'm not going to spend time on what could be nice and bla bla bla.....

BTW..... you can take out all the scripts, making the mission "inoperative" if palyers try to run it, if you've done a lot of things by scripts.

But you can't stop people from opening the .trk file and seeing (if you did it within Mission Editor) all the plane template, all the trigger zone, all the unit used to create a polygonal area with moose, see hidden vehicles etc.. etc...

From this point of you, unless you move everything outside mission editor using for everyting Vec2/3 and bla bla bla, people can always try to get a little bit of advantage if they want to take a look to .trk

Edited March 13, 2020 by Maverick87Shaka

[=475FG= Dawger]

The motivtion is to prevent players taking the mission offline, learning where all the targets are and how the scripts are workig the mission, then jumping back online an using that info to game the mission/ get ann unfair advantage

 

Password protect your server and only give the password to people who are not jackasses.

 

If your server is open to the public, no matter what you do, people will find a way to cheat. You may as well accept that reality and decide how you want to proceed.

 

There are much easier ways right now for someone to learn the location of every unit alive on the map and hiding the mission scripting isn't going to change that.

 

For your own sanity, don't even try.

[Gnadentod]

You can also encrypt the contents of the miz. Easier and more reliable than dynamic file calls.

How would you do that so the mission still runs fine on a multiplayer server for all to join?

Edited March 13, 2020 by Der Hirte