feat(ugc): staff reprocessing of a property goes to the front of the queue

/reprocessproperty and the dashboard's Reprocess all models mark the
property's models as priority (ugc.priority, migrations mysql 94 and sqlite
77). The UGC server takes priority models first, polls them even when its
queue is full, and puts them at its front, as it does cars and rockets. The
flag clears once a model is made.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Aaron Kimbrell
2026-09-28 12:26:56 -05:00
parent 8d57cc82cf
commit 9e4f2818c3
12 changed files with 49 additions and 18 deletions

View File

@@ -431,6 +431,9 @@ serving), the worlds:
minutes) it sends every player in the world the new `model.nif` checksums and transfers them back into the same
zone and clone. The client loads the property again and downloads the new meshes (its manifest cache has the new
checksums, which its files don't match). Models of a reprocess skip the "made again" switch.
The models are queued as priority (`ugc.priority`, also set by the dashboard's Reprocess all models): the UGC
server takes them before any other model, polls them even when its queue is full and puts them at its front (as
cars and rockets); the flag clears once a model is made.
### Waiting while the owner is still building