Home›Java›Mods›Schneckenhaus
Schneckenhaus
ModsJava

Schneckenhaus

by Lama06 · on Modrinth

Ever wanted to see how a chest looks from the inside? Ever wanted to take your buildings with you in your inventory?

⬇ Download on Modrinth
Open in MC Java ModsGet it on Google Play →

Schneckenhaus Plugin

Ever wanted to know how a shulker box looks from the inside? Ever wanted to enter a chest? Ever wanted to store your house in your inventory? This plugin has you covered!

Videos

Every snail shell (an enterable block) can be customized using a graphical interface:

If you aren't convinced yet, the plugin also features:

Documentation

Table of contents:

  1. Commands
  2. Custom Shells
  3. Configuration
  4. Permissions

Command System

Shell Selectors

When a command requires you to specify one or multiple shells like /sh tp shell <shell> or /sh info <shell>, you have multiple ways to do so:

Commands

Selections

Selections is a powerful feature, which enables you to search for snail shells using a variety of criteria. Besides, selections make it possible to run other commands on all shells that are selected. Every player and the server console has a current selection, which is empty be default.

Custom Shells

Creating Custom Shells

You first have to build a template for your custom shell type. When the custom shell type is instantiated, e.g. through crafting, a copy of the template is created in the snail shell world.

The template can be built in any world, but it is advisable to build it in the snail shell world. To do that, execute /sh tp world schneckenhaus to be teleported to the default snail shell world. You must build your template at a position where every block of the template has either a negative x or z coordinate. Otherwise, there could be conflicts between shells created by the plugin and your template.

When you are finished building, run /sh custom add <name> <world> <position1> <position2> <item> <ingredient>. name can be freely chosen by you and is used to identify your custom shell type. Renaming your custom shell type afterward is not possible. world is the world where you built the template, for example schneckenhaus. position1 and position2 are the corner positions of your template. Look at these corner blocks and use tab completion to make your life easier. item is the item/block that will represent an instance of your custom shell. ingredient is an ingredient used to craft your custom shell type. You can later edit and add ingredients in the config file.

Using the command /sh custom edit <name> ... you can set some other properties of your custom shell type. You could also change this is the config file.

Spawn Point

/sh custom edit <name> set-spawn

Configure where the player spawns in the snail shell and in which direction he will look.

Initial Blocks

/sh custom edit <name> add-initial-block <position>

/sh custom edit <name> add-initial-block-area <position1> <position2>

If you want a block to be copied, but you want the player to be able to break it and replace it afterward, configure the block as an initial one.

Menu Block

/sh custom edit <name> set-menu-block <position>

Clicking this block will open the snail shell menu.

Exit Blocks

/sh custom edit <name> add-exit-block <position>

Clicking one of these blocks will make the player leave the shell.

Block Restrictions

/sh custom edit <name> set-block-restrictions <position> [<restriction1>] [<restriction2>] [<restriction3>]

/sh custom edit <name> set-block-area-restrictions <position1> <position2> [<restriction1>] [<restriction2>] [<restriction3>]

/sh custom edit <name> clear-block-restrictions <position1>

For every block in your snail shell, there is a list of block types, which is called "block restrictions".

If this list is empty for a block, it means that there are no restrictions, and that the player can break the block and place another block at this position. Actually adding a block as an initial block (using /sh custom <name> edit add-initial-block), will under the hood set the block restrictions list for that block to be empty.

If the restriction list of a block is not empty, that block's type must be contained in the list.

Players won't be able to place/break blocks if this invariant is not fulfilled after that. Besides, the repair system also enforces this.

If you don't explicitly specify the restriction list for a block, the list's default value depends on whether the block is an air or non-air one. If it is an air block, the restriction list defaults to an empty list, meaning that players can place anything they want at that block position. If it is a non-air block, the restriction list defaults to a list only containing the block type of that non-air block. This means that players can't break any blocks that are part of the template by default.

