Goldwater wrote:On Saturday I answered two issues back to back that seemed to conflict with one another.
Following the advice of Mod Ransium here I thought I'd pass along the conflict.
First, I think I answered issue #224 which involved deciding whether or not to create a minimum wage. Then the very next issue I came to was issue #30 that had an option to abolish the minimum wage. And before you ask, in the first issue I chose option 3 which did not create an artificial price floor on labor, but issue #30 was already queued before I even answered the issue. So it wasn't that my response from issue #224 made me valid for #30.
I think the last option on #30 should not be valid for the nations for which #224 is valid.
Yes, I can see where our backstage records demonstrate that you answered #224.3 (to refuse to pay a living wage) and then #30.3 (to not invest in manufacture, get rid of import tariffs and let the market sort itself out), on the 12
TH.
I don't see conflict between those two options; it's very possible that the same leader who refuses to invest in manufacturing will be the same leader who slashes minimum wage. However, we accept that sometimes, conflict
can occur within issues. Often it occurs when two previously valid issues are dropped into a players' inbox and one becomes invalid with the answer of the first.
There's not much that can be done about that, save to dismiss the issue that doesn't work with your narrative.
It's worth pointing out here that not every outcome that can occur in an issue is tracked as a policy (although an ever-increasing number are). This can cause conflicts to occur, and preventing this is one of the main causes of new policies being added. So we welcome you to continue to raise any apparent conflicts so we can check them out.
Trotterdam wrote:Candlewhisper Archive wrote:Re: effect line #986, it was simply a double-space instead of a single-space at the start of the effect line. Now fixed.
#977 option 3 also has this.
Turns out there
was a bug in the code I had to catch these. The library function that I used to parse character entities ("Dàguó", etc.) also mangled spaces. Now fixed, so I'll be able to report future cases as they happen. (Probably not past ones, though - I had to turn that feature off due to too many false alarms resulting from trailing spaces in custom fields.)
Fixed. Thanks.