# Users With Transparent PFPs

This feature evaluates the user's PFP and blocks the message if the ratio of the transparent and opaque pixels doesn't matchs the tolerance.

## <mark style="color:$primary;">Scam Mechanics.</mark>

Before we start, just look at this message by **Mr. Diamond**, who is the server admin:

<figure><img src="/files/EgKZQ56IEjuV39lksvs6" alt=""><figcaption></figcaption></figure>

Did you notice anything that looks suspicious to you in this message? Probably not. <mark style="color:red;">And this is a problem!</mark> Because there are actually two messages from two different users!

In **Discord,** users can set up transparent PNG images for avatars, as well as use emojis instead of letters in their display names. And this is how the user profile can look as a result:

<figure><img src="/files/16OL2uGwVpEq1TNipfTL" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/QjWG0iEV3f3Mv0NBb8YE" alt=""><figcaption></figcaption></figure>

But if we inspect the source code via the developer console in the browser, we'll see that there is indeed another one PFP here - that very transparent PNG our Mr. Smart Guy set earlier for his account!

<figure><img src="/files/GWUycNF2QD6ubmA3ZCKs" alt=""><figcaption></figcaption></figure>

It is still a very popular scammer's trick! People in **Discord** are, in most cases, careless and relaxed, and can easily lower their guard and mistake such a message for a message from an administrator or a member of the project team.

## <mark style="color:$primary;">Explanation of the Feature.</mark>

And this is where the <mark style="color:$success;">Users With Transparent PFPs</mark> feature comes into action! It analyzes the user avatar if its ratio of the transparent and opaque pixels matches the tolerance, and if it doesn't, it blocks the message:

<figure><img src="/files/CP5SuzSUc2gJLXs5RXGo" alt=""><figcaption></figcaption></figure>

Depending on your [Guard Settings](/plugins/guard/guard-settings.md), <mark style="color:purple;">**Bocto**</mark> can also post a detailed alert to the <mark style="color:yellow;">**#alerts**</mark> channel it created during the [setup on the server](/getting-started/setup-on-server.md):

<figure><img src="/files/bDWoLw8YfwnFZ7Md1rjb" alt=""><figcaption></figcaption></figure>

Sometimes, scammers even try to set the transparent PNG image with a small, barely visible grey opaque dot to trick the weak filters. However, <mark style="color:purple;">**Bocto**</mark> uses a 40% tolerance barrier to determine and block scam PFPs, while allowing legit PFPs with some amount of transparent pixels.

<div><figure><img src="/files/6cnJOz4jzbb4ftyGW9pr" alt=""><figcaption></figcaption></figure> <figure><img src="/files/zz4ZsM1pnrls4JbsqhEu" alt=""><figcaption></figcaption></figure></div>

## <mark style="color:$primary;">PFP Types That This Feature Blocks.</mark>

Currently, the <mark style="color:$success;">Users With Transparent PFP</mark> feature only reacts to PFP transparency. In the future, we will also add an analysis algorithm for **Discord** themes' colors.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guide.bocto.octopeeps.com/plugins/guard/guard-features/users-with-transparent-pfps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.