Claimorous!
Активный0.0
Установок
0
Последнее обновление
1 неделю назад
Версии
1.20.1
Клиент и сервер
Fabric
Приключенческие
Игровые механики
Управление
Хранилища
Утилиты
Claimorous! - Advanced Land Protection Mod
Overview
Claimorous! is a powerful and highly customizable land protection mod for Minecraft servers running on the Fabric mod loader. It allows players to create protected areas (claims) where their builds and belongings are secured from unwanted interference.
With an intuitive in-game interface and fully configurable settings, Claimorous! offers a flexible claim system suitable for any multiplayer environment. Server administrators have extensive control over the entire system through detailed configuration options, making it an excellent tool for customizing gameplay within modpacks.
Designed to perform efficiently on high-population or high-density servers, Claimorous! ensures both reliability and scalability.
We want you! If you are a server admin and want to discuss features or a player who wants to join the mod test server, Join Us on Discord
Key Features
- Tiered Claim System: Three tiers of claims with customizable sizes
- Comprehensive Protection: Control block breaking/placement, entity interaction, PvP, and more
- Permission System: Fine-grained control on what other players can do within your claim
- Claim Transfer: A contract-like item to transfer claim ownership
- Visual Indicators: Customizable claim borders with particle effects
- Essence System: Optional upkeep system for claims requiring "essence" as a resource
- Admin Claims: Special administrator-controlled claims with unique settings
- Detailed Configuration: Extensive options for server owners to tailor the system to their needs
- And much more: Explosion, pistons, fluids, projectile, and many more option can be configured! Check the Wiki below for more details
Getting Started
Creating a Claim
- Craft a Claim Anchor (the primary block used to define and manage a claim)
- Place the Claim Anchor where you want the center of your claim to be
- The claim will extend in all directions from the anchor according to the tier settings
Claim Management
-
Craft the Claim Monocle item and hold it in your off hand to visualize claim boundaries
-
Interact with your Claim Anchor to manage permissions, upgrade tiers and manage claim essence (if enabled)
Wiki
Claimorous! was designed with an emphasis on extremely granular configuration, allowing any restriction to be managed through a powerful and flexible configuration system. Your imagination is the limit!
While Player Claim follow global server rules and relies on the Claim Anchor, Admin Claim are created and menaged through commands (if OP) and they follow specific rules that can be defined by creating custom admin claim type: this will let you create different admin claimed area that will follow their own rules.
It's not recommended to change config manually, instead player claim config menu can be accessed in game by running /claimorous config, while for admin claim use /claimorous admin config <type>.
Player Claims
Player Claims have different 3 tiers that change the size of protected area. Every plaryer claim have the same restriction behavior, based on config (or default values). Player Claim has these features:Global Claim Settings
These features concern the general settings of player claims. Be careful! Changing claim size won't affect previously placed claimShow config
```toml # Size settings for each claim tier # It represents the cube side length, must be odd, claim anchor is the center of the cube. tier0_claim_size = 7 tier1_claim_size = 11 tier2_claim_size = 15 # Vertical limits of claim anchor's placement min_claim_height = -64 max_claim_height = 319 # Permission level required to bypass claim restrictions (2 = OP) min_permission_level_to_bypass = 2 # Maximum number of claims a single player can own max_claims_per_player = 3 # Minimum distance required between different players' claims min_distance_between_claims = 16 ```Protection
Claims grant their owners a number of protective mechanics that can be activated individually. In addition to activating the protection policy, lists of IDs and Tags can be compiled to indicate exceptions to the rule. For example: by setting `prevent_block_breaking` to `true` and including the tag `c:ores` among the exceptions, ores can be broken by any player. On the other hand, by setting `prevent_item_use` to `false` and `minecraft:bow` as exception ID, only the owner of the claim will be able to shoot arrows. Entities can also be protected from other players' interactions and attacks, however the ownership of pets and mounts exceeds the ownership of the claim (the owner of a horse will be able to interact with it even in other people's claims)Block and Item
```toml # Control whether blocks can be broken within claims by non-owners prevent_block_breaking = true # Lists of block IDs/tags that are exceptions to the block breaking restriction prevent_block_breaking_exceptions_ids = [] prevent_block_breaking_exceptions_tags = [] # Control whether blocks can be placed within claims by non-owners prevent_block_placement = true prevent_block_placement_exceptions_ids = [] prevent_block_placement_exceptions_tags = [] # Control whether blocks can be interacted with within claims by non-owners prevent_block_interaction = true prevent_block_interaction_exceptions_ids = [] prevent_block_interaction_exceptions_tags = [] # Control whether items can be used (ex. eating food) within claims by non-owners prevent_item_use = true prevent_item_use_exceptions_ids = [] prevent_item_use_exceptions_tags = [] # Control whether items can be used on blocks (ex. hoe on dirt) within claims by non-owners prevent_item_use_on_block = true prevent_item_use_on_block_exceptions_ids = [] prevent_item_use_on_block_exceptions_tags = [] ```Entities
```toml # Protect entities within claims from being attacked by non-owners protect_entity_from_attack = true # Lists of entity IDs/tags that are exceptions to damage protection protect_entity_from_attack_exceptions_ids = [] protect_entity_from_attack_exceptions_tags = [] # Protect entities within claims from being interacted with by non-owners protect_entity_from_interaction = true # Lists of entity IDs/tags that are exceptions to interaction protection protect_entity_from_interaction_exceptions_ids = [] protect_entity_from_interaction_exceptions_tags = [] # Protect claim owners from hostile mob attacks within their own claims protect_from_hostile_mob = true ```PvP and Combat
```toml # Prevent PvP targeting of claim owners protect_owner_pvp = true # Prevent all PvP within claims (for everyone) protect_everyone_pvp = false # Prevent projectile damage within claims prevent_projectile_damage = true # Visual effects for blocked projectiles show_projectile_effects = true projectile_particle_scale = 1.0 projectile_particle_count = 16 projectile_effect_cooldown = 100 projectile_particle_density = 1.0 ```Environmental
```toml # Prevent fluids from flowing into claims from outside prevent_fluid_flow_into_claim = true # Distance from claims where fluid placement is prevented fluid_placement_protection_radius = 3 # Prevent fire from spreading across claim boundaries prevent_fire_spread_across_claim = true # Prevent explosions within claims prevent_explosion = true # Visual effects for blocked explosions show_explosion_effects = true explosion_particle_scale = 0.5 explosion_sound_volume = 50 explosion_effect_cooldown = 500 # Prevent pistons from pushing blocks across claim boundaries prevent_piston_interaction = true # Prevent dispensers from working across claim boundaries prevent_dispenser_interaction = true ```Essence System
Through claim essence, a cost of maintaining claims is introduced. As long as this mechanic is active, claims will start with a small amount of essence at placement that will deplete over time. The owner, or anyone who can interact with the claim anchor, can place the designated item to increase the essence level: if the essence within a claim ends, it will deactivate, ceasing to protect the property.Essence config
```toml # Enable or disable the essence system enable_essence_system = true # Interval in ticks between essence consumption (20 ticks = 1 second) essence_consumption_interval = 1200 # Amount of essence consumed per interval essence_consumption_amount = 1.0 # Initial grace period once claim anchor is placed in ticks initial_grace_period_ticks = 2400 # Maximum amount of essence that can be stored in a claim anchor max_essence_storage = 2000 # Amount of essence provided by each essence item essence_per_item = 20 # Item ID for the essence item essence_item_id = "claimorous:claim_essence" ```Permission System
Optionally, “Manage Permissions” can be granted (if `allow_permission_management_sharing` is set to true). This permission allows non-owner players to manage the permissions of other players, otherwise only the claim owner will be able to manage permissions. However, granting “Manage Permissions” to a player will not allow him to further grant the “Manage Permissions” permission ```toml # Enable/disable the permission system within claims enable_permission_system = true # Allow claim owners to share permission management with trusted players allow_permission_management_sharing = true ```Claim Transfer
Claim Contracts can be used by players to transfer ownership of a claim. After crafting them, players can sign them using the item. The owner of a claim can use a signed claim contract on his claim anchor and confirm the transfer in the dedicated screen.Visual Settings
```toml # Show particle borders around claims show_claim_borders = true # Maximum distance at which claim borders are visible claim_border_view_distance = 128 # Size of claim border particles claim_particle_scale = 2.0 # Update interval for claim border particles (in ticks) claim_particle_update_interval = 20 # Density of particles in claim borders claim_particle_density = 1.0 # Colors for different claim tiers (in hex format) tier0_claim_color = "#55FF55" # Light green tier1_claim_color = "#5555FF" # Blue tier2_claim_color = "#CC4444" # Red ```Logging Settings
```toml # Enable logging for claim creation log_claim_creation = true # Enable logging for claim removal log_claim_removal = true # Enable logging for claim modifications log_claim_modification = true # Enable logging for player warnings (attempted violations) log_player_warnings = true # Enable periodic statistics logging log_periodic_stats = false # Interval for periodic stats logging (in seconds) periodic_stats_interval = 3600 # Enable logging for configuration changes log_config_changes = true # Enable debug logging (verbose) log_debug_info = false ```Admin Claims
Admin claims can only be created by server operators using commands. They have their own configuration, separate from regular claims and can override global settings, including different values between length height width. The protection rules in admin claims depend exclusively on which type they belong; each type follows its own rule and can be configured individually. A new admin claim type can be created via the command `/claimorous admin configAdmin Claim Commands
### 1. Create Commands #### Create Cubic Admin Claim ``` /claimorous admin createThese are example config screens:
According to the following example config, in a claim that players do not own:
- they cannot break blocks except grass;
- they cannot place blocks except flowers;
- they cannot interact with blocks except doors and buttons.
Troubleshooting
Common Issues
- Claim creation fails: Check if you've reached your maximum claim limit or if you're too close to another claim
- Protection doesn't work: Verify the configuration settings for the specific protection type
- Visual effects not appearing: Check if particle effects are enabled in your game settings and in the config; also claim monocle must be in your off hand.
Config Validation
The mod automatically validates configuration values on load to ensure they are within acceptable ranges. Invalid values will be adjusted to the nearest valid value.
Would you like an even more immersive experience?? Try Claimorous! along with Lock'n'Pick mod
