chromium Posted August 23, 2021 Posted August 23, 2021 Hi, I'm aiming to have a reliable setup for a force-on-force campaign where clients should not be able to check the mission file by renaming the automatically available track once the mission end (the campaign do not use randomization: the scenery is constantly updated every mission). I already created a password system to prevent clients logging in the wrong coalition, having something that is similar to what Buddyspike employ (I'm going to share it as soon as it's tested and rock-solid reliable). But I would like to know if there are solution that could prevent bad clients to check the miz-by-track file and therefore know many info about enemy positions. I could move every single group during the mission and therefore outdate every "downloaded" info once the mission is saved, but still it not a very good solution. Is there any other solutions? Thanks. 1 Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.
Maverick87Shaka Posted September 4, 2021 Posted September 4, 2021 (edited) As far as i know, there is now way to avoid that the track .trk contains all the stuff that you put in the mission editor. What I normally do is to create just the "templates" in mission editor, and make all the spawn, routes, etc.. "dynamic" by .lua scripting. After design a mission like that, I load all the required .lua scripts directly from storage without embed it in the mission .miz file. This simple step normally prevent most of the "spoiler" if anyone try to open the trk file It's require the DCS sanitize "hack" of your server Edited September 5, 2021 by Maverick87Shaka FlighRIG => CPU: RyZen 5900x | RAM: 64GB Corsair 3000Mhz | GPU: nVIDIA RTX 4090 FE | OS Storage: SSD NVMe Samsung 850 Pro 512GB, DCS Storage: SSD NVMe Sabrent 1TB | Device: Multipurpose-UFC, VirPil T-50, TM WARTHOG Throttle, TrackHat, MFD Cougar with screen. Our Servers => [ITA] Banshee | Krasnodar - PvE | PersianConquest PvE Live Map&Stats | Syria Liberation PvE Conquest Support us on twitch subscribing with amazon prime account linked, it's free!
chromium Posted September 4, 2021 Author Posted September 4, 2021 That is not suitable for my design, that is about full persistence. AFAIK, that is the way DDCS does (or it's similar), but if there's no know solution, I'll found a different way or I'll accept the limitation Author of DSMC, mod to enable scenario persistency and save updated miz file Stable version & site: https://dsmcfordcs.wordpress.com/ Openbeta: https://github.com/Chromium18/DSMC The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.
Recommended Posts