Мод @BoxLoader_ACE для ARMA 3 (арма 3). Установлен на 1 серверах RiseOfServers. Ниже: серверы с модом и описание Workshop.
# BoxLoader ACE
BoxLoader ACE brings the original BoxLoader cargo system into an ACE-based interaction workflow while keeping the original BoxLoader loading behavior as intact as possible.
The goal is simple: use the proven BoxLoader cargo system, but make the player-facing controls cleaner and more consistent with ACE.
## Main Features
- ACE interaction based loading and unloading
- BoxLoader cargo racks on supported vehicles
- Precise unloading
- Master pallet support
- Pallet jack support
- Vehicle-specific BoxLoader cargo setups
- Dedicated server and Headless Client support
- Helicopter cargo rigging
- Universal helicopter Hook up interaction
- Original BoxLoader cargo assets and behavior retained where possible
## Cargo Rigging
Cargo can now be prepared for helicopter sling loading through ACE.
### How to use it
1. ACE-interact with a supported crate or cargo object.
2. Open:
**BoxLoader ACE → Rigging**
3. Collect the sling ropes.
4. Walk to the helicopter.
5. ACE-interact with the helicopter.
6. Select:
**BoxLoader ACE → Hook up**
7. Board the helicopter and climb vertically above the cargo.
8. Once enough clearance is reached, the load will attach underneath the helicopter.
Pilots can release the cargo through ACE Self Interaction.
Loose ropes can also be returned through ACE Self Interaction.
On-screen hints remain active to guide players through the process.
## Universal Helicopter Support
The **BoxLoader ACE → Hook up** interaction is available on helicopters generally and does not require the helicopter to support normal BoxLoader Vehicle-in-Vehicle cargo loading.
This means helicopters can use the rigging system without being given a hidden BoxLoader cargo rack.
## Mission Maker Rigging Controls
By default, Rigging is available on normal ammo, medical and logistics crates, as well as standard BoxLoader cargo and pallet classes.
Mission makers can manually enable Rigging on other suitable objects.
Place this in the object's Eden init field:
```sqf
this setVariable ["NUKUBU_BoxLoader_RiggingEnabled", true, true];
call nukubu_boxloader_fnc_addObjectActions;
```
This allows custom crates, mission props or other objects to use the BoxLoader ACE rigging system even if they are not normally recognized as BoxLoader cargo.
Mission makers can also disable Rigging on an object that would normally support it:
```sqf
this setVariable ["NUKUBU_BoxLoader_RiggingEnabled", false, true];
```
This gives mission makers direct control over which objects can be prepared for helicopter sling loading.
## Master Pallets
BoxLoader ACE supports loading cargo onto the original BoxLoader master pallet and then loading that complete pallet into supported vehicles.
Master pallet handling has received additional multiplayer and dedicated-server fixes to support nested Vehicle-in-Vehicle cargo.
## Dedicated Server Support
The mod contains additional handling for dedicated servers and Headless Clients, including:
- multiplayer locality handling;
- server and HC startup diagnostics;
- reduced background scripting;
- event-driven vehicle cleanup;
- dedicated-server fixes for master-pallet loading.
All machines running the mission, including Headless Clients, should load the full BoxLoader ACE mod through their normal `-mod=` launch configuration.
## Vehicle Physics
Custom proxy-mass synchronization has been removed.
BoxLoader ACE no longer manually modifies the parent vehicle's physical mass when cargo is loaded into hidden BoxLoader racks, reducing unwanted vehicle damage and physics instability.
## Original BoxLoader
This mod is built around the original BoxLoader system.
Where possible, the original BoxLoader cargo behavior, models and Vehicle-in-Vehicle handling are preserved, with ACE used primarily as the player interaction layer.
## Current Status
BoxLoader ACE is still under active development and testing.
Dedicated-server testing, large multiplayer sessions and unusual modded vehicles may still expose edge cases.
If you find a problem, please include:
- the vehicle or cargo classname;
- whether the issue happened locally or on a dedicated server;
- whether Headless Clients were active;
- relevant RPT errors if available.