With the introduction of custom items, it would be great, if their name is used in chat messages.
There is already a placeholder for this: ITEM_ASSET_NAME
But
This isn't used much within the asset definitions
it would refer to the asset's name, as it is shown in the wardrobe, so we would see unmotivated capital letters in the chat messages all of a sudden
articles (a/ an/ the) are not supported. So they are either left out or probably wrong, if we go with a general approach
The idea to solve this would be to introduce two optional parameters to the asset definition:
chatGeneric and chatSpecific, for instance:
name: { wardrobe: "Armbinder", chatGeneric: "an armbinder", chatSpecific: "the armbinder", ... }
If left blank, "a/ an" and "the" would be generated by Pandora and used in the chat message. For custom item names, it would be the same, so the item creator can omit articles or change them at their will or let Pandora do the work, for example:
name: {
wardrobe: "Clare's present",
chatGeneric: "a wrapped gift",
chatConcrete: "the present",
...
}
With the introduction of custom items, it would be great, if their name is used in chat messages. There is already a placeholder for this: ITEM_ASSET_NAME But
The idea to solve this would be to introduce two optional parameters to the asset definition:
chatGeneric
andchatSpecific
, for instance:name: { wardrobe: "Armbinder", chatGeneric: "an armbinder", chatSpecific: "the armbinder", ... }
If left blank, "a/ an" and "the" would be generated by Pandora and used in the chat message. For custom item names, it would be the same, so the item creator can omit articles or change them at their will or let Pandora do the work, for example: