The command unassignCurator appears to have no effect.
Description
Description
Details
Details
- Legacy ID
- 4279714505
- Severity
- None
- Resolution
- Not A Bug
- Reproducibility
- Always
- Category
- Scripting
Steps To Reproduce
Create a mission in which a unit is set as the owner of a curator module.
Add this into an init field or init.sqf:
{unassignCurator _x;} forEach allCurators;
Event Timeline
Comment Actions
To whoever voted against the issue:
Could you explain why? Are you able to get this command working?
Comment Actions
Seems the problem might be a bit more specific, this works:
this addAction ["Unassign Curator Module",{unassignCurator (getAssignedCuratorLogic (_this select 0))}];
Comment Actions
I wonder if it might be a multiplayer related issue as I can also get the original snippet working in the SP editor. Whereas I was testing in a MP environment before. Will try and get a consistent repro up.
Comment Actions
Figured it out, simply a case of the command being called at mission start causing it to have no effect because the curator objects presumably aren't yet assigned.
Tested using this in init of appropriate unit:
systemChat format ["AssignedCurator is %1",getAssignedCuratorLogic this];
Returns:
"AssignedCurator is <NULL-object>"
Issue can be closed unless this is unexpected behavior.