> For the complete documentation index, see [llms.txt](https://tweak5m.gitbook.io/tweak5m-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tweak5m.gitbook.io/tweak5m-docs/noir-configuration.md).

# NOIR configuration and usage

### Choose your installation

Use any combination of the four standalone packs with one Library, or use the Collection with one Library. The Collection already contains all four bag styles.

### Configuration

Use each product's `config.lua` for its supplied options. Review framework selection, storage capacities, carry profiles and interaction settings. Use the Library configuration for shared UI/provider settings.

Keep item identifiers, metadata and storage identifiers stable after players begin using bags. Changing them can disconnect existing items from saved storage.

### Inventory weight

Bag storage has its own limits. Stored contents are not dynamically added to the bag item's weight in the player's inventory.

### Carry controls and animations

Backpacks support back wear, Hold Straps and either hand. Purses support shoulder wear and either hand. Pouches support either hand independently. Chest bags support chest wear and manual Hold Straps with male/female freemode fits. Their two pockets open while worn; they have no hand carry or ground placement.

Pouches do not need a continuous holding animation. Carry poses yield to other detected emotes and weapon actions. X cancels Hold Straps; configure `Config.CancelStrapsKey` to change or disable this behavior.

Custom emote systems may require the supplied `Config.ShouldPauseCarryAnimation(ped)` integration. Preserve the existing return behavior when adapting it.

### Props and characters

The packs include male and female freemode attachment profiles. Custom peds and clothing can need profile adjustments. Keep a copy of working values before changing offsets.

Carried props hide inside vehicles. Logging out, death and resource lifecycle changes can clear the carried state; select a carry mode again when needed.

### Admin and shop integration

Use the owning pack's documented server-side `GiveBag(playerId, itemName, metadata)` export for integrations. Read the included README for its return values. Only call it after your server-side permission or purchase checks.

The item-use export opens an existing inventory item; it is not an item-granting command. Available admin commands and permissions come from your inventory/admin resource.

### Updates

Back up the resource configuration and database. Read the new installation instructions, compare editable settings, replace the resource, then verify an existing bag and a newly granted bag. Preserve item metadata and storage data.