The default values can also be changed by using /sh custom edit <name> set-protect-air true. If the protect_air property is set to true, the restriction list of an air block in the template will default to a list containing only air. Therefore, players can't place blocks in the custom shell unless they are explicitly allowed to do so at a certain location.

Exporting Custom Shell Types

Run /sh custom export <name>. Copy the file created in the plugins/Schneckenhaus/export directory. You can share your creations on our Discord server.

Importing Custom Shell Types

Place the file to import in the plugins/Schneckenhaus/import directory. Move to the world and position where you want the template to be placed. It is recommended to place your template in the default snail shell world. To do that, type /sh tp world schneckenhaus to be teleported to this world. Now make sure that your x and z coordinate are both negative, and that you are far enough away from positive x or z coordinates (e. g. x = z = -100) This is important because if you place the template too near to other shells (which always have positive x and z coordinates), the template's area and the shell's area could overlap. Now run /sh custom import <filename> as <name> name will be the alias you use to refer to the newly imported shell type. Custom shell types can't be renamed afterward. After importing, you can use the crafting recipe (see config file) or /sh create custom template <name> to create instances of your custom shell type.

Configuration

Shulker / Chest / Head Shell Configuration

# This documentation applies to chest and head shells accordingly
shulker:
  # whether shulker shells can be crafted
  crafting: true
  # ingredients needed for crafting besides a (colored) shulker block
  ingredients:
    - item: 'minecraft:spyglass'
      amount: 1
      # model refers to the custom model data attached to an item (used to create custom items)
      model: null
      
  # the size if no size ingredient is used
  initial_size: 4
  # the maximum size that can be achieved through adding size ingredients
  max_size: 30
  # can be optionally added to the crafting recipe to increase the shell's size
  size_ingredient: { item: 'minecraft:gold_ingot', amount: 1, model: null }
  # how much the size will increase if one size ingredient is added
  size_per_ingredient: 2

  # the maximum size that can be achieved through upgrades
  max_upgrade_size: 30
  # used to upgrade the size in the snail shell menu
  upgrade_ingredient: { item: 'minecraft:gold_ingot', amount: 1, model: null }
  # how much the size increases per upgrade
  size_per_upgrade_ingredient: 2

  # number of ticks between color changes in rainbow mode
  # this is also limited by shell_instances_sync
  rainbow_delay: 60 
  # can be added to the crafting recipe to enable rainbow mode
  rainbow_ingredient: { item: 'minecraft:clock', amount: 1, model: null }

Custom Shell Configuration

NOTE: While it is possible to add and edit custom shell types through the config file, it is way easier to do so by using the commands described here

custom:
  # name of your custom shell type, don't change this unless you know what you are doing
  portable-garden:
    item: minecraft:birch_wood # the item / block representing this shell type
    crafting: true
    # ingredients needed to craft this custom shell type
    ingredients:
    - {item: 'minecraft:birch_log', amount: 64, model: null}
    - {item: 'minecraft:birch_sapling', amount: 1, model: null}
    - {item: 'minecraft:bone_meal', amount: 16, model: null}
    - {item: 'minecraft:moss_block', amount: 32, model: null}
    - {item: 'minecraft:spyglass', amount: 1, model: null}
    template_world: schneckenhaus # name of the world where the template for this shell type is placed
    template_position: -30 0 -30 -20 10 -20 # area of the template
    protect_air: false # whether players can build anywhere inside the shell by default
    block_restrictions: # see the section about creating custom shells for a detailed explanation of what this means
      -25 1 -25: ['minecraft:cauldron', 'minecraft:lava_cauldron', 'water_cauldron']
    spawn_position: {x: -188.50940344422307, y: 122.9375, z: 219.30000001192093, yaw: -18.117798,
      pitch: 3.7506914}
    # clicking one of these blocks teleports you back
    exit_blocks: [-189 124 218, -189 123 218]
    # opens the snail shell menu
    menu_block: -188 123 218

