Make examine_action assign multiple actions

[GuardianDll]

Is your feature request related to a problem? Please describe.

Doors have few different actions, that they can have - locked_object, locked_object_pickable and door_peephole. Alas, only one of them can be used at the furniture defintion, which means you need to manually activate a tool to perform action with it (which a lot of people don't know you can)

Solution you would like.

Make examine_action accept a range of actions you can perform with it

"examine_action": { "locked_object", "locked_object_pickable", "door_peephole" }

Describe alternatives you have considered.

No response

Additional context

No response

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Please do not bump or comment on this issue unless you are actively working on it. Stale issues, and stale issues that are closed are still considered.

[Procyonae]

Can EOCs call examine actions?

[GuardianDll]

No, and it's wrong way to resolve this issue

[Procyonae]

Why, wouldn't the EOC selector stuff would be ideal?

[GuardianDll]

EoC is a tool, not a duct tape we can apply everywhere where code doesn't work
What if someone need to make action use EoC, do they need to make EoC in EoC? What if multiple EoCs? Amount of json to support it would bloat exponentially, when the actual change is just make examine_action accept range

[Procyonae]

...what are you on about? I'm saying it would make sense to make it take an "examine_action": { "EOC_examine_action": [ "locked_object", "locked_object_pickable", "door_peephole" ] that uses the EoC selector stuff as opposed to hardcoding new selector behaviour to allow it to take a range

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Please do not bump or comment on this issue unless you are actively working on it. Stale issues, and stale issues that are closed are still considered.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Please do not bump or comment on this issue unless you are actively working on it. Stale issues, and stale issues that are closed are still considered.