as noted in the tagging, I don’t restrict the debate on adv3Lite, so JJmcC can contribuite (in his redoubtable way) on the adv3 side
after many mulling and musing around, I’m thinking that is definitively not a bad idea having a more selective disambiguation, e.g. TAKE’s disambiguation ignores all decos, fixtures and like, OPEN takes in consideration for disambiguation only thing with the openable attribuite, GO TO (already a source of woes, as noted in another thread…)'s disambiguation looks at rooms (eventually things with, say, a “isLandmark” flag) and so on…
the usefulness still has some limits, because for example, can give an early reveal of hidden details because an attribuite flag is set, but when the dictionary synonyms & adjectives reach trinity levels, the disambiguation listing reached a depth whose can even be called pathological (we’re talking about disambiguation lists of 20+ elements, as debated elsewhere) so, I think that can be an useful addition to both adv3 and a3Lite.
I’m happy to take a look at this, but I think I’ll need a slightly clearer idea of how exactly you’d want to limit the disambiguation options. Also, I’m very close to releasing adv3Lite 2.0, and I don’t want to make any further changes until that’s done (otherwise I’ll never release it if I keep making tweaks); but I suspect that this request isn’t all that urgent, so there’ll be plenty of opportunities for me to include it in a later update if we can arrive at a workable scheme for achieving it.
OK, let’s continue in PM ?
(I suspect that my not exactly clear english has stricken again, so I’ll work toward a better explanation and, yes isn’t urgent)
oh, a suggestion box for 2.1: extending the enumeration also to suggested topic lists (I admit that I like the dialogue interface of computer RPG…)
I vaguely recall doing something of the sort for an adv3 extension a long time back, so I could probably dig out the code and see if it’s readily portable to adv3Lite. I personally didn’t much like the interface it created, but that doesn’t mean it shouldn’t be offered as an option to players who might like it.
Sure, but perhaps it’s a conversation other people would like to contribute to?
well, perhaps my considerations stemming from the comparision of your adv3’s scene extension and adv3’s scenes.t are constructive criticism, but still criticism, so perhaps is best that is discussed in private…
You actually recall well, you refer to SayQuery.zip; HyperEnum indeed seems to fit the bill…
Another reason of talking in private is explaining some important (and spoiler…) detail of the rationale behind my propension toward using a suggested topic talk system, albeit I reckon that a library must be universal, but I have no problems nor qualms in applying custom modifies
so, I guess that if we publicily discuss about porting your adv3 modules to a3Lite, perhaps we can stimulate the redoubtable creativity of jbg so aside spoilers and criticism, I agree on discussing publicily, perhaps some quickly-implemented improvement to 2.0 can stem from this debate
Sure. Except Version 2.0 is now sufficiently close to release (i.e. within the next 24 hours) that I shan’t be making any more changes to it at all other than to correct any last minute errors that come to light. Any further improvements, however quickly-implemented, will have to await a future release (I’ve already started compiling a list of things to look at, but if I don’t draw a line at what’s already there in 2.0, I fear 2.0 may never be released!).
The hyperlinking part of HyperEnum is already in adv3Lite. It looks like I forgot to add a command to allow the player to activate it - something else to add to my list!. As a game author you can activate it with the following code:
OK. so, I can hope that the enumeration part can be added to the lib late/end '24 ?
(I can nominally test thru the hyperlink part, but as yourself points out in SayQuery docs, the “buts” are significant, esp. the second (later in private on that), so the enumeration part is better (side note, the first actual deployment of the enumeration disambiguation wasn’t criticised…) )
Probably quite a bit sooner than that, unless I encounter any unexpected snags. I’m assuming version 2 will receive some feedback that may require tweaks, and I’d probably get a version 2.01 or 2.1 out in a couple of months, depending on the number, complexity and urgency of any issues that emerge,
My reservations are about the effect of switching between different kinds of command interface for different aspects of a game and the different feel that could result from clicking hyperlinks or typing numbers instead of typing words when engaged in conversation (which to me, feels different from disambiguation), but I imagine different people will have different tastes here, so it should be a matter of ensuring such features are under player control.
