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

Scan for redundant decision triggers #111

Open
Alpinia opened this issue Mar 29, 2020 · 1 comment
Open

Scan for redundant decision triggers #111

Alpinia opened this issue Mar 29, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@Alpinia
Copy link
Contributor

Alpinia commented Mar 29, 2020

Decisions have a trigger hierarchy (allowed -> visible -> available), so any triggers on the ones before don't need to be repeated in the latter ones - the only exception being visible and target_trigger, which need to be equal to one another.
image
In the above case, the available is completely redudant, as the conditions are already being met if the decision is visible.

@Zankoas Zankoas added the enhancement New feature or request label Mar 29, 2020
@CaesarVincens
Copy link
Collaborator

It can be useful to duplicate the available triggers since those show up in the tooltip for the player, but sometimes you may not want the decision to be visible until it is also available.

For more context (perhaps for tooltips), and please correct me if I go wrong:
Allowed is a single check that tells the game whether to check this decision further. Mostly this is best done to limit decisions to certain tags.
Visible is whether to show the decision
Available is whether the decision can be taken.
These terms are used in ideas (specifically for ministers, etc.) also and tech.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants