Actor Prototype Token Name Improvements #117

Closed
opened 2026-06-27 19:48:05 +00:00 by Oliver · 0 comments
Owner

Currently, when an actor is duplicated, the prototype token name stays the same it was on the original actor, instead of just changing the prototype token name to be the duplicated name, we instead prompted the user for a new name (similar to what the createDialog does), and then assigned the name from the dialog into both the actor name and the prototype token's name.

In addition, when changing an Actor's name, it doesn't update the prototype token at all, it would be nice where if the prototype token and the actor name are exactly identical, then the prototype token name will be updated alongside the actor name, keeping them in sync.

The name-sync step requires the duplicate adjustment in order to fully function because otherwise the name editing will immediately fail due to the prototype token name deviating from the actor name.

Currently, when an actor is duplicated, the prototype token name stays the same it was on the original actor, instead of just changing the prototype token name to be the duplicated name, we instead prompted the user for a new name (similar to what the `createDialog` does), and then assigned the name from the dialog into both the actor name and the prototype token's name. In addition, when changing an Actor's name, it doesn't update the prototype token at all, it would be nice where if the prototype token and the actor name are exactly identical, then the prototype token name will be updated alongside the actor name, keeping them in sync. The name-sync step requires the duplicate adjustment in order to fully function because otherwise the name editing will immediately fail due to the prototype token name deviating from the actor name.
Oliver added this to the v3.2.0 milestone 2026-06-27 19:48:05 +00:00
Oliver self-assigned this 2026-06-27 20:08:02 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Foundry/taf#117
No description provided.