PokeNavBot / issue-tracker

Bug reports / feature tracking repository for PokeNav
https://pokenavbot.com
20 stars 4 forks source link

research-aliases #311

Open TheGerontocracy opened 5 years ago

TheGerontocracy commented 5 years ago

Is your feature request related to a problem? Please describe. The players reporting quests on my server tend to report quests in ways that are not understood by pokenav. E.g. "silver pinap x5" (not understood) instead of "5 silver pinap" (understood), or make the same kind of typos over and over "pinab" instead of "pinap". This produces unnecessary moderation work.

Describe the solution you'd like Each server can set local research aliases that pokenav goes through when a quest is reported. Each alias is mapped to a reward and a task. If the the reported quest is not found in the list of aliases, pokenav defaults to the current behavior.

Suggested commands:

1) Create new aliases, should allow for batch adding aliases. E.g. $create resarch-aliases alias, reward, task; alias, reward, task; alias, reward, task The ";" separates individual aliases. Example: $create research-aliases larvitar, Larvitar, Make 3 Excellent Throws in a row; ヨーギラス, Larvitar, Make 3 Excellent Throws in a row; hatch 5, Chansey, Hatch 5 eggs.

2) Clear all registered aliases (when new quests are released.) $clear research-aliases

Describe alternatives you've considered

Additional context This feature would move the responsability for maintaining list of synonyms for quests ("razz berries", "razz berry", "razz", etc.) to individual servers. Usefull lists of aliases could be passed on between servers, and quickly deployed when new quests are launched without the need to be centrally approved. The feature would also allow international servers to quickly roll out local translations and adaptations. Lists of usefull aliases can be passed from server to server.

Kdog0073 commented 5 years ago

A few things to add on to this:

1) ignore the term "task". I've noticed people post "spinda task", "aerodactyl task" etc.

2) minor detection of when a user inputs the task rather than the reward. Key task phrases begin with words like "use", "catch", "make", "battle", "win", "hatch", "power", "evolve", "use", "send", "trade", "transfer", "earn". If the user inputs phrases that start with these, they are talking about the task (and these words do not feasibly tie into any possible reward)

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.