Documentation
Documentation
Commands and permissions
Each command requires the "ports.[commandname]" permissions node. Everybody has "ports.list" by default, and ops have permission to use all of the following by default.
- /port reload - reloads the config.yml file for this plugin.
- /port create [name] - creates a port with the given name. Its activation region is determined by your current WorldEdit selection and its arrival location is determined by your current position.
- /port delete [name] - deletes the port.
- /port select [name] - sets your WorldEdit selection to the port's activation region.
- /port arrive [name] - sets the arrival location of the port to your current location.
- /port update [name] - sets the activation zone of the port to your current WorldEdit selection.
- /port schedule [name] [schedule] - sets the schedule of the port. [schedule] should be a number greater than or equal to 0. The numbers correspond to Minecraft time - 1000 is one Minecraft hour, 24000 is one Minecraft day, 168000 is one Minecraft week and so on. Examples:
- /port schedule [name] 0 - Makes the port depart instantly
- /port schedule [name] 500 - Makes the port depart every half (Minecraft) hour
- /port schedule [name] 168000 - Makes the port depart every (Minecraft) week
- /port describe [name] [description] - sets the description of the port. The description is used in various places in this plugin - for example, the messages that appear while you are waiting for the port to depart.
- /port destination [from] [to] - sets the destination of [from] to [to] without changing the destination of [to].
- /port link [port1] [port2] - sets the destinations of [port1] and [port2] so that they point to each other.
- /port list - lists all the ports
- /port rename [old-name] [new-name] - renames a port.
- /port permission [name] <permission> - sets the permission node required to use the port. Omit the <permission> parameter to remove the requirement and allow anyone to use the port.
- /port ticket [name] item:data - sets the ticket required to use the port. Users will need to be holding the ticket in order to use the port, and the ticket will be taken from them when they step into the port. Omit the item:data parameter to remove the requirement and allow anyone to use the port without a ticket.
Configuration
When you first run the plugin, a default config.yml file will be copied to the Ports directory in your plugins folder. The file contains the following configuration options:
- port-tick-period: Sets the number of game ticks between each port tick. Increase this if Ports causes lag on your server.
- notify-tick-period: Sets the number of port ticks between each notification. Adjust this if you feel that notifications occur too quickly or too slowly when players are standing within port activation areas.
The file also contains a number of translations, which you can customise. This feature can also be used to translate messages into other languages.
Wheres the node to tp?
@wiinick
It's not yet added. You take a look here for yourself. https://github.com/robinjam/Ports/issues/10
can you update ? to latest RB thx
Needs tickets/warmup times/cooldown times to compete with voxelport, but this is so much better than it already
I have 2 ports linked ( PlotworldA and PlotworldB ) When I have op they work fine. When I dont have op it says You are not allowed to enter this world . ( Both portals are in different worlds ) I did do ports port permission plotworldA / PlotworldB to remove the permissions What am I missing? I use these plugins : essentials , dimensiondoor , pex Its obviously a permission node but I cant find any.
@Dathmineboy
You'll need to give players the dimensiondoor.access.<worldname> permission so that they can change world. More info at https://github.com/grandwazir/DimensionDoor/wiki/permissions
Hello, I tried to do a teleporter from World to Netherworld, doing /port create NetherWorld in some part of the Normal World, and then I go to the NetherWorld and I do /port arrive NetherArrive and it says:
That port is in a different world ('world')
How can I fix it? I would like to do that in this way :c
Greetings!
Here's a few ideas to improve your plugin if possible:
Set train schedule to certain TIMES of day (eg 9am 12am 3pm and 6pm), perhaps via something like /port addtime [port] [time]
Also, integrating this with money systems like iconomy would be great, because pretty much all items are craftable so thereby its practically impossible to make travel very expensive.
FAILING that, add an "amount" parameter to /port ticket so some journeys (to nearer destinations), cost less than journeys to further away ones.
I also think it would be good if there was some sort of cutoff time parameter, so like 30 seconds before departure either it stops accepting new people for transport, or the worldedit region doesnt let new people on, or maybe integrate this with lockette door signs so a trains doors could close and stop new people getting on the train.