Greenhouses#

Greenhouses is a BentoBox add-on to power-up your island world! It enables players to build their own biome greenhouses complete with weather, friendly mob spawning, unique plant growth, and even block erosion!

Greenhouses are made out of glass and must contain the blocks found in the Biome Recipe to be valid. There is a recipe GUI. Once built, the greenhouse can be used to grow plants with bonemeal, and it may spawn biome-specific mobs. If you include a hopper with water in it, snow will form inside the greenhouse when it rains. If you put bonemeal in the hopper, biome-specific plants will grow. Some blocks can also transform over time due to "erosion".

Created and maintained by tastybento.

Features#

• Craft your own self-contained biome greenhouse on an island (or elsewhere if you like)
• Greenhouses can grow plants that cannot normally be grown, like sunflowers
• Friendly mobs can spawn if your greenhouse is well designed - need slimes? Build a swamp greenhouse!
• Blocks change in biomes over time - dirt becomes sand in a desert, dirt becomes clay in a river, for example.
• Greenhouses can run in multiple worlds.
• Easy to use GUI shows greenhouse recipes (e.g. /is greenhouses)
• Admins can fully customize biomes and recipes

How to Build A Greenhouse#

This example is for when you are in the BSkyBlock world. For AcidIsland, just use /ai instead of /island.

1. Make glass blocks and build a rectangular set of walls with a flat roof.
2. Put a hopper in the wall or roof.
3. Put a door in the wall so you can get in and out.
4. Type /island greenhouses and read the rules for the greenhouse you want.
5. Exit the GUI and place blocks, water, lava, and ice so that you make your desired biome.
6. Type /island greenhouses again and click on the biome to make it.
7. Type /island greenhouses help to see other options.

Once made:#

• Use bonemeal to grow small plants on grass blocks immediately in the greenhouse.
• Or place bonemeal in the hopper to have the greenhouse sprinkle bonemeal automatically. Come back later to see what grows!
• Place a bucket of water (or more) in the hopper to cause snow to fall in cold biomes. Snow will fall when it rains in the world. Each snowfall empties one bucket of water.
• Friendly biome-specific mobs may spawn in your greenhouse - the usual rules apply (be more than 24 blocks away).

FAQ#

• Can I use stained glass? Yes, you can. It's pretty.
• Can I fill my greenhouse full of water? Yes. That's an ocean.
• Will a squid spawn there? Maybe... okay, yes it will if it's a big enough ocean.
• How do I place a door high up in the wall if the wall is all glass? Place it on a hopper.
• How do I place a door on a hopper? Crouch and then place it.
• Can I use metal doors? Yes.
• Can I use a trap door? Yes.
• Can I grow swamp flowers with this? Yes. Make a swamp biome and use bonemeal.
• How much bonemeal is used to grow plants? One per successful plant.
• How much water do I need to put into the hopper to make it snow? One bucket of water (just the water) is used up every time it rains. This only happens in cold biomes.
• Can I build a Nether greenhouse? Try it and see... (Actually, you may need permission)
• Can I build greenhouses in the Nether? Yes. You can colonize the nether with them.
• What kind of mobs spawn in the biomes? It's what you would expect, wolves in Cold Taiga, horses on plains, etc.
• How can an admin update the Nether greenhouse to have a chance to spawn Wither Skeletons? Add the mob to the NETHER recipe in biomes.yml — see Customising mob spawns below.

Required Plugin#

This version of Greenhouses is an add-on for BentoBox and will not run stand-alone!

1. BentoBox - make sure you use the latest version!

Installation and Configuration#

1. Download and install BentoBox if you haven't done so already
2. Download the add-on
3. Place into the BentoBox addon's folder
4. Restart your server
5. The addon will make a data folder called greenhouses. Open that folder.
6. Check config.yml and edit to be what you want, note the list of world names.
7. Configure the biomes.yml if you wish (advanced).
8. Type /bsbadmin greenhouses reload in the game to reload the config or restart the server.
9. Done!

To make your first greenhouse, build a glass box and type /is greenhouses make to see what kind of greenhouse you get. Type /is greenhouses to see the recipes.

Upgrading#

Read the file release notes for changes and instructions on how to upgrade.

Player Commands#

Add these commands to /island, /ai. The command label is greenhouse, with the aliases gh and greenhouses.

• greenhouses - opens the recipe GUI; clicking on a recipe tries to make that greenhouse
• greenhouses help - lists these commands
• greenhouses make [recipe]: Tries to make a greenhouse, by finding the first valid recipe or by using the named one
• greenhouses remove: Removes a greenhouse that you are standing in if you are the owner

Admin Commands#

Registered under your game mode's admin command, e.g. /bsbadmin greenhouses or /acid greenhouses. The label is greenhouses, with the aliases greenhouse and gh.

• IDs come from list and can be shortened to any prefix that matches only one greenhouse. An ambiguous prefix is treated as no match rather than a guess, because deleting the wrong greenhouse cannot be undone.
• Everything except tp works from the server console.
• Greenhouse records that cannot be loaded — overlapping, unknown recipe, missing world, no location — are kept in memory with the reason instead of being silently dropped. That is what makes them listable and deletable.
• Records are never deleted automatically. Removing a player's greenhouse without being asked would be worse than a recurring warning.

Customising mob spawns (example: Wither Skeletons)#

Every mob a greenhouse can spawn is defined per recipe in plugins/BentoBox/addons/Greenhouses/biomes.yml, so adding a new mob is just a config edit. Each entry in a recipe's mobs: section has the format:

ENTITY_TYPE: chance:BLOCK_TO_SPAWN_ON

For example, to give the Nether greenhouse a chance to spawn Wither Skeletons, find the NETHER: recipe and add one line to its mobs: section:

NETHER:
  # ...
  mobs:
    ZOMBIFIED_PIGLIN: 10:NETHERRACK
    PIGLIN: 10:NETHERRACK
    STRIDER: 10:LAVA
    ENDERMAN: 5:NETHERRACK
    WITHER_SKELETON: 5:NETHERRACK

This gives a 5% chance per spawn attempt for a Wither Skeleton to appear on a netherrack block inside the greenhouse. The spawn-on block can be any block in the greenhouse — for a more fortress-like feel you could use WITHER_SKELETON: 10:NETHER_BRICKS instead, but then players need nether bricks inside the greenhouse for it to trigger.

Apply the change with /bsbadmin greenhouses reload (or your game mode's admin equivalent, e.g. /acid greenhouses reload), or restart the server. Existing greenhouses pick up the new mob without being rebuilt.

Things to keep in mind:

• All the chances in one recipe must add up to 100 or less. If a new entry pushes the total over 100, that mob is skipped and an error is logged on load (Mob chances add up to > 100% in NETHER biome recipe! Skipping ...).
• Spawning is also limited by the recipe's moblimit and maxmobs values, and by the mob tick interval in config.yml — so a low percentage can feel rare in practice.
• The ENTITY_TYPE must be a valid Bukkit EntityType name; unknown names are skipped with a warning.

Permissions#

A full list of permissions is here.

Permission to use specific biomes can be added in biomes.yml.

For example, the permission for the Nether biome is greenhouses.biome.nether and is set here:

NETHER:

permission: greenhouses.biome.nether

The permission can be anything you like, e.g., a rank permission, myserver.VIP.

General permissions are:#

greenhouses.player:

 description: Gives access to player commands
 default: true

greenhouses.admin:

 description: Gives access to admin commands
 default: op

Since 1.10.0 each admin sub-command also has its own node — greenhouses.admin.list, .info, .delete, .tp, .verify and .reload — all defaulting to op. Operators need no action, but if you grant admin access through a permissions plugin you will want to add them. They were missing from addon.yml entirely before that release, which is why nothing but op access worked.

Translations#