en-properties

en-properties lets survivors build their own bases. Use a building plan item to open the build menu and plant a Base Flag. The flag claims the ground within 35 m for you, or for your group if you're a group officer or leader. Inside that territory, only members can build walls, gates, storage crates and utility props such as a workbench, campfire, generator or work light. Placement uses a ghost preview with rotation and wall snapping.

Building costs materials, and so does upkeep. You pay upkeep in days at the flag, scaled by the size of the base, and an unpaid base decays every day.

Other players can raid a base. They can pry walls and doors apart with a crowbar (loud, and it draws zombies), force storage crates open, or plant breach charges that explode after a fuse. Destroying the flag abandons the base: its storage opens to anyone, and a new flag planted there takes it over.

Pieces are client-side local objects, so a base uses no networked entities.

#At a glance

#How it works

#Planting a flag

To plant a flag you need the plan item and must be placing within 9 m of yourself. The spot can't be in a no-build zone or inside claimed territory, and it must be at least 90 m from other flags. You must also be under the per-character or per-group base limit, and you pay the flag's cost.

A blank name defaults to "<Character name>'s Camp". New bases start with startingDays of upkeep. Planting inside an abandoned base's territory takes that base over.

#Membership

The owner's character, or anyone in the owning group, is a member. Members can:

• build pieces (each one awards 2 crafting XP)
• repair pieces for 25% of their build cost
• take pieces down for half the materials back (the flag must be the last piece, and removing it deletes the base)
• set a numeric door code of up to 8 digits
• open storage
• pay upkeep at the flag, up to maxDays ahead
• rename the base (3–40 characters)

#Doors

Members open gates freely. So does anyone, once a base is abandoned. Outsiders need the door code, if one is set.

#Storage

Storage pieces are en-inventory stashes with the id en-properties:<pieceId>. The piece's stash block sets the grid size and weight.

#Upkeep and decay

Daily upkeep is the cost list multiplied by ceil(pieces / blockSize), with a minimum of one block. Decay is checked hourly. For each whole overdue day, every piece loses maxHealth * decay. A piece at 0 health is destroyed, and destroying the flag abandons the base.

#Raiding

Teardown and forcing make noise that attracts zombies. A destroyed storage piece spills: its stash stays open to anyone for 10 minutes before it is removed. With offlineProtection on, a base can't be damaged while none of its members are online.

#Streaming

The server sends bases to players within 260 m and removes them beyond 320 m. Clients spawn piece objects within 180 m.

#Placement controls

#Configuration

#Piece fields

Default pieces:

#Adding pieces

Any GTA prop can be a piece. This example adds a sturdier sandbag wall and a larger crate:

Config.pieces.wall_sandbag_heavy = {
    label = 'Double Sandbag Wall', category = 'walls', model = 'prop_mb_sandblock_02', health = 2600, snap = 'wall',
    description = 'Two layers deep. Takes a lot of prying.',
    cost = { { item = 'cloth', count = 16 }, { item = 'scrapmetal', count = 6 } },
}

Config.pieces.supply_cache = {
    label = 'Supply Cache', category = 'storage', model = 'prop_mil_crate_01', health = 1400, role = 'storage',
    description = 'A reinforced crate for the good stuff.',
    cost = { { item = 'scrapmetal', count = 24 }, { item = 'duct_tape', count = 2 } },
    stash = { width = 10, height = 8, maxWeight = 250.0 },
}

#Exports

#Server

A public piece is { id, baseId, kind, x, y, z, heading, health, maxHealth, open, coded, forced }.

#Client

#Commands

#Events

Server-local events:

#Database

Storage contents are stored by en-inventory under stash id en-properties:<pieceId>.

#Examples

Block a custom placeable item inside other players' bases:

-- server
local base = exports['en-properties']:GetBaseAt(GetEntityCoords(GetPlayerPed(source)))

if base and not exports['en-properties']:IsBaseMember(source, base.id) then
    return false, 'You can\'t set that up in someone else\'s base.'
end

Let your own explosive damage base pieces:

-- server
AddEventHandler('mymortar:server:impact', function(pieceIds)
    for _, pieceId in ipairs(pieceIds) do
        exports['en-properties']:DamagePiece(pieceId, 400)
    end
end)

Announce raids to the owning group:

AddEventHandler('en-properties:server:breached', function(source, baseId, coords)
    local base = exports['en-properties']:GetBase(baseId)
    print(('%s is under attack at %.0f, %.0f'):format(base and base.name or baseId, coords.x, coords.y))
end)

#Related

• en-crafting
• en-inventory
• Groups
• en-zombies