Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated last year
All versions
1.5
Release
NosGrammar 1.5last year 76
Compatibility
Minecraft: Java Edition
1.21–1.21.8
1.20.x
1.19.x
1.18.x
Platforms
Paper
Purpur
Spigot
Changes
New:
- Import/Export Spellings
- Code Overhaul Restructure
Changed:
- Better Commands - All commands now go under /grammar instead of having each command for each logic.
- Better Messages - MiniMessage support, messages have been remapped with more customizability and consistency between all commands, while keeping the legacy mapping.
- Performance Optimization - The plugin is now less likely to experience memory leaks with an efficient and smart caching system
Removed:
- /grammarreload
- /grammarview
- /grammarforce
- /reloadgrammar
- /enablegrammar
- /disablegrammar
- /togglegrammar
- /grammartoggle
- /viewgrammar
Update: messages.yml
# NosGrammar Messages Configuration
# Supports MiniMessage hex colors and placeholders
# Global prefix for all messages
prefix: "<gradient:#FF8500:#FF9D33>[NosGrammar]</gradient> <#DBDBDB>»</#DBDBDB>"
# Status messages with customizable placeholders
status:
enabled: "&fGrammar correction is currently &6Enabled&f."
disabled: "&fGrammar correction is currently &6Disabled&f."
# Placeholders: {status} - enabled/disabled, {player} - player name
other_player: "&fGrammar correction is currently &6{status} &ffor &6{player}&f."
# Toggle messages
toggle:
enabled: "&fGrammar correction has been &6Enabled&f."
disabled: "&fGrammar correction has been &6Disabled&f."
# Force command messages
force:
success: "&aSuccessfully &f{action} &agrammar correction for &f{player}&a."
target_notified: "&fA staff member has &6{action} &fyour grammar correction."
# Placeholders: {action} - enabled/disabled, {player} - target player name
# Error messages
errors:
no_permission: "&cYou do not have permission to use this command."
player_not_found: "&cPlayer &4{player} &cwas not found."
invalid_input: "&cInvalid input. Use: &7enabled/disabled &c(or &7on/off, yes/no&c)."
only_players: "&cThis command can only be used by players."
export_failed: "&cFailed to export spellings. Check console for details."
import_failed: "&cFailed to import spellings. Check console for details."
usage:
general: "&cUsage: &7/grammar <toggle|force|check|reload|export|import>"
force: "&cUsage: &7/grammar force <player> <enabled|disabled>"
check: "&cUsage: &7/grammar check [player]"
export: "&cUsage: &7/grammar export <filename>"
import: "&cUsage: &7/grammar import <filename>"
# Success messages
success:
reload: "&aPlugin configuration has been &2reloaded&a successfully."
export: "&aSuccessfully exported spellings to &2{filename}.txt&a."
import: "&aSuccessfully imported spellings from &2{filename}.txt&a."
# Help messages
help:
header: "&6=== &eNosGrammar Commands &6==="
toggle: "&7/grammar toggle &8- &fToggle grammar correction for yourself"
force: "&7/grammar force <player> <enabled|disabled> &8- &fForce grammar correction for another player"
check: "&7/grammar check [player] &8- &fCheck grammar correction status"
reload: "&7/grammar reload &8- &fReload plugin configuration"
export: "&7/grammar export <filename> &8- &fExport current spellings to file"
import: "&7/grammar import <filename> &8- &fImport spellings from file"
footer: "&6========================"
# Advanced customization options
# You can use MiniMessage hex colors like: <#ff6b6b>text</#ff6b6b>
# Or gradient colors like: <gradient:red:blue>text</gradient>
# Or rainbow: <rainbow>text</rainbow>
# Example with hex colors (uncomment to use):
# status:
# enabled: "<#00ff00>Grammar correction is currently <#008000>enabled<#00ff00>."
# disabled: "<#ff0000>Grammar correction is currently <#800000>disabled<#ff0000>."
# Example with gradients (uncomment to use):
# toggle:
# enabled: "<gradient:green:lime>Grammar correction has been enabled.</gradient>"
# disabled: "<gradient:red:dark_red>Grammar correction has been disabled.</gradient>"
# Legacy message mappings (for backward compatibility)
# These will be automatically mapped to the new structure
legacy_mappings:
togglegrammar_enabled: "toggle.enabled"
togglegrammar_disabled: "toggle.disabled"
no_permission: "errors.no_permission"
player_not_found: "errors.player_not_found"
usage_forcegrammar: "errors.usage.force"
usage_grammarcheck: "errors.usage.check"
grammarforce_torf: "errors.invalid_input"
grammar_status: "status.enabled"
grammarcheck_status: "status.other_player"
reload_success: "success.reload"
authorized_player: "errors.only_players"
grammarcheck_status_informed: "force.target_notified"
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:JfNGnspl:GX2voD7q"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JfNGnspl:GX2voD7q"
}

