This a list of the things I've identified that are missing in order to enable a proper 3DEN multiplayer mod.
**Need:**
1.1 3DEN event handler that triggers when an entity's attributes change and are confirmed/saved.
Basically the already existing object [[ https://community.bistudio.com/wiki/Arma_3:_Eden_Editor_Event_Handlers#AttributesChanged3DEN | AttributesChanged3DEN]] but then editor wide for all entities (object, group, trigger, logic, waypoint, marker, layer, comment).
```add3DENEventHandler ["OnEntityAttibutesChanged", {
params ["_entity"]; // either Eden Entity or Eden ID
}];```
1.2 #DEN event handler that triggers when an entity's layer changes.
```add3DENEventHandler ["OnEntityLayerChanged", {
params ["_entity", "_newLayerId", "_oldLayerId"];
}];```
1.3 3DEN event handler that triggers when a context menu action is used/pressed (triggers before action happens):
```add3DENEventHandler ["OnContextMenuAction", {
params ["_name"]; // entry config name i.e. configFile >> "Display3DEN" >> "ContextMenu" >> "Items" >> _name
}];```
This is the more future proof out of two solutions, the other being, that I only found 6 problematic context menu actions which could be fixed by:
Adding a scripted event handler to `BIS_fnc_3DENEntityMenu` that includes `_mode`.
Move to formation, snap to surface, orient to terrain normal and orient to sea normal should all trigger an AttributesChanged event. (should be fixed either way :P)
1.4 Command to load or start a new 3DEN scenario, I imagine something like:
Syntax: `load3DENScenario missionPath` where `missionPath` is the relative path to the mission's folder from the current profile directory. Returns bool based on success.
When instead of a valid mission path a valid [[ https://community.bistudio.com/wiki/worldName | world name ]] is specified it creates a new scenario:
Examples:
`load3DENScenario "missions\test.VR"` Loads the mission: "C:\Users\Username\Documents\Arma 3\missions\test.VR".
`load3DENScenario "mpmissions\specialOps\test.VR"` Loads the mission: "C:\Users\Username\Documents\Arma 3\mpmissions\specialOps\test.VR".
`load3DENScenario "VR"` Creates an new VR scenario.
**Nice To Have:** //(ordered from most to least wanted)//
These are more of a Hail Mary, any of these would be a nice bonus but don't in anyway impede the core functionality if not taken on board.
2.1 3DEN event handler that triggers when an entity is dragged, triggers for everything except layers.
Basically the already existing object [[ https://community.bistudio.com/wiki/Arma_3:_Eden_Editor_Event_Handlers#Dragged3DEN | Dragged3DEN ]] but then editor wide for all entities except layers (object, group, trigger, logic, waypoint, marker, comment).
```add3DENEventHandler ["OnEntityDragged", {
params ["_entity"];
}];```
Why: this one I'm honestly kinda iffy about since Dragged3DEN already works for object and logic (you can add to triggers but it doesn't trigger) and the rest would still properly update if 1.1 (OnEntityAttibutesChanged) is added. However I think it be better to have around than to not have around.
2.2 3DEN event handler that triggers before mission preview is launched, and if it returns true prevents the mission preview from happening.
```add3DENEventHandler ["PreMissionPreview", {
params ["_isMp"]; // true if about to start MP preview
true // Prevent mission preview from happening
}];```
Instead passing an `_isMp` could add [[ https://community.bistudio.com/wiki/Eden_Editor:_Actions | action state ]] to MissionPreview, MissionPreviewBriefing and MissionPreviewMP.
Why: I'd use this to both prevent accidental mission previews and to have players automatically join the hosts server when they start an MP preview.
2.3 3DEN OnEntityCreated event; existing ticket: https://feedback.bistudio.com/T170168 (Maybe call it OnCreatedUnits to stay consistent with naming of [[ https://community.bistudio.com/wiki/Arma_3:_Eden_Editor_Event_Handlers#OnDeleteUnits | OnDeleteUnits]]? )
2.4 Update 3DEN OnDeleteUnits event to include deleted entity and trigger just before the entity is deleted.
Why: right now I have to detect entity creation and deletion by using [[ https://community.bistudio.com/wiki/all3DENEntities | all3DENEntities ]] and have their ID which is quite slow.
2.5 Show chat in Multiplayer 3DEN (to allow `systemChat` debugging but also to later maybe add a chat system)
Why: to allow `systemChat` debugging but also to later maybe add a chat system
2.6 Commands to get all entity/mission attributes in a given category, something like:
Syntax: `entity get3DENAttributes category` and `section get3DENMissionAttributes category`, return name value pairs: `[[name1, value1], [name2, value2]]` (or maybe hashMap?)
Examples:
`player get3DENAttributes ""` Gets all attributes from player unit
`player get3DENAttributes "Init"` Gets all attributes from Init category, e.g: `[["Init", ""], ["Name", "CoolPlayer"]]`
`"Multiplayer" get3DENMissionAttributes ""` Gets all multiplayer mission attributes
`"Multiplayer" get3DENMissionAttributes "Type"` Gets all attributes from multiplayer Type category, e.g: `[["GameType", "TDM"], ["MinPlayers", 1], ["MaxPlayers", 16]]`
Why: would by nice QOL functionality
2.7 Command to tell entity type from Eden Entity or Eden ID, something like:
Syntax: `get3DENEntityType entity` where entity is either Eden Entity or Eden ID. Returns: `"OBJECT"`, `"GROUP"`, `"TRIGGER"`, `"LOGIC"`, `"WAYPOINT"`, `"MARKER"`, `"LAYER"`, `"COMMENT"` or `nil` (Or maybe number? Prob faster but less descriptive).
Examples:
`get3DENEntityType player` returns "OBJECT"
`get3DENEntityType group player` returns "GROUP"
`get3DENEntityType -1` returns nil
Why: would by nice QOL functionality
2.8 Allow 1.4 (`load3DENScenario`) to be used from main menu
Why: I'd use it to smoothly transition players back to the 3DEN Collab session after an MP 3DEN preview ended.