Current version: 2.2.4 This project is moving to BukkitDev! Go here! The information on this post is no longer being maintained. This topic is here for historical reference. I would strongly prefer if BukkitDev were used over this, so that I can keep communication all in one place. 2.2 brings a few new features and a ton of bug fixes. Most tickets that were open against the plugin are now closed with this release. Check it out over at BukkitDev! So, I was thinking the other day about how long it takes to travel from place to place. I figured that portals to the nether would be pretty cool when they work, (oh hey now they do) but I wanted a quick way to get anywhere. /warp works, but that is just too easy for users. As such, I decided to write my own plugin to do this. One day later, enter TravelPortals. They're fairly simple to use, though I will admit that I would like a more intuitive interface than using commands. Portals are 3x3, and consist of 6 pieces of obsidian, a door, and a redstone torch for the center. From above, the portal looks like this: Code: n o n o R o n D n o is a stack of two obsidian blocks, D is a door, and R is a redstone torch. n can be any block or air. It does not matter. After you have constructed the frame, place a redstone torch at the bottom. It should tell you that you have created a portal, and fill up with water. Just add a redstone torch! After this, just give the portal a name, and give it the name of another portal for the destination and you're set. As long as the destination portal exists, walking into it will take you straight there. For help in-game, type /portal help. Yes, this does work across multiple worlds. Using /portal help will list all of the commands in game. The important commands are /portal name, /portal warp, /portal list, and /portal hide. Here is a video explaining exactly how to make them, provided by MinecraftZero. Old Change Log (Move your mouse to reveal the content) Old Change Log (open) Old Change Log (close) New changes will be shown on the BukkitDev project. This is no longer maintained. Recent Changes: 1.5_1 - Fixed a small world loading issue. If you ever had issues with multiworld worlds not loading right, this build is for you! 1.5 - moved TravelPortals.ser to the data folder (finally) - also moved travelportals.txt to data folder - more intuitive backup system that should remedy any problems with saves -- new configuration variable; lets you define how many backups of the portals to keep. This should make recovery easy if anything ever goes wrong. - lots of code fixes - if anyone saw all of the misuse of static in the plugin, it's fixed! - A minor typo that may not have even been in a released version of the plugin - Gives a user feedback when just using /portal. Note: Another build may be released in the coming days, but it will have no new functional updates. I just want to work on the documentation a bit; getting a functional release out seemed more important than this. 1.4_3 - Cooldown time is now variable. The config option is "cooldown" and the default has been changed to 8. 1.4_2 - Made hidden portal destinations show up as such. - Fixed a small issue with the included config file. Replace or repair yours if you want both door types to work right. The second instance of door needs to be door2. 1.4_1 - Permissions fix because I goofed up something minor. If you don't use permissions, don't worry about this one. 1.4 - Fix for portals not always triggering in recent versions. - /portal info now shows info about nearby portals, or those named. (Permission node: travelportals.command.info) - /portal deactivate [name] will deactivate a portal given its name. The physical portal will be untouched, but all data related to it will be deleted. This is op only without permissions, and should only be used for cleanup. (Permission node: travelportals.command.deactivate) - /portal export Will export all portals to a text file. The format is: x,y,z,name,destination. There is a new configuration option that will automate this process whenever a portal is made or destroyed. - /portal list is now paginated and shows portal destinations. This looks indescribably better than the old version. - Support for metal doors is now on by default. There is now a second configuration option for doors - both block types can be used to make a portal. If you do not want this functionality, set the second door type to be the same as your first door type, as laid out in the comments in the new configuration file. - Minor changes to the save system; whenever TravelPortals.ser is saved, the older version is moved to TravelPortals_ser.bak, and the new one takes its place. This might help with the random deletions one user referred to. There is also more debugging information available if something happens to go wrong. - Migration to the BLOCK_DESTROY hook; I figured this would trigger when a block was destroyed by anything. WRONG. It is more optimal than the alternative, however. - Various bug fixes, code cleanup, and user output cleanup. 1.3_2 - onCommand fix. 1.3_1 - Block damage fix. (To developers wondering, org.bukkit.block.BlockDamageLevel.BROKEN has become org.bukkit.block.BlockDamageLevel.STOPPED. Your code will compile fine but blocks will not break right.) 1.3 - Configuration file support! (plugins/TravelPortals/config.yml) -- Customize the types of blocks used to construct the portal - Permissions support (Thanks to Cecer) - Minor bug fixes. 1.2 (and its derivatives) - Multiworld support! - Various bug fixes. Download: Latest Version: Download If you want help with this plugin, please provide the following information about your server setup. It will help me figure out what is wrong, and what you or I can do about it. Your failure to include this information in support requests may result in your post being ignored. Help Requests (Move your mouse to reveal the content) Help Requests (open) Help Requests (close) I receive a good amount of requests for support with this plugin. Some of them are better than others; if you do not want to be part of the second category, I will need some information about your server, and how it is set up. Simply telling me "it doesn't work" does not tell me anything. I run the most recent version of this on my own server with around 60 users; I'm pretty sure it is capable of working in at least some settings. Please provide as much of this information as you can reasonably find. If I detail how to get it, I want you to do that! - an EXTREMELY detailed description of the problem (Don't spare any words; I don't mind reading) - Any errors shown in the console - Any errors shown to the client - All of the information from /debug info and /plugins - Server's CraftBukkit build (go to the console and type /version; provide that.) - Any changes in your setup that preceeded the errors - Any other details that could be relevant. Source code is in the dev.bukkit git repository! Please report any bugs via email, or here. Enjoy!