Page 1 of 1

startcondition otheroption doesn't like arrays

Posted: 23 January 2021, 19:30
by galehar
I have an option for which some values only work with some specific values of another option. So, it looks like this (I've simplified it, the real version is worse):

Code: Select all

'startcondition' => [
3 => ['type' => 'otheroptionisnot', 'id' => 100, 'value' => [2,3],
      'message' => totranslate('6 player draft option requires Brink of War')]
]
This doesn't work.

However, this works.

Code: Select all

'startcondition' => [
3 => ['type' => 'otheroptionisnot', 'id' => 100, 'value' => 2,
      'message' => totranslate('6 player draft option requires Brink of War')],
     ['type' => 'otheroptionisnot', 'id' => 100, 'value' => 3,
      'message' => totranslate('6 player draft option requires Brink of War')]
]
So, just to let you know that there's a workaround if you run into the same issue. Not sure how to properly report the bug though. The "web site" bug report is so flooded I doubt it can be used to manage framework issues.

Re: startcondition otheroption doesn't like arrays

Posted: 23 January 2021, 20:09
by Victoria_La
Why do you think it does support array? If it is not document - it does not, if it is ducumented - maybe you can correct it
Not all option support array of values.

Re: startcondition otheroption doesn't like arrays

Posted: 23 January 2021, 20:21
by galehar
The doc for startcondition says
otheroption conditions ensure another option is set to this given values. That works the same as in displaycondition.
And in displaycondition, it does support array. So it looks like a bug.

Re: startcondition otheroption doesn't like arrays

Posted: 24 January 2021, 22:03
by fafa-fr
galehar wrote: 23 January 2021, 19:30 The "web site" bug report is so flooded I doubt it can be used to manage framework issues.
Framework bugs or suggestions can be managed in the Studio bug report system (https://en.studio.boardgamearena.com/bugs)