Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Track NPC crew status so we can warn if you fail to assign them #2033

Open
richardbuckle opened this issue Dec 8, 2020 · 5 comments
Open

Track NPC crew status so we can warn if you fail to assign them #2033

richardbuckle opened this issue Dec 8, 2020 · 5 comments

Comments

@richardbuckle
Copy link
Member

We currently do not track the player's NPC crew, so we cannot implement a warning, similar to the limpet check, if you are in a ship with a fighter bay but have forgotten to set the crew active.

NB the "Ship swapped" script does currently include a blanket reminder to set someone active.
@Tkael
Copy link
Member

Tkael commented Dec 9, 2020

I see two ways to accomplish this:

  1. via a variable set within a Cottle script
  2. via a variable added to the ship

Either way, we'd react to crew assignment events by updating our variable.

Do we have a preference as to the implementation method?

@richardbuckle
Copy link
Member Author

I’d favour 2 but am ruminating over whether it is a property of the ship or not.

@Tkael
Copy link
Member

Tkael commented Dec 13, 2020 •
edited
Loading

Fair. In some ways crew are more like cargo but I'm not sure we need a Crew monitor right now. ;-)

@Tkael
Copy link
Member

Tkael commented Oct 12, 2021

Consider adding a Crew check script (ref. #2271), triggered like a limpet check, to remind commanders to assign crew.

@Tkael Tkael mentioned this issue Oct 12, 2021
Closed
@richardbuckle
Copy link
Member Author

Sounds good to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@richardbuckle @Tkael