Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report #1111  -  Item stack size glitch
Posted Dec 28, 2017 - updated Apr 01, 2020   Shortlink: http://arx.vg/1111
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Fixed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • Status
     
    Fixed
  • Assigned to
    Not assigned to anyone
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     Daniel Scharrer
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Not determined
  • Resolution
    RESOLVED
  • Priority
    Not determined
  • Reproducability
    Not determined
  • 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
For items with a max stack size of 10 is sometimes possible to stack one stack of 9 items onto another stack of 9 items, creating a stack of 18 items.

http://steamcommunity.com/app/1700/discussions/0/1621724915793377124/
Steps to reproduce this issue
  1. Create a stack of 9 items in a chest
  2. Create a stack of 9 items of the same type in your inventory
  3. Drag the whole stack from your inventory using shift
  4. Drop the dragged stack onto the stack in the chest but release shift just before you release the mouse button
  5. With some luck the two stacks will be combined

#3
icon_reply.pngReply
Comment posted by
 Daniel Scharrer
Mar 22, 01:21
This happened when dropping an item onto a secondary inventory slot which contains a different item but a non-full stack of the dropped item type is somewhere else in the secondary inventory. Shift does not seem to make a difference.

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.
#4
icon_reply.pngReply
Comment posted by
 Daniel Scharrer
Apr 01, 21:45
This should now be fixed in 1.2-dev-2020-04-01.