Installation and configuration
To install this Script, simply unzip the downloaded zip folder and drag and drop the loki_luftrettung folder into your resources. Then just refresh your resources and start the script. To add the script to autostart, move the script to a folder inside your resources which gets autostarted, or add ensure loki_luftrettung
to your server.cfg or an external .cfg file for starting scripts. It is not needed to install anything database related.
Down here, I will guide you through the different Config options in the config.lua file to properly setup the script.
Framework
This script needs your framework for only one single reason, checking the players job. If you did not enable the job check feature, the script is completely standalone. If you want to use a custom framework that is not ESX, QBCore or QBOX, go to the client/custom.lua
file and implement support for it. If you do run one of the previously listed frameworks, the script detects it automatically and works out of the box.
Config.Job
Whith this setting, you can restrict the interaction marker for the helipad to a specific Job. For example in this case, only players with the job ambulance
can see and interact with the marker. For this setting one of these Frameworks is required: ESX, QB-Core or QBOX. Alternatively add support for your own as stated in Framework. You can set this to nil
or false
to make the marker available for any player. If you set this to nil/false, the script does not need any framework to run.
Config.Locale
This setting is used to change the languge. Currently the translations are only used for the help text when standing in the marker. You can set this to "de"
or "en"
by default. You can also edit the locales/*.lua
files for your own translations.
Config.DefaultPosition
This setting determins, whether the helipad spawns inside or outside the hangar when starting the script. You can set this to either "inside"
, or "outside"
.
Config.InteractionKey
Config.LoopWait
This is the time assigned to waits after each run of the loop used to move the helipad in ms. A higher value means better performance since the helipads position is updated less frequently, while a lower value leads to a smoother animation. 20ms is equivalent to about every second frame at 60 fps.
Config.Marker
Config.DefaultOffset
This is the offset used when attatching the helicopter to the helipad while moving the helipad. These values are used when there is no custom value specified in Config.CustomOffsets
Config.CustomOffsets
These are custom offsets that can be used instead of the default ones, for example for models where the center of the model is not the center of the visual part. Inside the brackets goes the model name, you have to use backticks to convert the model name to the hash.
Still need help?
If you still have any questions or problems, feel free to join our discord and open a Ticket.
Last updated
Was this helpful?