Arx Libertatis Bug Tracker
Please log in to bookmark issues
CLOSED  Bug report #1435  -  Item stack exploit (go above stack limit)
Posted Mar 10, 2020 - updated Apr 01, 2020   Shortlink:
icon_info.png This issue is a duplicate of issue #1111 - "Item stack size glitch"
icon_info.png This issue has been closed with status "Not a bug" and resolution "DUPLICATE".
Issue details
  • Type of issue
    Bug report
  • Status
    Not a bug
  • Assigned to
    Not assigned to anyone
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Not determined
  • Resolution
  • Priority
    Not determined
  • 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
I was able to combine 10 blue powder in my inventory with 6 blue powder in a chest (dragging 10->6) for a total stack size of 16 blue powder. Also worked with other alchemical powders

Played on 1.2-dev-2019-07-22
Steps to reproduce this issue
Drag a pile of powder from the inventory onto another pile in a chest inventory. The chest powder must be found directly from the world (e.g. in the alchemy room in the castle) while the inventory powder must be crafted with a pestle and mortar. If they both have the same source (or perhaps if the powders have been mixed), it won't work.

Comment posted by
 Daniel Scharrer
Mar 22, 01:23
This is now fixed in the development source code and the fix will be part of the next development snapshot.

The issue was updated with the following change(s):
  • The status has been updated, from New to Not a bug.
  • This issue has been closed
  • The resolution has been updated, from Not determined to DUPLICATE.
Comment posted by
 Daniel Scharrer
Apr 01, 21:44
This should now be fixed in 1.2-dev-2020-04-01.