Age Verification

Masquerade uses a semi-automated verification system powered by Elias — The Attendant and Rico Rojo — Master of Ceremonies.

Here is the exact flow:

1. The user opens a verification ticket

   • They are prompted to submit:

     • Date of Birth

     • Current Age

2. A private thread is created automatically

   • Only the user, Bouncers, and Admins can see it.

   • The Staff roles are quietly added — no pings yet.

3. The user sends their verification photo(s)

   • The bot detects the image.

   • The user receives a Submit button.

   • Pressing the button:

     • Stores their user ID as the ticket’s “User”

     • Alerts the Bouncer role with a ping

     • Prepares the ticket for review

4. Bouncer reviews the submission

   • The Bouncer clicks the Action Menu on the ping message. They can choose:

     • Verify

     • Deny

     • Unset (rarely needed—used only if the wrong user was bound to the ticket)

5. Verification Type Selection

   • If verifying, the Bouncer chooses:

     • ID18+ (standard ID + paper + selfie verification)

     • Partner (trusted partner verification)

   • Bot displays the exact DOB cutoff date (e.g., “User is 18+ if DOB is on or before 11/16/07”)

6. Confirmation

   • Bouncer: “Are you sure you want to verify this user?”

     • If yes:

       1. Verification roles are automatically applied

       2. A verification log is generated automatically (to #mod-logs)

       3. The user is notified

7. Ticket Closure

   • The user is reminded to delete photos before closing

   • Bouncer to use /ticket requestclose to trigger timed closure

   • Age Verification tickets do NOT generate transcripts

Check the following:

1. Both required photos are present

   • Selfie + paper

   • ID + paper

2. All details match

   • Same date and ticket number

   • Same username

   • ID appears legitimate

   • DOB aligns with the cutoff date

3. Content is clear and readable

   • Not too dark

   • Not blurry

   • Text clearly visible

4. Photos appear genuine

   • Watch for:

     1. Heavy edits

     2. Strange cropping

     3. Blurred or mismatched faces

     4. Signs of manipulation

5. The user appears to be 18+

If something feels off → escalate.

Used when a member is already age-verified in a Trusted Partner server.

Required Proof

One (1) screenshot or short screen recording showing:

• The user’s Discord username

• The partner server name or icon

• Their age-verified role in that server

What Bouncers Check

• The server is on the Trusted Partner List

• Username matches this ticket

• The verified role is legitimate (not cosmetic)

• Screenshot/video is clear and unedited

• No suspicious cropping or mismatched profile info

If Approved

• Select Partner during verification

• Confirm → bot applies roles, logs, and prompts closure

If Denied

User may:

• Resubmit correct partner proof

• Or switch to ID Verification

Escalate if:

• Server isn’t recognized

• Role seems fake or unsafe

• Screenshot appears altered

• Something feels “off”

Missing Required Content

• Only one of two required photos provided

• Missing handwritten paper

• Missing date, ticket number, or username

Unreadable or unclear photos

• Too dark

• Too blurry

• Glare obscures details

• Face partially covered or shadowed

• Camera too far away

Incorrect file type

• Photos submitted as HEIC
  (We do not download files; user must resend as PNG/JPG.)

Suspicious or inconsistent submission

• ID doesn’t match the selfie

• Ticket number is incorrect

• Signs of editing

• Information inconsistent with DOB/appearance

Partner Verification issues

• Screenshot missing username/server/role

• Server not on Trusted Partner list

• Role does not confirm age

Bot opens a denial form.

Bouncer should:

• Choose the correct reason

• Add comments if needed

• Encourage the user to correct and resubmit

Escalate immediately if:

• The user appears underage

• ID/DOB conflict

• Photos look altered or suspicious

• The user attempts to circumvent verification

• They show hostility, defensiveness, or inconsistent information

• Partner verification comes from an unknown or questionable server

• You’re simply unsure

When in doubt → escalate.