Urgent UI Changes | World Anvil

Remove these ads. Join the Worldbuilders Guild

Urgent UI Changes

User Interface (UI) / User Experience (UX) · Overlay system · Created by Dungeon_builder14
open
User-interface Design statblocks
Worldanvil's new UI changes are detrimental to my experience as a creator and campaign-writer, and I do not say that lightly. Two issues have sprung up from the UI, one inconvenient, the other significant.   Do note that I am a mobile user (specifically an iPad user), and I don't know if these issues are present on PC.  

Inability to Hold-tap for Tabs

Previously, it was possible for me to simply hold tap on a Worldanvil link-button to "preview" it. I mainly did this with statblocks to compare two for balancing. Due to the new interface, I cannot do this anymore, and attempt to do so merely highlights the icon. The navigation is also far less intuitive than before, as to edit a statblock, you have to click on its text, rather than finding the distinct pencil editing symbol.   While it is true that I can go to the start menu and open a new tab from there, doing so means that I have to navigate back to Worldanvil, find the article or statblock, and open it in that new tab. This is far more inconvenient than simply hold-tapping and opening the new tab in literally less than a second—something I could do before with the old, completely functional page-based UI.   However, this issue is nowhere near as significant as the new one that I found mere minutes ago.  

Missing Statblocks

Some of my statblocks are straight up gone from the UI. Not there, and I also cannot search them using the filter either. I tried. I know they still exist, as I went to the statblock discovery and did find them through searching. However, they are completely gone from the statblock UI at the side of the screen. Images below for reference.
As you can see, the statblock still exists, and if I click on it in the public statblock searcher, I can still edit it. However, that is stupidly inconvenient. I can tell that, unlike the previous issue, this is a bug, not a feature; however, it is far more significant of an issue than the previous problem, as the process to get around it takes significantly longer.

Follow up


Update: the bug has been fixed. Do not vote on this.   Also, I apologize for using Feature Request for a bug report, but I literally couldn’t find the bug report at the time of making this.
Current score

2/300 Votes · +399 points

Votes Cast