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

First draft for task: Update FAQ/Arguments/dev mode/beta #35

Merged
merged 5 commits into from
Sep 8, 2024

Conversation

Darkfinst12
Copy link
Contributor

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@Darkfinst12 Darkfinst12 marked this pull request as draft August 9, 2024 18:43
Copy link
Owner

@MoonlightCapital MoonlightCapital left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job with making subfolders for the dev mode images! Also the FAQ will generally need to be re-verified entirely since some things need rewording or updates for clarity


You can also contact support to receive a temporary exemption from sustaining, if necessary.
2. **Vote Requirement**: The number of votes received by the adder must be equal to or greater than the number of days the temporary role lasts. For example, a 30-day temprole requires at least 30 votes to be sustained.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. **Vote Requirement**: The number of votes received by the adder must be equal to or greater than the number of days the temporary role lasts. For example, a 30-day temprole requires at least 30 votes to be sustained.
2. **Vote Requirement**: The number of votes received by the adder must be equal to or greater than half the number of days the temporary role lasts, rounded up. For example, a 30-day temprole requires at least 15 votes to be sustained

My bad for having forgotten this, half. Also link to the page that explains voting


## Will my temproles be erased if a bot downtime happens?
3. **Premium Instance**: The server must be on a premium instance (Advance+ tier).
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
3. **Premium Instance**: The server must be on a premium instance (Advance+ tier).
3. **Premium Instance**: The server uses a MoonlightBot Premium instance (Advanced tier or higher)

link here as well


No! There's absolutely no reason to worry about potential data losses as MoonlightBot is designed to be resilient. We are committed to 99% uptime, but if it ever happens that the bot goes down, your temproles will be removed as nothing happened.
4. **Exemption Request**: The adder must have requested and received an exemption from bot staff
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
4. **Exemption Request**: The adder must have requested and received an exemption from bot staff
4. **Be Exempted**: The adder must have requested and received an exemption from bot staff

Where? How? Exemption from what?

* Reaction roles have an option to make their roles temporary. To see how to set up reaction roles, see [Setting up reaction roles](setting-up-reaction-roles.md).

## How do I cancel a temprole?

You can cancel a temprole to force an immediate expiration by using the `temprole` command with a duration that would make it expire in the past. Say you want to cancel a temprole that has 3 days left of time:
You can cancel a temprole to force an immediate expiration by using the `temprole` command with a duration that would make it expire in the past. Say you want to cancel a temprole that has 3 days left:
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
You can cancel a temprole to force an immediate expiration by using the `temprole` command with a duration that would make it expire in the past. Say you want to cancel a temprole that has 3 days left:
You can cancel a temprole to force an immediate expiration by using the `/temprole` command with a duration that would make it expire in the past. Say you want to cancel a temprole that has 3 days left:

same goes for any other temporary action

- Your maximum duration allowed to set must be the same when you add it, and when the duration expires
- While the temporary role is active, have gained [a vote](../support/upvote-moonlightbot.md) for at least half of the days. For example, a 30 days temprole is sustained by at least 15 votes

If neither condition is satisfied, the temprole will not removed from the target user. You can check if everything is sustained with the `/status` command, and eventually how to correct it.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So now how does one check? (/list-temproles)

@MoonlightCapital MoonlightCapital self-requested a review August 9, 2024 19:01
Darkfinst12 and others added 4 commits August 9, 2024 21:01
Co-authored-by: MoonlightCapital <[email protected]>
Co-authored-by: MoonlightCapital <[email protected]>
Co-authored-by: MoonlightCapital <[email protected]>
Co-authored-by: MoonlightCapital <[email protected]>
Copy link
Owner

@MoonlightCapital MoonlightCapital left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Previous approve was a misclick

@MoonlightCapital MoonlightCapital changed the title First draft for task: First draft for task: Update FAQ/Arguments/dev mode/beta Aug 9, 2024
@sks316 sks316 merged commit 345aa84 into MoonlightCapital:testing Sep 8, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants