44 lines
1.7 KiB
Markdown
44 lines
1.7 KiB
Markdown
# V4.2.10 – Admin Drop Diversity Fix
|
||
|
||
## Problem
|
||
Admin-generated NFT gifts (`artifact_origin=admin_drop`) could end up visually too close to an already owned winning NFT. In practice this produced near-duplicate collectibles with the same visible theme (for example two very similar `Apex Racer` cards), which weakens the collector value.
|
||
|
||
## Root cause
|
||
The collection prompt already varied by task/winner/seed, but the visible trait selection was still narrow enough that an admin drop could collide with a previously owned card:
|
||
|
||
- the same high-level theme could be selected again,
|
||
- pose and atmosphere could also land close to an earlier card,
|
||
- the prompt did not strongly enough enforce cross-card distinctness.
|
||
|
||
This was not an admin queue problem anymore; it was a *collectible diversity* problem.
|
||
|
||
## Fix
|
||
The artifact generator now adds a collector-aware diversity pass for `admin_drop` items:
|
||
|
||
1. Before rendering an admin drop, the artifact worker loads up to 128 already-owned ready collectibles for the target owner.
|
||
2. Their visible collection traits are re-derived.
|
||
3. The new admin drop then deliberately prefers the **least-used** values for:
|
||
- theme
|
||
- pose
|
||
- atmosphere
|
||
- camera / staging
|
||
- palette story
|
||
- scene emphasis
|
||
4. The image prompt now includes stronger art-direction sections:
|
||
- `CAMERA / STAGING`
|
||
- `COLOR STORY`
|
||
- `SCENE EMPHASIS`
|
||
- `COLLECTOR UNIQUENESS REQUIREMENT`
|
||
|
||
This makes admin gifts much less likely to repeat a card the account already owns.
|
||
|
||
## Scope
|
||
Only the collection-artifact path changed. No database migration is required.
|
||
|
||
## Deployment
|
||
Rebuild only:
|
||
|
||
- `Dockerfile.server`
|
||
|
||
Customer-Service and Worker images do not need changes for this fix.
|