Talk:Quest ransack

So I've been running one quest a lot recently to get stats on collectable drops - maybe 20 times in the week and exactly six in the last 2 hours. And I am not seeing any ransack penalty. I type /ransack and I get a report that mentions another quest I ran a few times has 10% against it. I run that again and it goes to 30%. /ransack appears to be working but I have no ransack for the main quest I just ran six times (I was re-trying /ransack after 4th, 5th, 6th completions). End quest reward guy did note I had run the quest a lot but none of the chests had less stuff and the rewards list was still as full as ever. The quest in question is Lords of Dust (level 16) run on Casual so it's level 15 effectively and with a level 14 PC. I have a few buffs going for extra xp (guild and potion), gem of +1 treasure level, guild bonus and the one for increasing kill counts in wilderness areas. Doubt any of those would account for this. Is it being on Casual that makes it ignore ransack? I saw no penalty to xp which was a little varied probably due to the bonus xp optional stuff for killing a randomly appearing red name dog. Base xp 2940 (as listed), total xp was listed as 3528 or 4021. Come to think of it I didn't check that was the actual increase in my listed total xp, but I could tell I was gaining xp faster than i ought to have been. I was getting +10% each for the aggressive, perfect and no-re-entry bonuses. Don't recall if I ever saw any ransack notices on chests or quest completion beyond the last time, but if I did then it made no impact on actual xp or treasure. is this a known effect? Elajna (Contributions • Message) 03:17, March 31, 2014 (EDT)


 * From my experience it seems chest ransack doesn't increase on casual either. In fact it is probably governed by the same logic so maybe the two pages should be merged?  Chest ransack and quest ransack.  I don't know why you'd not want to get all the details and read both if you are wanting that knowledge.  Unknown is whether casual run gets normal chest drops (for casual play) even after you have got ransack penalties on the chests that would normally lead to you getting almost nothing.  Also: Solo play does accrue ransack.  At least for the purposes of reporting using the /ransack command.  Solo is not counted as Casual.  Elajna (Contributions • Message) 11:51, March 31, 2014 (EDT)


 * Also... how do you auto create the fancier sigs? I know about 4 tildes. Is there another sig pattern you are using?  If so is that pattern on the new users page?  Elajna (Contributions • Message) 11:51, March 31, 2014 (EDT)


 * I have done three more runs of Haverdasher casual with the same character. Both chests and end reward ended up ransacked. So it's a different mechanics. Also, the fancy sig is a function of the Template:Post which I have used; I have signed my post using the same 4 tildes as you. --Cru121 (Contributions • Message) 14:13, March 31, 2014 (EDT)


 * OK, I am now getting chest ransack, and even completely emptied on chests in the quest (after another 4 runs of Lords of Dust). XP reward remains the same and /ransack shows nothing. Elajna (Contributions • Message) 23:13, March 31, 2014 (EDT)


 * I am wondering about the phrase "and if you never wait a full 36 hours you will always have some penalty". It made me think that the ransack penalty was halved after a day (ie a 30% penalty becomes a 15%) whereas the penalty is reduced by 50 (ie 30% ransack simply goes to zero).  if that is the case i don't understand how the statement "and if you never wait a full 36 hours you will always have some penalty" is true.  If you run the ransack up to 80% and wait 18 hours it will be at 30%.  If you run again (50%) and then wait another 18 hours it will be at zero without you waiting a clear 36 hours ever.  Am I misunderstanding how it works?  Elajna (Contributions • Message) 23:13, March 31, 2014 (EDT)


 * That 36 hours statement is confusing and should be removed/reworded somehow. You're understanding the mechanics correctly.--Cru121 (Contributions • Message) 02:50, April 1, 2014 (EDT)


 * Yes, this was fixed (release notes). --Cru121 (Contributions • Message) 00:18, November 15, 2014 (EST)