Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added FAQ #2904

Merged
merged 4 commits into from
Oct 28, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/_meta.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,5 +2,6 @@
"introduction": "Introduction",
"adding-servers": "Adding Servers",
"using-servermappings": "Using Server Mappings",
"inactive-servers": "Inactive Servers"
"inactive-servers": "Inactive Servers",
"faq": "FAQ"
}
2 changes: 1 addition & 1 deletion docs/adding-servers/metadata.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Below is a table of the basic fields that are required for your server's metadat

| Field | Description |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `id` | This is the ID for the server, discussed in the [overview](server-mappings/adding-servers/overview), this must match the name of your server's folder. |
| `id` | This is the ID for the server, discussed in the [overview](/overview), this must match the name of your server's folder. |
| `name` | This is the name for your server. |
| `description` | This is the description for your server. It must be **between 16-80 characters** and in English. The Lunar Client translation team is responsible for translating this to server other supported languages. |

Expand Down
44 changes: 44 additions & 0 deletions docs/faq.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
# FAQs

<details>
<summary>How long does it take for my Pull Request (PR) to be merged?</summary>

We typically review all pull request once to twice a week.
However, if your pull request is marked with issues that need resolved, we will skip over your pull request, until those issues have been resolved.

</details>

<details>
<summary>How long does it take for my server to appear in Discord/Lunar RPC?</summary>

After your pull request has been reviewed and merged, it typically takes around 24-48 hours before your server will start to appear.
In certain cases, like updating your server logo, it can take several days before appearing due to Discord's cache. There is nothing we're able to do about the cache.

**Note:** Do not alert or contact us asking for an update if it has __not__ been over 5 consecutive days after your pull request has been merged.

</details>

<details>
<summary>What should I do if I own or manage a domain that's in the inactive file?</summary>

You can open a fork, removing it from the `inactive.json` file. After that, ensure your server information is update and contains all the required information.

If you do not update your server information, your pull request will be denied.

Don't know how to create a fork? [Click here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)!

</details>

<details>
<summary>Why was my Pull Request (PR) closed?</summary>

We only close pull request in the following events;

- Our team or automated bot requested changes you have not addressed and resolved within 48 hours.
- You deleted, modified, or added unnecessary files.
- If your pull request contained too many errors. Unfortunately, if your pull request contains too many issues, we might close it.
- Your pull request contained copyrighted, stolen, or proprietary images, code, text, or brand related content.

We recommend you create your pull request once you're ready to have it merged. If your pull request has been closed, you may reopen it at anytime.

</details>