Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Scattering of Journal Abilities fix request

This seems like a bug to me... Is there a plan to fix the problem where if you have more than 10 abilities on the journal clicked as "Token Actions", that they will not remain in order on the screen but will instead scatter in the order in which they appear at the top of the screen? This repair would be very appreciated by at least me... and I assume many others.
1436211362
Stephen Koontz
Forum Champion
Marketplace Creator
Sheet Author
API Scripter
Compendium Curator
The order of Token Actions isn't guaranteed and wasn't originally envisioned for more than 10. It is working as intended and isn't a bug. That said, this is something that's been brought up before and may be functionality we'll revisit later.
Thanks for the response Steve. I can work with 10, a few more would simply be better.
Why are so many bugs like this being labeled as resolved when they're not?
1436256105

Edited 1436256753
Kryx
Pro
Sheet Author
API Scripter
Because it is "working as intended" even if that intention is not what should have been. It's a poor definition of a bug imo. If there was a limit of 10 items and they sorted correctly then this would be a design limitation and adding more would be a feature. If there is no limit, but after a certain amount they stop sorting properly then that is a bug. A software bug is an error, flaw, failure, or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways. Most bugs arise from mistakes and errors made by people in either a program's source code or its design It may not be desirable for roll20 to fix these less common cases, but it is indeed a bug by that definition imo.
In fairness, I understand the concept of a Cost/Benefit analysis, and perhaps the Devs do not believe that it is worth their time to repair this bug compared to the value of how many people this will affect. As a paying subscriber, however, I request that they do repair this bug.
1436390640
Kryx
Pro
Sheet Author
API Scripter
Agreed. I also understand that as I work in the same industry. Often it's rare enough that it doesn't deserve priority. I understand that. The rant above is that issues should be categorized correctly.