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.

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

Associate equipment, etc., with individual workers #45

Open
kingjon3377 opened this issue Nov 7, 2018 · 2 comments
Open

Associate equipment, etc., with individual workers #45

kingjon3377 opened this issue Nov 7, 2018 · 2 comments

Comments

@kingjon3377
Copy link
Owner

kingjon3377 commented Nov 7, 2018

While some equipment is shared by all workers in a unit, some ought to be specific to an individual worker. And animals ought to be treated similarly. We need this to be able to start on a combat simulator, and also for #31; once animals (mounts) are associated with workers, we can start deducing unit MP instead of always requiring the user to enter it.

On the other hand, sometimes multiple workers need to be associated with a singular piece of equipment, or perhaps even (in the case of something like an elephant) an individual animal.

@kingjon3377
Copy link
Owner Author

Once equipment can be associated with individual workers, we should add a check to the map-checker app to warn about equipment like uniforms being placed in a fortress.

@kingjon3377
Copy link
Owner Author

We'll also want to add the ability to move equipment onto and off of workers to the worker management app.

kingjon3377 added a commit that referenced this issue Jun 21, 2021
This includes changes to the model and to both XML and database I/O, but
nothing more.

For #45.
kingjon3377 added a commit that referenced this issue Jun 21, 2021
…ess.

The list of implement kinds that will be flagged is currently empty, but
the *code* is in place.

For #45.
kingjon3377 added a commit that referenced this issue Jun 21, 2021
We don't mention equipment because that's not likely to be useful
information in the purposes for which this app is used.

For #45.
kingjon3377 added a commit that referenced this issue Jun 21, 2021
kingjon3377 added a commit that referenced this issue Jun 21, 2021
…ore robustly.

This previously didn't include equipment at all, but because unit members were only
handled specially as an operation on the units, that never got caught.

Includes code needed (once this is being done at all) because of #45.
kingjon3377 added a commit that referenced this issue Jun 21, 2021
kingjon3377 added a commit that referenced this issue Jun 21, 2021
Everything but the tunic has a chance of not being generated for
unleveled and one-level workers.

For #45.
kingjon3377 added a commit that referenced this issue Jun 26, 2022
This includes changes to the model and to both XML and database I/O, but
nothing more.

For #45.

"Cherry-picked" (hand-ported) from
2724d5d, plus changes from its previous
commit that belonged in it.
kingjon3377 added a commit that referenced this issue Jun 26, 2022
…ess.

The list of implement kinds that will be flagged is currently empty, but
the *code* is in place.

For #45.

"Cherry-picked" (hand-ported) from
fa01e08.
kingjon3377 added a commit that referenced this issue Jun 26, 2022
We don't mention equipment because that's not likely to be useful
information in the purposes for which this app is used.

For #45.

"Cherry-picked" (hand-ported) from
5ff9487.
kingjon3377 added a commit that referenced this issue Jun 26, 2022
kingjon3377 added a commit that referenced this issue Jun 26, 2022
kingjon3377 added a commit that referenced this issue Jun 26, 2022
For #45.

"Cherry-picked" (hand-ported) from
d70855a.
kingjon3377 added a commit that referenced this issue Jun 26, 2022
kingjon3377 added a commit that referenced this issue Jun 26, 2022
…ore robustly.

This previously didn't include equipment at all, but because unit
members were only handled specially as an operation on the units, that
never got caught.

Includes code needed (once this is being done at all) because of #45.

"Cherry-picked" (hand-ported) from
1d03147.
kingjon3377 added a commit that referenced this issue Jun 26, 2022
For the new check we want for #45.

"Cherry-picked" (hand-ported) from
2193255.
kingjon3377 added a commit that referenced this issue Jun 26, 2022
… workers.

For #45.

"Cherry-picked" (hand-ported) from
5fbd0f9.
kingjon3377 added a commit that referenced this issue Jun 26, 2022
Everything but the tunic has a chance of not being generated for
unleveled and one-level workers.

For #45.

"Cherry-picked" (hand-ported) from
d81a77d.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant