Installation
Install tc-banana_defuse: resources, arena, ped and checks.
#1. Copy the resource
Put the tc-banana_defuse folder in resources.
#2. server.cfg
After your framework (if any):
server.cfg
ensure ox_lib
ensure tc-ui
ensure tc-banana_defuse#3. Database
None. sql/install.sql contains nothing to import: the script keeps no data in the database (arena positions are in data/positions.json).
#4. Set up the map
Open config.lua and adapt to your map:
| Option | Role |
|---|---|
Config.Arenas | One arena = one possible simultaneous game. The sample coordinates (Legion Square) must be checked |
Config.Npc.coords | Access ped position (vector4, chest height: the ped is placed 0.98 lower) |
Config.Npc.model | Ped model |
Lua
Config.Arenas = {
{ label = 'Legion Square', bomb = vector3(195.0, -933.0, 30.7), heading = 0.0 },
-- { label = 'Arena 2', bomb = vector3(x, y, z), heading = 0.0 },
}
Config.Npc = {
model = 'a_m_y_hipster_01',
coords = vector4(209.0, -925.5, 30.69, 160.0),
}Place an arena in game
As staff, stand where you want it and type /banana arene [n]: arena n's bomb is placed at your position (saved in data/positions.json, effective next game).
#5. Ped per framework
- Vision: the ped is handled by the staff management (management menu → “Banana Bomb” interactions): move, change the ped, delete.
Config.Npc.coordsis only used on first start. - Other frameworks: the ped (local ped + blip) is created directly at
Config.Npc.coords, with the E key.
#6. Staff rights
- Vision: one of the
Config.Permissions. - Others:
add_ace group.admin command allow(orConfig.Bridge.Admins).
#7. Test
- Go to the ped and press E: the lobby opens.
- With 3 players (or a staff member starting it), the game begins.
- A bomb appears on a table, with three chairs.
Items
No item to create.
OneSync
A game is isolated in a routing bucket (Config.BucketBase + arena number). OneSync is recommended, and server-side distance checks are only active with it.