You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, prerequisite unsatisfaction just displays a fixed, static warning, but if this was able to be specified, then the different types of conflicts could display their consequences.
In the case of the arm armor example; we could set -1 DX to Limbs: Stacked Armor as the warning instead of the current static warning, which would then show up when two items with the Arm Armor tag are both present and equipped.
The default warning remains ⚠Unsatisfied Prerequisite(s). (Possibly in order to prevent data file bloat, this could be a dropdown that can be set to either Default Warning, or Specific Warning/Label As:, however you want to call these user specified warnings).
A third type of warning could even be "Display conditional modifier" (along with highlighting the violating bits), but that's not super necessary, especially if it's difficult to do.
The text was updated successfully, but these errors were encountered:
I'd like to point out that these rules depend on the table, I am currently playing the game where you can add up to 50% of rigid armor without getting the penalty (given that whole body is 305% as per LT and LTIA), so it may raise some issues
It isn't clear to me if this custom warning is a single thing that shows if any of the prereqs fail, or if you are asking for every prereq entry to allow for a custom message. If the latter, how does that work for the various and/or combinations that can be set?
richardwilkes
changed the title
Extend prerequsite functionality to check for more types of conflicts and display custom warnings for the conflict type
Display custom warnings for the prerequisite failure
Apr 17, 2024
Custom warnings for unsatisfied prerequisites
Currently, prerequisite unsatisfaction just displays a fixed, static warning, but if this was able to be specified, then the different types of conflicts could display their consequences.
In the case of the arm armor example; we could set
-1 DX to Limbs: Stacked Armor
as the warning instead of the current static warning, which would then show up when two items with theArm Armor
tag are both present and equipped.The default warning remains
⚠Unsatisfied Prerequisite(s)
. (Possibly in order to prevent data file bloat, this could be a dropdown that can be set to eitherDefault Warning
, orSpecific Warning
/Label As:
, however you want to call these user specified warnings).A third type of warning could even be "Display conditional modifier" (along with highlighting the violating bits), but that's not super necessary, especially if it's difficult to do.
The text was updated successfully, but these errors were encountered: