According to the wiki the Ended event handler should be fired every time a mission ends and it has no special case about not firing on the server, but following the steps to reproduce you'll see that it only runs locally on the player and never on the server.
Description
Description
Details
Details
- Severity
- Major
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Category
- Scripting
Steps To Reproduce
- Create a mission with EDEN.
- On init.sqf include this:
addMissionEventHandler ["Ended", {
diag_log "ENDED";
diag_log "ENDED";
diag_log "ENDED";
}];Export mission to SP and MP.
SP test case
- Load the exported mission by using the "Scenarios" menu
- End the mission by either using the Zeus "End scenario" module, "endMission" script command or just dying.
The RPT will have the 3 "ENDED" lines.
Local MP test case
- Load the exported mission by hosting a local server by using "Host server" in the server browser.
- End the mission by either using the Zeus "End scenario" module, "endMission" script command or just dying.
The RPT will have the 3 "ENDED" lines.
Dedicated server test case
- Use TADST, dedicated server parameters, or any other tool to setup a dedicated server with the previously exported mission loaded.
- Join the server and start the mission.
- End the mission by either using the Zeus "End scenario" module, "endMission" script command or just dying.
The Server RPT will NOT have the 3 "ENDED" lines while the player WILL have those 3 lines.
Additional Information
For some reason it seems that that event in particular is never fired on the dedicated server and only runs locally on the players but there is nothing on the wiki stating that it only runs locally.
Using BIS_fnc_endMissionServer doesn't have any effect on the server output.
Adding the event handler during the mission on the server also has no effect on the output.