first and foremost, my compliments to Eric for the excellent a3Lite parser.
But I have a situation where said parser is too good, and I’ll describe it:
I have three near-identical (singular) readable items, plus a dummy deco, whose role is in the comment in the snippets of vocab below:
// this is for suggesting to X invidually the parchments, and turning on the // lightbulb. Decoration 'three parchments; framed three; trio parchments; them' [...] Lparch: Fixture 'left parchment; framed left; parchment; it' [...] Cparch: Fixture 'central parchment; framed central centre middle; parchment; it' [...] Rparch: Fixture 'right parchment; framed right; parchment; it'
lightbulb aside (it’s a joking reference to the hint given), the adv3 rendition works as designed, X PARCHMENTS gives the suggestion and hint, and X and READ individually the parchments works as expected.
with a3Lite, its parser works too well, correctly interpreting X parchments as player’s request to examine/read all three parchments and duly outputs all four
description, and worst, ALL three readDesc (whose are three long wall of texts with some differences between them, and these differences matters, whose is why I suggest to read individually in the description of X parchments, allowing player to note the differences in the parchment’s long text)
the last week was spent around this issue, and I scoured a3Lite’s library reference manual, to no avail.
so, I need for this issue, downgrading in this specific case the unique excellence of parser, whose correctly form the plural of parchment and apply X PARCHMENTS not only to the dummy object, but also to the three singular parchments, with disastrous results in the case of READ PARCHMENTS (I have already received strong critique from testers on long wall of text… )
In other words, I’m at a loss in dealing with a feature (in an spectacular twist of the old saying about bugs and features…) whose works too well is, paraphrasing Clarke, indistinguishable from a bug…
Best regards from Italy,