Secret Hideout

Secret Hideout is a map: a phone repair shop and, under a hatch in its technical room, a lower level of three rooms that comes in five setups. The setups are dressing, not gameplay. What the script runs is the hatch and its two levers, the switch between setups and the people working downstairs.

Requirements#

• Game build 3717 or newer. Some of the props come from recent DLCs.
• OneSync, recommended. The server uses it for two checks: that the player who pulls a lever is standing next to it, and that nobody is in the shaft when the hatch closes. Without OneSync the resource still runs, prints a warning on start and skips both checks.
• No framework and no other resources. It’s standalone.
• Built and tested on FiveM (GTA V Legacy).

Install#

1. Get the files. Owner: under Granted Assets in your Cfx.re Portal. Developer: the download link in the Tebex email.
2. Put the secret_mlo folder in your server resources. Keep that name: the export uses it.
3. Add these lines to your server.cfg and restart, or run refresh and ensure secret_mlo in the server console:

sv_enforceGameBuild 3717
ensure secret_mlo

Where it is#

The interior is smlo_hackshop. Its door is the basement door of the building in the alley, at about 2.4, -1215.1, 25.9. In the game that door is painted on the wall; this resource cuts it out of the building so you can walk in (see Conflicts with other maps).

The upper level sits just below the street, down a short stairway from the alley door: the shop, its counter and stock room, a toilet, a workshop, a storeroom and the technical room. The way down is the hatch in the technical room: it opens onto a shaft with a ladder, and at the bottom there are the three rooms of the lower level.

The resource also streams the floor plan of the interior for the radar and the pause map.

Setups#

The lower level comes in five setups. Only one shows at a time, for every player.

See all five in the video on the product page.

Each setup is an entity set of the interior (smlo_meth, smlo_coke and so on). None of them comes with a job, a drug system or a hack: that’s up to your scripts.

Pick the one it starts with#

When the resource starts, it uses the first of these that is set:

1. The convar smlo_variant, in server.cfg before ensure secret_mlo.
2. Config.Variant in config.lua, which is blackhat out of the box.

set smlo_variant meth
ensure secret_mlo

If the convar names a setup that doesn’t exist, the server says so in its console and uses Config.Variant.

Switch it live#

With the command:

smlo_variant coke

From the server console it always works. Players need the ace command.smlo_variant:

add_ace group.admin command.smlo_variant allow

Without a name, the command prints the setup in use.

From another server script, with the export:

local ok = exports.secret_mlo:setVariant('weed')

Players near the MLO reload the interior on the spot when the setup changes. Nobody needs to leave or reconnect.

Read it from your scripts#

The setup in use is in GlobalState.smlo_variant, and GlobalState.smlo_hatch is true while the hatch is open. Your scripts can read them, for instance to start a job only when the lab is there:

if GlobalState.smlo_variant == 'meth' then
    -- your code
end

Only this resource should write them.

The hatch and the levers#

There are two levers: one in the technical room, out of sight on the side of the big electrical cabinet, and one on the wall at the bottom of the shaft. Walking up to either shows a prompt, “Press E to pull the lever.” Pulling it opens or closes the hatch for everyone: the server holds its state, so all players see the same hatch. Other players see the pull too. The hatch takes about 6 seconds to move, and the ladder can be climbed once it has fully opened.

An open hatch closes by itself Config.AutoCloseSeconds after it finishes opening: 45 by default, 0 for never. With OneSync it won’t close while a player is in the shaft; it waits until the shaft is empty. A lever pulled while the hatch is moving shows “The hatch is already moving.”

Settings#

These are in config.lua, which is open in both editions:

To add a language, copy locales/en.lua to locales/<code>.lua, change Locales.en to Locales.<code>, translate the four lines and set Config.Locale to that code.

The positions of the hatch, the levers, the ladder and the shaft are in shared/mlo.lua. They belong to the interior: moving them breaks the hatch.

Who can use the levers#

server/permissions.lua holds canUse(source, lever). source is the player’s server id and lever is 1 for the one in the technical room or 2 for the one at the bottom of the shaft. Return true to let the pull through. Out of the box it lets everyone through. The file is open in both editions and has commented examples for an ace, an ESX job, a QBCore job and an ox_inventory item.

With an ace, no framework needed:

function canUse(source, lever)
    return IsPlayerAceAllowed(source, 'secret_mlo.hatch')
end

add_ace group.admin secret_mlo.hatch allow

With a keycard in ox_inventory, only to go down (anyone can open it from below):

function canUse(source, lever)
    if lever == 2 then return true end
    return exports.ox_inventory:Search(source, 'count', 'keycard') > 0
end

A refused player sees “The lever won’t move.” With OneSync, so does a player further from the lever than Config.Distance.pull.

People downstairs#

Each furnished setup has six people working on the lower level: in the hall, the middle room and the camera room, and a guard in the shaft room. Upstairs, in every setup, someone behind the counter and someone at the computer of the workshop. They exist only on each player’s own game, appear when the player comes near the MLO and go away when they leave, change with the setup, can’t be hurt and don’t react to anything. empty has nobody downstairs.

Their places are in shared/ambience.lua, open in both editions. Each group there is one scene, placed by the at of its first ped: moving it moves the people and their props together, so a group moved by hand no longer lines up with its chair or table.

Conflicts with other maps#

To make the basement door walkable, stream/ carries two of the game’s own files with that door cut out:

• sc1_00b_bld2.ydr, the building;
• lr_sc1_00b_0.ybn, its collision.

If another resource on your server also replaces either of them, only one version loads. With the other version, the door of this MLO shows painted shut or its collision blocks the way in.

To check, search your resources folder for those two file names. Keep one copy: remove them from the other resource if it doesn’t need them, or ask its author for a version without them. Both files are left unencrypted so you can swap them.

stream/int721482162.gfx is the floor plan on the radar and the pause map. Deleting it removes only that.

Debug mode#

Add this to server.cfg, before ensure secret_mlo:

setr smlo_debug 1

The server and the client then print what they do (pulls, refusals, setup changes, props created) to their consoles, and three commands become available:

Reference#