Difference between revisions of "Automated Multiplayer Updates/2019 December"

Revision as of 00:00, 5 December 2019

[Update] Nuku says, "Single-target Debug removed for direct damage, but now DoTs have debug, just to be sure it's all working."

[Update] Nuku says, "Debug complete, DoTs are now also benefitting from focused powers (that being single-target powers)."

[Update] Nuku says, "Fixed a big bug in focused DoTs that made them do ALL THE DAMAGE."

[Update] Nuku says, "Fixed a display bug in resist command."

[Update] Nuku says, "Armed with Motherly Advice and keeping a Motherly Vigil, the Den Keeper is ready to dial up those maternal instincts to 11/10! Wait, no, 40/10! As they join that club."

[Update] Nuku says, "You've already walked into their Planned Trap. Don't bother chasing them, they'll lead you to their Favored Terrain. Strategists knew they'd get into the 10/40 club today."

[Update] Nuku squeaks, "Confirmation: [line break] works fine in form descriptions."

[Update] Nuku squeaks, "Over on the dev server, trinket rewards dropped, but per-monster rewards have raised. Try it out. If I get a thumbs up, I'll port to live."

[Update] Nuku squeaks, "Fixed a bug that could have been causing some people to get way less freecred than they should have for each enemy in combat."

[Update] Nuku squeaks, "Cred from enemies in combat increased by 200%(x3). Trinket value decreased."

[Update] Late Night Coder Inutt says, "Nanomagic programs now correctly require data nanomagic instead of the non-existing program nanomagic"

[Update] Nuku squeaks, "You can now use +mako/vanity (listed in +mako) to spend 30 mako to buy 1 additional vanity point."

[Update] Nuku squeaks, "When you list perks, you will now be told how many excess vanity points you have spent."

[Update] Nuku squeaks, "You can now @ person (without the space) as many times as you do please within one channel message."

[Update] Late Night Coder Inutt says, "Zephyr's resident Zebra chef Alex has resumed baking cakes for agents on their birthdays. As a reminder, following changes in how the data is stored, if +birthday says your birthday is invalid, YOU NEED TO USE +birthday #set TO MAKE IT VALID AGAIN!"

[Update] Late Night Coder Inutt says, "Temporal anomalies have been fixed, everyone's age should now either correspond to their birthday, or their birthday will show as invalid. No more 30 year olds born in 2015... (Reminder: update your birthday!)"

[Update] Late Night Coder Inutt says, "OK, confession time: I accidentally broke everyone's birthdays. My fault entirely, but now everyone really needs to reset their birthday again, even if you already have. Really sorry about that. (+birthday #set)"