At @deilann's request, divide the drop chance bonus for contributor levels in half and add a +1/level contributor bonus (subject to the subscription multiplier once implemented in private code) to drop cap.
Currently, when you put on equipment, you see the messageBought notification. There was no messageEquipped notification in the code so I've added one.
I've updated ALL locale files IN ENGLISH, following the convention already in place for using English when there is no translation (e.g., locales/pl/messages.json, locales/sv/messages.json).
When a to-do is checked off, the rewards are increased by the number of checklist items that have been completed. However as reported in https://github.com/HabitRPG/habitrpg/issues/3474, if the to-do is later un-checked, then the rewards subtracted are not being similarly increased by the number of checklist items completed. This fix will change that - the number of checklist items completed will have an equal effect on checking and unchecking a to-do.
This of course won't fix the problem of, upon unchecking, not being able to calculate the exact value of the rewards that had been given upon checking, so there will still be a discrepancy between checking and unchecking, but it will be much smaller than it is currently.
Currently, when you feed a pet enough to turn it into a mount, you see the messageAlreadyMount notification ("You already have that mount. Try feeding another pet."). This fix changes it to the messageEvolve notification ("You have tamed <%= egg %>, let's go for a ride!").
"Candycane" had the "d" left out in headSpecialCanycaneText and headSpecialCanycaneNotes. I've inserted the "d" in all places that needed it.
I've checked all locale files and none of them had that typo.
For questEggHuntCollectPlainEgg, I've pluralised the text (Plain Eggs) because that reads better in the messages it appears in (and plurals are used in questEvilSanta2CollectTracks and questEvilSanta2CollectBranches).
For questRatCompletion, I've removed "out" from this: "we let out down our guard"
Repeat https://github.com/HabitRPG/habitrpg-shared/pull/205 without conflicts.
In productivity contexts, "goals" tend to be large, long-term projects, whereas "tasks" are smaller actions, and I think "tasks" better matches HabitRPG's features.
"task" is used in Habit's code in many places. The wiki uses "tasks" rather than "goals" throughout, although admittedly that was a fairly recent change. Many players use "task" when describing habits/dailies/to-dos in the Tavern.
Tyler Renelle