Arx Libertatis Bug Tracker
Please log in to bookmark issues
CLOSED  Bug report #1522  -  Drag behavior when cooking bug
Posted Jan 15, 2021 - updated Jun 28, 2021   Shortlink:
icon_info.png This issue has been closed with status "Fixed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • Status
  • Assigned to
    Not assigned to anyone
  • Progress
  • 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
  • Priority
  • Reproducability
  • 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
Moving multiple stacked food at once into a cooking zone is breaking the items, we can't cook multiple food, the items are broken and with no interactivity after perform this, for example drag 10 ribs into the fire
Steps to reproduce this issue
Stack multiple food Drag to the cook zone Food is broken

Comment posted by
 Daniel Scharrer
Jun 05, 00:28
Hm, this isn't completely fixed by 2a3055f: if the player is close enough to the fire, the stack starts cooking while dragging.
Comment posted by
 Daniel Scharrer
Jun 07, 22:33
Dragging stacks is new but this can also be reproduced by dragging a single item:

  1. Move player close to a fire
  2. Start dragging a cookable item (e.g. fish)
  3. Drop the item back into the inventory on an empty slot
  4. Stack another item on top of it
  5. One item is cooked while the rest of the stack remains non-interactive in the inventory. We should probably not allow stacking non-interactive items or maybe not allow dropping them in inventories at all? TODO: test AF 1.21
Comment posted by
 Daniel Scharrer
Jun 28, 21:59
This has been fixed in the latest development snapshot.

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from New to Fixed.
  • The resolution has been updated, from Not determined to RESOLVED.
  • This issue's progression has been updated to 100 percent completed.