Too Many Portals

Too Many Portals is a Beet plugin that enables you to create easily configurable portals between dimensions.

Usage

Add too_many_portals to your beet pipeline

Configuration

The plugin is configured in too_many_portals inside meta

Portals

Example

"portals": [
  {
    "block": "glowstone",
    "activation": "lava",
    "dimension_a": "minecraft:overworld",
    "dimension_b": "minecraft:the_nether",
    "color": "#EFBA30"
  }
]

block – The block that the portal frame is built from. This can be any block but not a block tag such as #logs.

activation – The activation method for this portal. May be vanilla (flint and steel or fire charge), water or lava.

dimension_a / dimension_b – The dimensions to be linked with this portal. Which dimension is which has no effect outside of the folder structure of the data pack.

floor_portal – Whether or not this portal is a floor portal. A floor portal is built as a 2x2 hole in the ground lined with the portal frame block and activated in the same way as a standard portal.

color – By default the portal will have the appearance of a blue nether portal. You can specify your own color with this property. This may be any color hex color such as #FBBE55 or #0BF5. Decimal colors such as 14117309 can also be used. If a texture has been provided it will be colored with this property.

texture – Alternatively you can specify a texture from your resource pack. For example "texture": "foo:block/portal" would point to assets/foo/textures/block/portal.png. Animated textures using .mcmeta files are also supported as well as multiple sizes of textures.

Dimensions

Example

"dimensions": {
  "minecraft:the_nether": {
    "max_height": 128,
    "min_height": 70
  }
}

max_height – The maximum height a portal may generate in this dimension.

min_height – When a portal cannot find a place to generate it will attempt to generate at the translated coordinates of the entrance portal. To avoid the portal generating outside of the world this property together with the maximum height is used to clamp the y-level a portal may generate in this dimension.

Other settings

custom_model_data_start – The custom model data for the first portal, used to avoid conflicts with other resource packs.