Commands#
Club House registers two commands. Both are restricted to players with the matching ACE (see Installation) and both work from the server console without the slash. Every change is saved and sent to all players online.
Command | ACE | What it does |
|---|---|---|
|
| Changes the warehouse layout: 0 storage, 1 empty weed lab, 2–4 weed stages 1–3, 5 cocaine lab. Stages 2–4 need layout 1 active first. |
|
| Adds or removes the exterior terrace. No arguments — each use flips it. |
From the server console or txAdmin:
clubhouseint 5 # cocaine lab
clubhouseext # toggle the terraceUsing It From Your Own Scripts#
The simplest and safest way for a drug, gang or property script to change the clubhouse is to run the command from the server. It runs with console rights, so no ACE is needed, and the change is saved and synced exactly as if an admin typed it.
-- server side: the MC finished a harvest, grow the next batch
ExecuteCommand('clubhouseint 1')
ExecuteCommand('clubhouseint 2')
-- later, move it to the next stage
ExecuteCommand('clubhouseint 3')
-- hide the terrace during a raid
ExecuteCommand('clubhouseext')
clubhouseexttoggles, it does not set. Readmap_state.jsonwithLoadResourceFile('qs_clubhouse', 'map_state.json')first if your script needs to know whether the terrace is currently on.
Events#
The resource uses these network events internally. You can listen to them, or trigger the client ones for a local, unsaved preview.
Event | Arguments | Effect |
|---|---|---|
|
| Clears every warehouse layout and shows the given one. |
| — | Adds the terrace to the world. |
|
Entity Set Reference#
Each warehouse layout is an interior entity set on the interior at -1155.86, -1567.53, 8.02. Useful if another script toggles entity sets directly.
Number | Entity set |
|---|---|
0 |
|
1 |
|
2 |
|
3 |
|
4 |
The terrace is the IPL jge_clubhouse_ext.