Home Shell Configuration

If home shells are enabled, players will automatically receive a new shell when they join the server and don't already have a home belonging to them. The player must have the permission schneckenhaus.home_shell (which is false by default). If players additionally have the permission schneckenhaus.never_homeless (which is true by default), it is impossible for them to lose their homes. Because if they lose it, it will be given back to them on rejoin / respawn.

Examples:

home_shell:
  type: shulker,
  size: 16,
  color: white
  enter_permission_mode: everybody # this can be specified regardless of shell type
  build_permission_mode: whitelist # but is not repeated for the following

home_shell:
  type: chest
  size: 16
  wood: birch

home_shell:
  type: head

home_shell:
  type: custom
  template: your-template-name

World Configuration

Example:

worlds:
  # name of the world
  schneckenhaus:
    fallback: true # whether this is the default world for snail shell creation, can only be true for one world
    biome: 'plains' # biome of the void world, this value is only used when newly creating the world, not for already existing ones
    time_sync_world: world # will sync the time with another world
    conditions: []
  schneckenhaus_homes: # for example, a second world that should contain all home shells
    fallback: false
    time_sync_world: world
    conditions: # at least one of the following conditions must be true for a shell to be created in this world
      # example condition: all shells created by the home shell system will be created in this world
      type: creation
      creation_type: home

Shell Conditions

Shell conditions are YAML objects that can be evaluated for shells that are being created or are already created. Using these conditions, you can enable some features only for some shells. There are multiple types of shell conditions. If you have to specify a list of conditions, usually at least one has to be true.

Examples of the different condition types:

type: shulker
size: {min: 5, max: 10} # optional
colors: green, red, white # optional
rainbow: false # optional

type: chest
size: {min: 5, max: 10} # optional
wood: birch # optional

type: head

type: custom
template: your_template_name # optional

type: creation
creator: 7370723c-1f89-4e7c-a9fe-30ba8b4f0ae3 # optional
creation_type: crafting # optional, can also be command or home
permission: some.permission # optional, permission which the creator must have, 
                            # can only be checked for online players

type: tag
tag: some-tag-name

type: not
condition:
  type: shulker
  size: {min: 10}

type: and
conditions:
  - type: shulker
  - type: creation
    creation_type: crafting

Miscellaneous Config Options

# if enabled, the chunks of a snail shell stay loaded if it is in an online player's inventory or placed in a loaded chunk
chunk_loading:
  enabled: true
  conditions: []
  delay: 100
# if enabled, hoppers can be used to transfer items into snail shells and out of them
hoppers:
  enabled: true
  conditions: []
# this system handles animations (rainbow mode) and manual color changes
shell_instances_sync:
  enabled: true
  conditions: []
  delay: 20
  shells: true
  placed_shells: true
  placed_shells_range: 32
  items: true # animate items in inventory
  dropped_items: true # animate dropped items
  dropped_items_range: 16 # max range near a player
# if enabled, players can't break other players' snail shells
# there can be exceptions to this via permissions
theft_prevention:
  enabled: true
  conditions: []
# will prevent exploits like using pistons / ender pearls etc. to escape a shell
escape_prevention:
  enabled: true
  conditions: []
  delay: 20
# will revert even the most severe kinds of damages to snail shells (WorldEdit etc.)
repair_system:
  enabled: true
  conditions: []
  delay: 200
# players will be teleported here when leaving a shell, but no exit location is known
# set to null to use world spawn
fallback_exit_location:
  world: world
  x: 0
  y: 80
  z: 0
  yaw: 0
  pitch: 0
# don't change this
data_version: 3.0.0

Permissions

Quick facts

Install steps are the general flow for this file type — see the MC Java Mods guides for the full walkthrough.

Verified by MCModsHub

These come from our own check of the pack file, not from the source page.

Explore more

All Mods for JavaAll Minecraft Java modsJava mods for 1.21