ED Armor applies configurable armor levels when a character wears an allowed vest drawable. The reviewed version 1.0.0 uses ESX Legacy, ox_lib and ox_inventory. Its original GitHub repository was archived on 27 April 2025, so the old invitation to open a support issue should not be read as a promise of ongoing maintenance.
Install the actual resource and inventory items
The repository contains a nested ed_armor folder with fxmanifest.lua, client, server and shared directories. Put that inner folder in your resources directory and use ensure ed_armor after its dependencies. Configuration is in shared/config.lua; the repository root is not the resource folder.
The supplied items/items.lua lists light_armor, medium_armor and heavy_armor with levels configured as 50, 75 and 100. The client matches those three item names literally. Changing nameitem in the configuration alone does not change that matching logic. Check your installed ox_inventory item-use and consumption behavior before merging the example item definitions.
Vest checks are periodic and client-side
The default vest tables allow drawable 1 in clothing component 9 for male and female peds. Match these numbers to your clothing pack; a visible vest is not automatically accepted. Applying armor runs a five-second cancellable progress circle, then sets the armor level rather than adding points to the existing value.
Monitoring defaults to one-minute intervals and starts only under the conditions implemented by the client. At spawn or resource start, existing armor without a compatible vest does not start the monitor. The cached ped and sex are refreshed on those two events, so test character-model changes and armor supplied by other scripts instead of assuming continuous coverage.
Item handling and review scope
Armor is applied locally before the client requests item removal. The server checks that an ESX player exists, but does not restrict the submitted item name to the three armor items or check the removal result. Confirm that one successful use consumes exactly one item, while cancellation and rejection consume none, and review authoritative ownership checks before deployment.
Source checked on 10 September 2026 at revision 428fddfd5a79128cdfeaab44baa5d074a0775f47. Manifest, configuration, item examples and complete Lua code were inspected. No clothing, inventory or gameplay test was performed; performance improvements are not established.