Installation
Welcome to the Bablo Death Screen installation guide! This guide will walk you through the complete installation process for our asset. By following each step carefully, you'll ensure a smooth and hassle-free setup, provided that all instructions are followed thoroughly.
Download asset
To find the asset, you must have made the purchase using your own keymaster account. Otherwise, you can use the transfer system to move the asset to a different keymaster account.
After purchasing from our official website (opens in a new tab), the asset will be delivered directly to your Keymaster (opens in a new tab). From your panel, you can download the asset and proceed with the installation using the provided documentation.
Setup CFG
To ensure everything functions correctly when you're utilizing either the ESX framework or the QBCORE framework instead of the standalone version, it's essential to adhere to the following steps carefully. Following these guidelines will help you achieve a seamless integration and maintain optimal performance across your systems.
When setting up your server environment, it is crucial to ensure that your core scripts are initialized before any additional resources. Specifically, the core resources such as es_extended or qb-core should be started first before you introduce other elements like the bablo-deathscreen resource. This order is essential for maintaining a stable and functional environment.
-- First we will start the cores, never below
ensure es_extended or qb-core
-- Run bablo-deathscreen here
ensure bablo-deathscreenEssential
You must delete any other death screens you have.
ESX default
In esx_ambulancejob, navigate to esx_ambulancejob/client/main.lua. Find line 357 and either uncomment or delete it. It should appear as follows (note that this may vary depending on your version):
OnPlayerDeath()Next Step
To add an export in the esx_ambulancejob on the client side, navigate to the client folder. In any .lua file within this folder, add the export shown below.
We provide a fixed exports.lua that you can place directly into the client folder if you're unsure how:
exports("RemoveItemsAfterRPDeath", function()
RemoveItemsAfterRPDeath()
end)Basic Configuration
Basic Framework Configuration
The asset will function automatically if your framework is named es_extended or qb-core, as it will detect either one when started. If your framework has been renamed, you can update its name in the config.lua file. Additionally, the asset supports standalone mode for users not utilizing a framework.