# Home Name

### Regex Filtering – How It Works & How to Customize It

Regular expressions (regex) are powerful text-matching patterns used to block unwanted home names. While they can look complicated, this section will help you understand **what the current regex does** and **how to add your own rules easily**, even without advanced knowledge.

## 🔍 What the current regex does

```yaml
regex: "(?i)(([a-zA-Z0-9.-]+)?\\.(gg|com|net|org|xyz|co|me|io|hu|uk|us|de|fr|it)(\\s|$)|f[uú][cçkq][kq])"
```

This pattern is designed to block:

1. **Domain names and server ads**\
   Examples it will block:
   * `example.com`
   * `mycoolserver.net`
   * `play.server.gg`
2. **Swear word variations**\
   Specifically obfuscated forms of the word `fuck`, like:
   * `fúck`, `fuçk`, `fuqk`, `fück`

It uses **case-insensitive matching** (`(?i)`), so it also blocks uppercase versions.

### 🧩 How to add your own regex (even if you're not a regex expert)

If you want to block something specific (e.g., names like "test123" or any word containing "hack"), you can simply extend the existing regex pattern using `|` (OR).

**Example: Block “test123” and anything starting with “hack”**

```yaml
regex: "(?i)(([a-zA-Z0-9.-]+)?\\.(gg|com|net|...)(\\s|$)|f[uú][cçkq][kq]|test123|hack[a-z]*)"
```

> 💡 `|` means OR\
> 💡 `hack[a-z]*` blocks "hack", "hacker", "hacking", etc.

### ✍️ Tips for Regex Editing

* Always escape backslashes (`\\.` instead of just `.`) in YAML.
* Wrap the entire expression in quotes (`"..."`), especially when using special characters.
* Test your regex online using tools like [regex101.com](https://regex101.com/) before adding it to your config.


---

# 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://docs.mongenscave.com/premium-products/homes/feature-help/home-name.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.