Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
OPEN  Bug report #1524  -  10x Lord Inut Potions
Posted Jan 21, 2021 - updated Jun 04, 2021   Shortlink: http://arx.vg/1524
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
Issue details
  • Type of issue
    Bug report
  • Status
     
    New
  • Assigned to
    Not assigned to anyone
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     Guest user
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Not determined
  • Resolution
    Not determined
  • Priority
    Not determined
  • Reproducability
    Always
  • Severity
    Not determined
  • Targetted for
    icon_milestones.png Not determined
  • OS
    icon_customdatatype.png Not determined
  • Architecture
    icon_customdatatype.png Not determined
  • Fixed in
    icon_customdatatype.png Not determined
Issue description
While doing Lord Inut's quest, I did encounter an interesting bug. When crafting the cure for Inut, if you use a bottle from a stack(10 bottles) on cauldron, then 10 of them will have this effect. In the end, when you apply those 10 bottles(split before use) on Lord Inut, it will allow you to get 20,000 EXP per bottle.

Screenshots:

Bottles: https://cdn.discordapp.com/attachments/693291735014572052/801924539524972544/unknown.png

EXP with Ridiculous (from zero): https://cdn.discordapp.com/attachments/693291735014572052/801926070197682206/unknown.png

Steps to reproduce this issue
1. Use 10x Stack Bottle of Water on cauldron

2. Use 10x Stack Lord Inut potion to Lord Inut

#2
icon_reply.pngReply
Comment posted by
 Daniel Scharrer
Jun 04, 20:23
This is a scripting bug: Instead of replacing the water bottle with another entity (which would only replace one of the stack), the scrip ends up setting a variable on the water bottle stack and changes the description to description_potion_strange.

We could work around / support this without script fixes by always unstacking when combining and then re-stack afterwards if the item is still the same. Or alternatively we could unstack when a script tries to modify a stacked item. To me it makes sense to pretend that they are individual entities wherever possible (like is already done for eatme and replaceme) and tread the stacking only as a usability/perf optimization.

Do we know if there are any cases where stacked items should all be modified at once - ie where something like this is the expected behavior?