Welcome to The Bug Genie
Please fill in your username and password below, and press "Continue" to log in.If you have not already registered, please use the "Register new account" tab to do so.
Please wait while updating issue type...
Could not save your changes
This issue has been changed since you started editing it
Data that has been changed is highlighted in red below. Undo your changes to see the updated information
You have changed this issue, but haven't saved your changes yet. To save it, press the Save changes button to the right
This issue is blocking the next release
Create a comment There are no comments
There is nothing attached to this issue
This issue has no duplicates
There are no code checkins for this issue |
|||||||||||||||||||||||||||||||||||||||||||||||
Really delete this comment?
Really delete this comment?
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?
Really delete this comment?
Really delete this comment?