Anonymous | Login | Signup for a new account | 2024-03-28 05:38 PDT |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
0010286 | Dwarf Fortress | Creatures | public | 2017-09-06 10:07 | 2017-09-06 10:07 | ||||||
Reporter | bearskie | ||||||||||
Assigned To | |||||||||||
Priority | low | Severity | minor | Reproducibility | always | ||||||
Status | new | Resolution | open | ||||||||
Platform | OS | OS Version | |||||||||
Product Version | 0.43.05 | ||||||||||
Target Version | Fixed in Version | ||||||||||
Summary | 0010286: CTAG defaults to true if !ARG not passed | ||||||||||
Description | If a creature variation does not provide the required arguments, CTAGs relating to that argument are assumed to be true. This seems rather counter-intuitive. Ideally it should be the other way around - defaulting to false if no arguments are provided, and NOT applying the CTAG. | ||||||||||
Steps To Reproduce | [CREATURE_VARIATION:TEST] [CV_ADD_CTAG:1:YES:<stuff A>] [CV_ADD_CTAG:2:NO:<stuff B>] [APPLY_CREATURE_VARIATION:TEST:HAHA] Obviously, !ARG1 is not YES, hence CTAG 1 is false and <stuff A> doesn't happen. However, despite !ARG2 not having been declared, CTAG 2 defaults to true and <stuff B> happens. | ||||||||||
Tags | No tags attached. | ||||||||||
Attached Files | |||||||||||
Issue History | |||
Date Modified | Username | Field | Change |
2017-09-06 10:07 | bearskie | New Issue |
Copyright © 2000 - 2010 MantisBT Group |