Added more depth than a command ref for Claim Protection #7
Conversation
WalkthroughThis pull request removes the outdated documentation file for claim commands and introduces a new, comprehensive guide for claim protection. The removed file listed various commands for creating and managing land claims. The new document consolidates guidance on creating claims, managing permissions—including granular permission types—and abandoning claims, along with additional features and tips. No changes were made to exported or public entities. Changes
Poem
Tip 🌐 Web search-backed reviews and chat
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (11)
docs/survival/claim-protection.md (11)
13-17: Formatting: Surround the Claiming Land table with blank lines.For better readability and to comply with Markdown best practices (MD058), consider adding a blank line before line 14 and after line 17 where the table is defined.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
14-14: Tables should be surrounded by blank lines
null(MD058, blanks-around-tables)
18-18: Formatting: Remove trailing punctuation from heading.The heading "#### How to Use:" ends with a colon. Removing it (i.e. changing to "#### How to Use") will improve consistency per MD026.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
18-18: Trailing punctuation in heading
Punctuation: ':'(MD026, no-trailing-punctuation)
26-32: Formatting: Surround the Managing Permissions table with blank lines.Adding an empty line before and after the table will help with readability and adheres to Markdown guidelines (MD058).
🧰 Tools
🪛 LanguageTool
[grammar] ~28-~28: ‘a’ may be redundant when used with the uncountable noun ‘permission’.
Context: ...---- | | /trust [player] | Grants a player permission to build and interact in your claim. | ...(A_UNCOUNTABLE_NOUN)
🪛 markdownlint-cli2 (0.17.2)
26-26: Tables should be surrounded by blank lines
null(MD058, blanks-around-tables)
35-37: Markdown: Specify a language for the fenced code block.To enhance syntax highlighting and clarity, add a language identifier (for example,
shell) after the opening triple backticks.-``` +/```shell🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
35-35: Fenced code blocks should have a language specified
null(MD040, fenced-code-language)
38-38: Style: Rephrase the access instruction for clarity.Rather than "Enter the player name you want to give access to on your claim, and then specify the type of access," consider rephrasing it to something like: "Specify the player name you wish to grant access to, then indicate the desired type of access." This change can improve clarity and flow.
🧰 Tools
🪛 LanguageTool
[style] ~38-~38: Try using a synonym here to strengthen your writing.
Context: ...> ``` Enter the player name you want to give access to on your claim, and then speci...(GIVE_PROVIDE)
41-41: Punctuation: Insert a comma for clarity.For the description at line 41, modify the phrase to "grants a player access to interact with all blocks, including inventory." This small change increases readability.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~41-~41: Possible missing comma found.
Context: ...ts a player access to interact with all blocks including inventory. - builder - gr...(AI_HYDRA_LEO_MISSING_COMMA)
46-48: Markdown: Specify a language for the fenced code block.Similar to the earlier code block, adding a language identifier (for example,
shell) after the opening triple backticks will boost clarity and syntax highlighting.-``` +/```shell🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
46-46: Fenced code blocks should have a language specified
null(MD040, fenced-code-language)
53-57: Formatting: Surround the Abandoning Claims table with blank lines.To follow Markdown formatting guidelines (MD058), please add an empty line before the table at line 53 and after line 57.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
53-53: Tables should be surrounded by blank lines
null(MD058, blanks-around-tables)
58-58: Formatting: Remove trailing punctuation from the Important Notes heading.Consider revising "#### Important Notes:" to "#### Important Notes" by removing the colon, which aligns with MD026.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
58-58: Trailing punctuation in heading
Punctuation: ':'(MD026, no-trailing-punctuation)
65-69: Formatting: Surround the Additional Features table with blank lines.Adding blank lines before and after the table will enhance readability per Markdown standards (MD058).
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
65-65: Tables should be surrounded by blank lines
null(MD058, blanks-around-tables)
70-70: Formatting: Remove trailing punctuation from the Example heading.To match style guidelines (MD026), remove the colon from "#### Example:" so it reads "#### Example".
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
70-70: Trailing punctuation in heading
Punctuation: ':'(MD026, no-trailing-punctuation)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
docs/survival/claim-commands.md(0 hunks)docs/survival/claim-protection.md(1 hunks)
💤 Files with no reviewable changes (1)
- docs/survival/claim-commands.md
🧰 Additional context used
🪛 LanguageTool
docs/survival/claim-protection.md
[grammar] ~28-~28: ‘a’ may be redundant when used with the uncountable noun ‘permission’.
Context: ...---- | | /trust [player] | Grants a player permission to build and interact in your claim. | ...
(A_UNCOUNTABLE_NOUN)
[style] ~38-~38: Try using a synonym here to strengthen your writing.
Context: ...> ``` Enter the player name you want to give access to on your claim, and then speci...
(GIVE_PROVIDE)
[uncategorized] ~41-~41: Possible missing comma found.
Context: ...ts a player access to interact with all blocks including inventory. - builder - gr...
(AI_HYDRA_LEO_MISSING_COMMA)
🪛 markdownlint-cli2 (0.17.2)
docs/survival/claim-protection.md
14-14: Tables should be surrounded by blank lines
null
(MD058, blanks-around-tables)
18-18: Trailing punctuation in heading
Punctuation: ':'
(MD026, no-trailing-punctuation)
26-26: Tables should be surrounded by blank lines
null
(MD058, blanks-around-tables)
35-35: Fenced code blocks should have a language specified
null
(MD040, fenced-code-language)
46-46: Fenced code blocks should have a language specified
null
(MD040, fenced-code-language)
53-53: Tables should be surrounded by blank lines
null
(MD058, blanks-around-tables)
58-58: Trailing punctuation in heading
Punctuation: ':'
(MD026, no-trailing-punctuation)
65-65: Tables should be surrounded by blank lines
null
(MD058, blanks-around-tables)
70-70: Trailing punctuation in heading
Punctuation: ':'
(MD026, no-trailing-punctuation)
Summary by CodeRabbit