Editorial process
Forsaken ID verification method
The database separates an editorial Roblox asset check from live player feedback. A public asset can match its record today and still stop working later because of moderation, privacy changes, or a Forsaken update.
Four-step check
How an ID becomes a published record
01
Identify the asset
Record the numeric ID, reported name, intended Forsaken category, and the public Roblox asset type.
02
Match the metadata
Confirm that the number resolves to the named audio or image asset and that its type matches the setting where it will be used.
03
Publish the check date
Store the last-check date and verification state on the dedicated detail page so the result is auditable over time.
04
Watch community status
Collect one current vote per visitor and ID. Repeated not-working reports flag the record for another editorial check.
Status definitions
What the labels mean
- Asset verified
- The numeric ID resolves to the recorded public Roblox asset, and the asset type matches the record.
- Community working status
- Players report whether the ID currently works in Forsaken. This signal can change independently from the editorial asset check.
- Last checked
- The date when the record’s asset match was most recently reviewed. It is not a permanent availability guarantee.
Corrections
When an ID stops working
Use the “Not working” button on the ID detail page. Reports do not automatically delete an entry; they create a visible signal for another check and protect the database from one-off or accidental reports.
Return to the Forsaken IDs search to open a record and submit current feedback.