Allow anonymous analytics?

Our cookieless analytics show us which features get used and store nothing on your device. We never sell your data or use it for advertising.

Privacy choices

Choose what ModDex may collect. You can change this anytime from Privacy choices in the footer.

Read the full privacy policy

Strictly necessary Required for the site to work: login sessions, security tokens, and abuse prevention. Always on and cannot be disabled. Always on
Analytics Cookieless analytics through PostHog's EU servers, used only to see which features get used. Nothing is stored on your device, and the anonymous visitor ID resets every day. Needs your consent because usage data goes to a third party. Never used for advertising or profiling. Off by default in the EU and UK.

Datapack Portals

Quick rating

Community listing page, reviews here may not be monitored by the author.

Report a bug to the author How listings work Are you the author?

Datapack Portals

By KyrptonaughtOwner

No reviews yet

Create custom portals using CustomPortalApi with datapacks

Mod Loaders
Minecraft
Shockbyte server hosting: 35% off your first server with code MODDEX35 (opens in a new tab)

About

Description

Datapack Portals

Create custom portals using CustomPortalApi with datapacks.

Inside your datapack create a "portals" folder, this is where you'll put all your custom portals. There is no set limit of allowed portals, as long as there aren't any duplicate frame blocks. See an example datapack here

Here is an example file: stoneendportal.json

 {  
 
       "block": "minecraft:stone",  

    "dim": "minecraft:the_end",  

    "r": 66,  

    "g": 135,  

    "b": 245

 }
  • block: the block used for the frame.
  • dim: the dim id to travel to
  • r, g, b: the color to tint the portal

There are also some optional arguments

  • ignitionType: the type of ignition to use. Options are "BLOCK", "FLUID", "ITEM".
  • ignitionSource: the id for block/item/fluid for ignition of the portal, the only supported block being fire : "minecraft:fire". All items and fluids are supported.
  • returnDim: the dimmension to return to, allows for specifying a location other than the overworld to return to

That is all! Portals will function exactly like vanilla nether portals do portals and stuff

Datapack Portals

Create custom portals using CustomPortalApi with datapacks.

Inside your datapack create a "portals" folder, this is where you'll put all your custom portals. There is no set limit of allowed portals, as long as there aren't any duplicate frame blocks.

Here is an example file: stoneendportal.json

 {  
    "block": "minecraft:stone",  
    "dim": "minecraft:the_end",  
    "r": 66,  
    "g": 135,  
    "b": 245
 }
  • block: the block used for the frame.
  • dim: the dim id to travel to
  • r, g, b: the color to tint the portal

There are also some optional arguments

  • ignitionType: the type of ignition to use. Options are "BLOCK", "FLUID", "ITEM".
  • ignitionSource: the id for block/item/fluid for ignition of the portal, the only supported block being fire : "minecraft:fire". All items and fluids are supported.
  • returnDim: the dimmension to return to, allows for specifying a location other than the overworld to return to

That is all! Portals will function exactly like vanilla nether portals do portals and stuff