Hi folks,
The recent update to the scroll case and the number of different scrolls (50 different scrolls, and 999 of each) is by my opinion, a bit too little.
Soloing more than one teen to an epic dungeon will fill up the limit of 50 individual scrolls quite swiftly before the end, and the rest will clutter the inventory. I've also noticed that once the scroll case is full, it won't add scrolls within to it even if there are already that kind of scrolls within.
I feel like the limit should be atleast doubled to make the case a bit more meaningful.
Scroll case limitation of different scrolls
Moderators: Active Admins, Forum Moderators, Active DMs
-
- Posts: 6
- Joined: Wed May 19, 2021 3:57 pm
Re: Scroll case limitation of different scrolls
The limits are in place to prevent cases from breaking and people losing their collection. These are measures that will continued to be reviewed to ensure containers work as intended.
Determine your Public CD Key here
Can't see your vault? Have you migrated your accounts? If you have tried, and still can't see them, message me.
Re: Scroll case limitation of different scrolls
The bit about it not adding is unintentional, I did this update while streaming my tests on the official and that was seemingly caught but I'll see why loot isn't following the rule!
As Spyre said and in a previous feedback thread I said, this is to address an error, were the error not so frequent or problematic I would be more hesitant, in addition these are not fixed numbers nor is this a final fix.
The primary issue is that we have an existing system that is looping a large amount of variables to gather data for display, to fix this we either need to change how/when it processes the variables or change the method in which the variables are stored.
Neither of which is simple as any mistake could erase all existing container (not just scroll cases) contents at this juncture.
As Spyre said and in a previous feedback thread I said, this is to address an error, were the error not so frequent or problematic I would be more hesitant, in addition these are not fixed numbers nor is this a final fix.
The primary issue is that we have an existing system that is looping a large amount of variables to gather data for display, to fix this we either need to change how/when it processes the variables or change the method in which the variables are stored.
Neither of which is simple as any mistake could erase all existing container (not just scroll cases) contents at this juncture.
Irongron wrote:I've literally never used -guard on anyone.