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, the asset will be delivered directly to your Keymaster. 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-deathscreen

Essential

ESX

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)

117B

exports.lua

QBCORE

You must delete any other death screens you have.

ESX default

In qb-ambulancejob, navigate to qb-ambulancejob/client/dead.lua.

You need to remove the following lines from dead.lua, related to the laststand event:

(note that this may vary depending on your version): We offer a fixed dead.lua file below if you prefer not to edit it yourself.

if LaststandTime > Config.MinimumRevive then
    DrawTxt(0.94, 1.44, 1.0, 1.0, 0.6, Lang:t('info.bleed_out', { time = math.ceil(LaststandTime) }), 255, 255, 255, 255)
else
    DrawTxt(0.845, 1.44, 1.0, 1.0, 0.6, Lang:t('info.bleed_out_help', { time = math.ceil(LaststandTime) }), 255, 255, 255, 255)
    if not emsNotified then
        DrawTxt(0.91, 1.40, 1.0, 1.0, 0.6, Lang:t('info.request_help'), 255, 255, 255, 255)
    else
        DrawTxt(0.90, 1.40, 1.0, 1.0, 0.6, Lang:t('info.help_requested'), 255, 255, 255, 255)
    end

    if IsControlJustPressed(0, 47) and not emsNotified then
        TriggerServerEvent('hospital:server:ambulanceAlert', Lang:t('info.civ_down'))
        emsNotified = true
    end
end

10KB

dead.lua

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.