weyne/dcs-retribution
1
0
Fork 0
mirror of https://github.com/dcs-retribution/dcs-retribution.git synced 2025-11-10 15:41:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Dedicated Server Guide [WIP] (markdown)

David Pierron 2020-10-21 13:28:02 +02:00
parent bd71842f7d
commit 6b62bdbf7c
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Dedicated-Server-Guide-[WIP].md

@ -1,9 +1,12 @@
There are a few additional steps and caveat to running a dcs-liberation mission on a dedicated DCS server.
I'll try and explain them, as the server manager of my squadron, and dcs-liberation contributor.
If you have any questions, comments, or think this document is incomplete or wrong, please contact me on dcs-liberation's Discord.
[VEAF]Zip.
## Preparing the server
### Modding `MissionScripting.lua`
@ -11,22 +14,29 @@ If you have any questions, comments, or think this document is incomplete or wro
Any DCS instance running dcs-liberation, be it a standalone installation or a dedicated server, must have a modified `MissionScripting.lua` in order for the LUA script to have access to the `os`, `io` and `lfs` packages.
When running on a standalone installation, usually (that is, if everything works as planned) the dcs-liberation program itself will replace the original `MissionScripting.lua` file with an edited version.
Of course, this is not possible when DCS run on a different machine, as a dedicated server.
In this case, you need to edit the file yourself.
The easiest way to do it is to replace the original file (`<dcs installation>\Scripts\MissionScripting.lua`) with the file in dcs-liberation distribution (`<dcs-liberation installation>\resources\scripts\MissionScripting.lua`).
Sometimes, you'll have an already modded file because you're using scripts that need access to specific packages.
That's alright, as long as the `os`, `io` and `lfs` packages are accessible.
To ensure this, simply be certain that these particular lines are commented out :
__Original:__
```lua
sanitizeModule('os')
sanitizeModule('io')
sanitizeModule('lfs')
```
__Commented out:__
```lua
--sanitizeModule('os')
--sanitizeModule('io')
@ -38,10 +48,14 @@ __Commented out:__
### The specific case of *slmod*
If you're using [slmod](https://github.com/mrSkortch/DCS-SLmod), you have to be extra careful.
It also has [a specific version](https://github.com/mrSkortch/DCS-SLmod/blob/master/Scripts/net/Slmodv7_5/SlmodMissionScripting.lua) of the `MissionScripting.lua` file which is used to replace DCS', and if you want the dcs-liberation script to work properly you have to edit it, too.
Go and edit this file : `<saved games>\dcs\Scripts\net\Slmodv7_5\SlmodMissionScripting.lua`.
Make sure to comment the lines mentionned in the previous section.
You should also make the modification to the original file in DCS folder (see previous section), and the caveat about updating applies to *slmod* too.
### Environment variables