Beta 28c Autocompletion Changes (UPDATE : fixed in 28d)
Just issued an update to Adventuron so that verb and noun autocompletion (pressing TAB) is more aware of the context.
This update only assists with nouns associated with GET, DROP, WEAR, REMOVE and EXAMINE verbs (or synonyms).
What exactly does it do?
Verb Behaviour (Unchanged)
If you press TAB with a blank textbox, adventuron will currently suggest a number of known verbs, or if you have previously used a verb recognised by your game, it will suggest that verb (after used once).
As always, cycle through available completions by continuing to press TAB. Games will need to recompile with the new version to receive this update.
Noun Autocomplete Behaviour (Changed)
Prior Noun Autocompletion Behaviour
Adventuron's printing routines scans for nouns used by the game. These may be in the match section, or in the vocabulary section, or garnered from the objects{} section.
The prior behaviour was that pressing tab would cycle through nouns that had previously been printed by the game engine. For example, if there is a lamp inside the game, but the lamp had not previously been printed, then typing GET LA <TAB> would do nothing. If the word LAMP had already been printed by the game, then typing GET LA <TAB> would autocomplete the MP. This approach is sensible to not spoil the game, but it can lead to weird scenarios where it will complete a noun in a different location that starts with the same few letters. You can cycle through to the noun you want, but it's tiresome and it makes Adventuron seem a little bit silly.
New Noun Autocompletion Behaviour
NOTE: This update only assists with nouns associated with GET, DROP, WEAR, REMOVE and EXAMINE verbs (or synonyms). Other verbs will follow the general "active noun" approach documented in the previous section.
The new logic will check if a full verb has been provided and if one of the GET, DROP, WEAR, REMOVE or EXAMINE verbs, then it will give priortity to suggesting nouns associated with entities in particular source locations associated with the verb. For example, the GET verb will give priority to nouns associated with entities (or objects) that are inside the current location. The DROP verb will give priority to nouns associated with objects in the player inventory (players pockets). WEAR will give priority to held but unworn items. REMOVE will give priority to worn items. EXAMINE will give priority to items in the same location or in the player inventory.
DROP, WEAR and REMOVE will stop using the noun logbook altogether, the other verbs will prioritise items in the source location.
It is very common for EXAMINE to be used for nouns that are not associated with objects but rather a noun that may be in the location text, therefore the noun logbook is still useful (but as a 2nd tier suggestion).
Do you have to configure anything or change anything?
No, all you have to do is recompile with the new version to benefit from these changes.