Make character UI retries transactional
This commit is contained in:
parent
aeac874dab
commit
1dd5706e15
6 changed files with 352 additions and 42 deletions
|
|
@ -104,7 +104,12 @@ retries on the next frame. Initial dialog-catalog, character root, and string
|
|||
misses likewise retry on later ticks without mounting a duplicate root or
|
||||
controller. Dialog presenter/catalog failures move their contexts to an
|
||||
internal retry ledger, so UI callbacks do not retain poisoned active/queued
|
||||
entries and the same context can appear after resource recovery.
|
||||
entries and the same context can appear after resource recovery. Priority
|
||||
contexts remain ahead of ordinary retries and preserve retail's nested
|
||||
preemption order when creation recovers. The mount coordinator owns a detached
|
||||
controller before attaching its root or running the first template-resolving
|
||||
tick; any partial failure disposes that exact controller before retry, so roots
|
||||
and handlers cannot accumulate.
|
||||
|
||||
There is deliberately no 3D preview and no claimed character-select background
|
||||
scene. The screen root remains neutral with respect to render-loop background
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue