Paint and Seek code history should show when a code was first reported, which creator it belongs to, what reward was claimed, and when Paint & Seek Lab last tested it.
Paint and Seek code history fields
Paint and Seek code history is more useful than a simple active list. A history row can explain why a code moved from reported to working, why a reward value changed, or why a code became expired.
| Field | Example use |
|---|---|
| First seen | The first dated source that mentioned the code. |
| Game creator | Ikitai Studios, Blend version, or unknown. |
| Claimed reward | The reward value before testing. |
| Verification method | Roblox description, in-game test, or media discovery. |
| Status change | Working, expired, conflicting, or unconfirmed. |
Why history matters
Paint and Seek code history protects players from stale posts. If a code was valid last week but expired today, Paint and Seek code history can show the change instead of hiding the old row. It also helps separate reward conflicts from creator confusion.
Current use
Paint and Seek code history will be filled as tests happen. Until then, this page defines the rules and links players to the current creator-specific ledgers.