stack merging vs shop pricing
When merging one stack into another and they have different obj->o_id price adjustments, keep the o_id of whichever one commands the higher shop price.
This commit is contained in:
+4
-1
@@ -312,8 +312,11 @@ looking into an applied container with ':' showed prices of unpaid items but
|
||||
prevent achievement luckstone from merging with other luckstones if kicked or
|
||||
dropped by monster (not applicable for dropped by player; achievement
|
||||
would have been recorded and luckstone reverted to normal if picked up)
|
||||
when splitting a stack of gems where internal ID is used to make adjustment to
|
||||
when splitting a stack where internal ID is used to make adjustment to
|
||||
shop prices, pick an ID for new stack that yields same prices as old
|
||||
when merging a stack where internal ID is used to adjust shop prices, always
|
||||
keep the ID which induces the higher price (only matters when buying
|
||||
from shop, not when selling; doesn't affect items already on bill)
|
||||
|
||||
|
||||
Fixes to Post-3.6.1 Problems that Were Exposed Via git Repository
|
||||
|
||||
Reference in New Issue
Block a user