#5295 Description is lost if stacks of marked scrolls are merged
Starting point
1- Right Hand : A scroll marked
2- 5 empty scrolls in bag
3- Empty spaces in bag
Method 1:
1- I use 1 empty scroll at the same spot that the marked scroll. The new one joins the stock in right hand. Both are marked with legend.
Method 2:
1- I put the scroll marked in the bag. Now my right hand is empty.
2- The scroll goes into the bag and it is marked with legend.
Now I put the 3 marked scrolls (with legend) in the floor
1- I use 1 empty scroll. It is marked without legend and it is in my bag. I merge with the ones I had on the floor and now I have 4 marked scrolls (without legend) in my bag.
2- I use /markscroll and now I have 5 marked scrolls (without legend) in my bag.
3- I drop the scroll without legend and I use /markscroll. Now I get a marked scroll with legend. In my right hand.
4- I move the 5 marked scrolls to my bag and from there I merge them with the one in my right hand. I get 6 marked scrolls (with legend) on my right hand.
I hope you can test it now.
Discussion
Anonymous
How can a marked scroll exist without a location?
Was that today in int_ados_townhall?
All marked scroll have a location. if you dont use the /markscroll you dont have legend on them, and if you use the command you have the legend. The problem is with the legends. and yes, it was today in int_ados_townhall where i did it.
What do you mean with "legend"?
M0.1 87864737 moved marked scroll 22595378 from bag to rhand
M1.1 87864812 created marked scroll 22595403 with infostring int_ados_town_hall_2 7 9
M1.1 87864813 marked scroll 22595403 is merged into marked scroll 22595378 resulting in 2 marked scrolls 22595378
M2.1 87864886 moved 2 marked scrolls 22595378 from rhand to bag
M2.2 87864943 created marked scroll 22595424 with infostring int_ados_town_hall_2 7 9
M2.2 87864944 marked scroll 22595424 is merged into 2 marked scrolls 22595378 resulting in 3 marked scrolls 22595378
M3.0 87865040 moved 3 marked scrolls 22595378 from bag to ground int_ados_town_hall_2 6 9
M3.1 87865045 created marked scroll 22595447 with infostring int_ados_town_hall_2 7 9
M3.1 87865084 moved 3 marked scrolls 22595378 from ground int_ados_town_hall_2 6 9 to bag
M3.1 87865263 3 marked scrolls 22595378 is merged into marked scroll 22595447 resulting in 4 marked scrolls 22595447
M3.2 87865262 created marked scroll 22595498 with infostring int_ados_town_hall_2 7 9
M3.2 87865263 marked scroll 22595498 is merged into 4 marked scrolls 22595447 resulting in 5 marked scrolls 22595447
M3.3 87865352 moved 5 marked scrolls 22595447 from bag to rhand
M3.3 87865494 created marked scroll 22595559 with infostring int_ados_town_hall_2 7 9
M3.3 87865263 marked scroll 22595559 is merged into 5 marked scrolls 22595447 resulting in 6 marked scrolls 22595447
M3.3 87865519 moved 6 marked scrolls 22595447 from rhand to ground int_ados_town_hall_2 6 9
M3.3 87865778 moved 6 marked scrolls 22595447 from ground int_ados_town_hall_2 6 9 to bag
M3.3 87865831 created marked scroll 22595663 with infostring int_ados_town_hall_2 7 9
M3.3 87865834 moved 6 marked scrolls 22595447 from bag to lhand
M3.3 87865832 6 marked scrolls 22595447 are merged into marked scroll 22595663 resulting in 7 marked scrolls 22595663
Infostring. That is why I use the command markscroll, so you can name your marked scrolls. And merging them, the infostring goes away sometimes.
Ah, I did not know about that. The description attribute is not part of the "may two stack be merged" check, only the itemname and infostring is. So if there are two stacks of marked scrolls with the same infostring (location), they are merged and one of the descriptions wins. This may be the empty description.
Persistent descriptions are kind of a hack, so the fix in not that simple.