As much as I'd rather not... sometimes it's possible multiple bait may be used initially. This is really only the case for non big fish though, but it may play into the mooched fish required to catch them.
As far as data formatting goes, alternative bait will be recorded in the YAML as follows:
The preferred bait should always be listed first, but alternative baits may be listed afterwards. The indentation is required. This will produce the following result:
It's not ideal, but until the YAML database is able to separate mooch bait from individual fish, having the first bait entry be an array should allow for alternative baits to be displayed.
In the UI, I would expect something like [BAIT_1] / [BAIT_2] > [MOOCH]
As much as I'd rather not... sometimes it's possible multiple bait may be used initially. This is really only the case for non big fish though, but it may play into the mooched fish required to catch them.
As far as data formatting goes, alternative bait will be recorded in the YAML as follows:
The preferred bait should always be listed first, but alternative baits may be listed afterwards. The indentation is required. This will produce the following result:
It's not ideal, but until the YAML database is able to separate mooch bait from individual fish, having the first bait entry be an array should allow for alternative baits to be displayed.
In the UI, I would expect something like [BAIT_1] / [BAIT_2] > [MOOCH]