There is no reason the workflow should ever create a custom item with no name and expect the user to start a separate workflow just to give it a name. Adding a custom item should immediately jump to edit it.
Note this is not about creating complex or magical items such as homebrew. It is as simple as adding a necklace (which may or may not ever be magical) or a feather and other spell-casting components.
Maybe when the item is created it still automatically has the temporary name, but it skips steps 5 and 6 and the name is already highlighted for you to replace it.
That would fix the workflow (saving a few seconds per item) without any additional risk of bugs.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Current process:
There is no reason the workflow should ever create a custom item with no name and expect the user to start a separate workflow just to give it a name. Adding a custom item should immediately jump to edit it.
Note this is not about creating complex or magical items such as homebrew. It is as simple as adding a necklace (which may or may not ever be magical) or a feather and other spell-casting components.
This workflow prevents a user from creating a custom item without a name, which could break things.
Find my D&D Beyond articles here
Then don't create the item until a name has been provided?
A bag of custom items that are unidentified only makes sense for the most evil of DMs.
Maybe when the item is created it still automatically has the temporary name, but it skips steps 5 and 6 and the name is already highlighted for you to replace it.
That would fix the workflow (saving a few seconds per item) without any additional risk of bugs.