Inactive [TP] Wormhole X-Treme - Multi-World Capable Stargates v0.854 [766]

This is now inactive - http://forums.bukkit.org/threads/tp-wormhole-x-treme-multi-world-capable-stargates-v1-011-953.23973/ is where you can find the currently active developed version.




Release v0.854 contains the fix to stop the IndexOutOfBoundsException that happens when 3d shapes have no light blocks. Also contains the fix for 2d gate iris levers (they get added properly again). The Wormhole X-Treme Worlds support is for a version of WXW that is still under development, expect things to break badly if you enable it without the proper version of WXW (0.5, which is not released as of yet).

If this is your first time downloading this please download the zip, it contains the database software we depend upon.
You are also encouraged to read the changelog and readme. Especially the readme.
Basic instruction for use and configuration can be found below.

Major Features:

• Player teleportation!
• Multi-world support
• Permissions integration (As well as some basic built-in permissions)
• Custom 3d & 2d gate shapes
• Iris password protection
• Minecart teleportation
• Help plugin integration

About Wormhole Xtreme:

Get the Source
Donate to my coffee fund (It helps me code faster!)

When I first heard about bukkit I knew I wanted to write a plugin. As I always wanted a way to teleport around I thought it would be fun to write a mod that could do this. I thought writing one like the Stargates from Stargate would be cool.

So I decided I would make my own portal plugin as my first try at bukkit (and really first mod for Minecraft so far).

So here is my release of Wormhole X-Treme!

video (open) video (close)

Samkio made a usage video here, it is a touch out of date but the general idea still works:

Changelog with important entries in bold (open) Changelog with important entries in bold (close)

Changes 0.854

• Updated chunk (un)loading to happen when gate (de)activates and when dial lever state changes happen.
• Fixed iris levers not being added properly with 2d gates. (Oops, guess that code WAS needed)
• Fixed IndexOutOfBoundsException on 3d gate shapes without lighting blocks.
• Hamfisted fix for signs not updating. Now we nuke the sign and build it from scratch every time a gate sign is toggled. Causes a flash, but... who cares. It works EVERY time now.

Changes 0.853:

• Fix for /dial gates breaking when a user who doesn't have dialer permission hit the lever.
• Switched to getTypeId() from getType(), hopefully this works around the getType() == Air bug that might be lingering.

Changes 0.852:

• Added support for upcoming Permissions 3.0.x release.
• Fixed a NPE in 2d shape code dealing with light block positions.
• Added soft dependencies to plugin.yml.
• Minor log format changes for readability.

Changes 0.851:

• Complete revamp of how we handle permissions checks. Lots more case statements, lots less if/else if. Much better. This is what enums are for.
• Added new gate use cooldowns. This feature will only work on complex permissions enabled servers. There are three groups you can assign a player to; 'wormhole.cooldown.groupone', 'wormhole.cooldown.grouptwo', and 'wormhole.cooldown.groupthree'. If you have an '*' on any user/group, remember to '-wormhole.cooldown.groupone' etc. There is a new command to enable, disable, and modify cooldowns; 'wormhole cooldown [true|false|group] <time>', valid groups being 'one', 'two', and 'three', valid time being between 15 and 3600 seconds. There are also Settings.txt options for all of these new settings. Cooldowns are set when a player enters a stargate, not when they /dial. Cooldowns are removed via timer events, and even if the timer event fails, we do a fall back calculation when a player enters a stargate, and gets denied access.
• Added new gate build count restrictions. This feature will only work on complex permissions enabled servers. There are three groups you can assign a player to; 'wormhole.build.groupone', 'wormhole.build.grouptwo', and 'wormhole.build.groupthree'. If you have an '*' on any user/group, remember to '-wormhole.build.groupone' etc. There is a new command to enable, disable, and modify build count restrictions; 'wormhole restrict [true|false|group] <count>', valid groups being 'one', 'two', and 'three', valid count being between 1 and 200. There are also Settings.txt options for all of these new settings.
• Updated the stargate sign dial sign reset code to be more reliable at causing the client to notice update changes.
• Added a thrown exception during stargate 3d shape parsing if the shape doesn't have an exit point. We depend on this location for pretty much everything. If it isn't there, really bad bad bad things happen.
• Now we have more than just Standard as our default shape. We extract Standard, StandardSignDial, Minimal, and MinimalSignDial to the gateShape folder if it is missing shapes.
• Now we don't toggle stargate signs when we start.

Changes 0.850:

• iConomy support removed. I will not depend on plugins that decide to change their package name 5 major versions in and basically give everyone who depended on the package location the middle finger.
• 3d Gate shapes now implemented.
• Custom gate settings now in place (read: per gate material settings). This included the re-addition of the portalmaterial and irismaterial commands. lightmaterial, redstone, wooshdepth, and custom commands newly added.
• Massive internal overhaul, refactorings, cleanups, general goodness and bugfixes.
• Added support for Wormhole X-Treme Worlds. This allows Wormhole X-Treme to offload its chunk loading and world loading to WXW, for worlds that exist in WXW. Requires user to change Settings.txt option WORLDS_SUPPORT_ENABLED from false to true. This option requires Wormhole X-Treme Worlds v0.5 to be installed, and preferably configured for every existing world populated with stargates. If this option is set to true but WXW is not v0.5 (or not installed), WX will not load its stargates from its database.
• Removed many superfluous chunk load requests. Added graceful chunk unload queue when we are done with a chunk.
• Bumped supported version of permissions to include the 2.7 tree.
• Updated help text for new/modified commands.
• Added backwards compatibility, for those users who just don't want to upgrade to 3d shapes.
• Added loads of failsafe settings, for when users don't have any shapes installed, but have stargates already.
• wxidc now only works on non-sign powered gates which have iris activation blocks set.

Changes 0.833:

• Fixed iConomy double(or many many more) charging issue. Tried to do something awesome, turned out to be a bad idea. We'll revisit these kind of changes when 3d shapes are in and I can do some major refactoring and method merges/splits.
• Bumped supported version of permissions to include the 2.6 tree.
• Merged some of the sign click schedule related methods. Should make sign click messages more reliable.

Changes in v0.832:

• Fixed a NPE in new database initialization. Whoops, missing null-check, added.

Changes in v0.831:

• Fixed erroneous messages sent when a plugin is attached to already and WXT receives a plugin event for it. Cosmetic bug, fixed.

Changes in v0.830:

• Water now will not flow over Stargate anythings. No more broken levers and magic blocks of water floating in their place.
• Buckets now will no longer work with stargate anythings. No free water and lava.
• Minor optimizations and code cleanups.
• PORTAL_MATERIAL, IRIS_MATERIAL, STARGATE_MATERIAL, ACTIVE_MATERIAL are all part of gate shape now.
  • All configuration values associated with these are gone now.
  • Gate shapes without these default to
    • PORTAL_MATERIAL = STATIONARY_WATER
    • IRIS_MATERIAL = STONE
    • STARGATE_MATERIAL = OBSIDIAN
    • ACTIVE_MATERIAL = GLOWSTONE
• Updated default gate shapes that come in the zip to include these new values.
  • See gate shape files for more details
• Removed version 1 DB conversion because new design doesn't allow for it anymore.
  • For users this means if you are upgrading from version 0.3 or less to this version you will need to remake your gates.
• Fixed NPE in onPlayerInteract caused by event not reporting the block the interact event was associated with.
• Logic tweak in the find safe teleport code. Should be *safererer*
• Sign powered stargates now can only target other sign powered stargates.
• Fixed so that when coming from a lava portal stargate to a non-lava portal stargate fire damage is canceled still. No more nasty fire after a teleport.
• Added the logic back in to stop people from randomly teleporting when next to the lever of an active gate. The side effect is, when block.getType() fails, gates don't work. Its one or the other.
• Fixed /wxcomplete permission deny issue with stargates on public networks.
• Added ICONOMY_OWNER_EXEMPT option to Settings.txt with a default value of true. When true this option disables the charging of gate owners for using their own gates.

Changed in v0.821:

• Update version of iConomy we build against and test for.
• Fix NPE in old non-shape based gates.
• Added custom StargateTeleportEvent for MinecartMania as we nuke the minecarts before we teleport the player and put them back in the minecart.
• Refactored package to com.wormhole_xtreme.wormhole in anticipation of adding more stargate related projects.

Changed in v0.820:

• Initial support for CraftBukkit Build 600.
• Got rid of the stupid double error that people got by not reading the readme. Now when we parse settings.txt, if the value is integer for the iconomy settings, we change it to a double by simply dropping a .0 at the end of it. Problem solved.
• Lots of optimizations to the distance finding method we were using. Also fixes to the gate shape parsing code. (Thanks lirelent)
• Overhaul of the way we handle permissions internally. More unified approach to the actual permissions checks.
• Gate block protection should now be compatible with plugins like mcMMO. "Should" being the operating word.
• Levers now properly move when used and toggle on and off when stargate and iris are activated.
• All Permissions deny events now log at Level.FINE. Got permissions problems with WXT? Now see what is happening.
• Optimized fire protection. Now we use timer events that go off 2 seconds after gates close. This way we don't have to listen for fire type events 24/7.
• Fixed teleportation dropping people into very unsafe locations. Now we scan for safe place to drop people, if we can't find one we drop the player in front of the DHD. This will also FIX wormholes by setting the stored teleport location to the new clean and safe location.
• We now support using the help plugin along with WXT.
• We now have settings.txt options to hard disable support of iConomy, Permissions, and the help plugin. No longer do we log a warning when unable to find the plugin we depend on. We log at INFO.
• Buttons are no longer really used. If a button exists on a stargate, it will be replaced with a shiny new lever on the first use.
• Lava stargates are *really* safe to use now. For trees even. Not minecarts though.
• A whole host of debugging information has been added at Level.FINE. If you can trigger a bug reliably, set yourself to fine and provide the server.log details surrounding the bug. Not recommended for production servers as well... its exceissive.
• The '/wormhole regenerate' command is partially added. Will regenerate missing activation and iris levers.
• Minecarts work across chunks and worlds now! If you run into a location where it doesn't work, use the wormhole in both directions to correct the wormhole, then try again.

Changed in v0.812:
- /wxgo now works properly when traversing world bounderies. First we quickly pop into the default spawn location for the target world, then from there we go to our final destination. It is a hack, but it is a working hack.
- methodized the code to find closest stargates, and find distance from closest stargate blocks as well as the math to find distance.
- Updated block ignition events to only use proximity style checks. Block ignition event cancellation radius increased to active stargate woosh depth or 4 blocks, which ever is further.
- Updated '/wxcompass' to use new FindClosestStargate method.
- Updated onEntityDamage to use only proximity style checks. On active gates a bubble of no fire damage of either woosh_depth or 4 blocks, which ever is larger, is created. On closed gates a bubble of 2 blocks is created to stop fire ticks occuring right as a gate closes. Stopped caring about potential drowning in stargate. If user decides they want to stand in the wrong side of a gate till they drown, that is their choice.
- Re-added missing CONSTRUCT_NAME_TAKEN error string in ConfigManager. This stops an NPE in 'wxcomplete'.
- Added support for tkelly's Help plugin. Will generate proper config based on permissions type (simple or complex) or lack of permissions plugin altogether.
- Refactored the heck out of iConomy and Permissions support. Own classes in a new package to go along with the Help support. Methodized a bunch of useful functions. Less duplicated code.
- Added some log output for 'wxforce'. Should help combat abuse.
- Ops are now always able to use 'wxremove'.
- The '/wormhole simple' command now refreshes Help entries to the proper permissions after being set.

Changes in v0.811:
- Came up with a proximity based check for stargates in the lava & fire event
cancellation code. Now only 3 block radius around active lava portals
gets its lava & fire events cancelled. STATIONARY_LAVA is safe for players
to use in portals now. For reals.
- Version 4.5 of iConomy is now supported and verified as working.
- Now we actually check for Iris on gate use while in minecart...
- Back to the good ol kick the player out of the cart and stuff them through
the stargate method. Doing a bit of a hackish teleport when going between
worlds as well. We tp to spawn, then instantly to destination. This is only
when starting the tp while in minecart. If minecart is empty and passing
into a stargate that will traverse worlds, we kick the minecart back. Otherwise
it will dissapear into the void.
- Now we cancel block ignite events on a proximity basis, same way we cancel
fire and lava events on player. No more trees bursting into flames near a stargate.

Changes in v0.810:
- Broke '/wxcompass' out into its own class. Removed '/wormhole compass'.
- Broke '/wxcomplete' out into its own class. Removed '/wormhole complete'.
- Broke '/wxidc' out into its own class.
- Broke '/wxremove' out into its own class. Removed '/wormhole remove'. Fixed so it toggles iris to off state before removing gates with iris active.
- Broke '/wxlist' out into its own class. Added no permissions error message. Removed from '/wormhole' command.
- Added command '/wxgo' and broke it out into its own class. Added no permissions error message.Removed from '/wormhole' command.
- Broke '/dial' out into its own class.
- Broke '/wxbuild' out into its own class.
- Broke '/wormhole' out into its own class.
- Added another message for active gates. Now it will say either remote activated, or activated by someone else already.
- Added SIMPLE_PERMISSIONS config option. The default value of 'false' makes permissions node settings use complex mode. While the setting of true sets the plugin to check for extremely simplified permissions. Permission node details can be found in the README.
- Refactored the WXForce class to Force. Hopefully this shuts MSSE up. ^^;
- Moved a bunch of the initial loading out of onEnable and into onLoad. Now we use onEnable only for events that should only happen at plugin Enable.
- Updated '/wormhole' command to have more descriptive errors and built in help. Updated help information for this command as well. Command now has unified messaging string headers. Added new 'simple' option to enabling simple permissions while the game is live. Requires the user to have proper permissions node for configuration in target mode. Removed a bunch of duplicated permissions checks. Only one check is needed at beginning of command call now.
- Revamped readme to reflect important recent plugin package changes.
- Fire damage, combustion damage, and drown events now canceled in stargate. Now LAVA is really a valid portal material.
- Creeper explosions are now canceled when they would cause damage to stargates. This will stop signs and buttons from being destroyed during that mad dash to/from a stargate. ^^

Plugin Commands (open) Plugin Commands (close)

dial:
description: Dial a remote Stargate, unlock IDC with optional password
usage: /dial <StarGate> [IDC]
<stargate> The StarGate to dial.
[IDC] Use optional password to open remote Iris.

wormhole:
description: Wormhole administration and configuration commands.
usage: /wormhole <commandtype> [ARG1] [ARG2]
Valid Commands - 'owner', 'perms', 'portalmaterial', 'irismaterial', 'lightmaterial', 'shutdown_timeout', 'activate_timeout', 'simple', 'regenerate', 'redstone', 'wooshdepth', 'cooldown', 'restrict', & 'custom'.

wxlist:
description: List all Stargates.
usage: /wxlist - List all Stargates.

wxbuild:
description: Automatically Build Stargate.
usage: /wxbuild <GateShape>
<GateShape> The GateShape to build.
After placing a DHD with a button (and sign if wanted) running this command then pressing the button will cause the specified <GateShape> to be built.

wxremove:
description: Remove a stargate, optionally destroy its blocks.
usage: /wxremove <GateName> [-all]
<GateName> The GateName to remove.
[-all] destroys gate blocks too.

wxcompass:
description: Point compass needle at nearest Stargate.
usage: /wxcompass - Point compass needle at nearest Stargate.

wxcomplete:
description: Complete StarGate construction.
usage: /wxcomplete <GateName> idc=[IDC] net=[Net]
<GateName> The name to give new Stargate.
[IDC] Optional password to give Stargate.
[Net] Optional network for Stargate.

wxidc:
description: Gets or sets a gates IDC.
usage: /wxidc <GateName> <optional_set_idc>
Requires being either owner or have wormhole.config
set -clear to remove the IDC

wxforce:
description: Forcefully shut down all gates and/or open all iris
usage: /wxforce <close|drop>

wxgo:
description: Teleport to specified wormhole.
usage: /wxgo <GateName>

Install directions (open) Install directions (close)

New Install:

1. Download the zip.
2. Unzip file into same directory that your craftbukkit.jar exists in. This should put the hsqldb.jar into the lib/ folder, the WormholeXTreme.jar into the plugins/ folder, and the latest versions of GateShapes into the plugins/WormholeXTreme/GateShapes/ folder.
3. Start server
4. (Optional) Stop the server and edit the newly generated /plugins/WormholeXTreme/settings.txt file as needed.
5. (Optional) Edit gate shapes in /plugins/WormholeXTreme/GateShapes/
6. (Optional) If using the Permissions plugin based plugin, set up the appropriate permissions. If using SIMPLE_PERMISSIONS = true remember to use permissions from the Simple Mode list, otherwise use nodes from Complex Node.
7. (Optional) Start Server again

Basic use instructions (open) Basic use instructions (close)

Basic Use:
First off you need to make a stargate. I you can see the design design below - you need the Gate, a Dial Home Device (DHD), and a stone button or lever facing away from the gate on the DHD. The purple blocks are Obsidian, and the Blue has to be air, but will turn to water when the gate is activated.


A real example of a constructed gate:


You MUST make the gate exactly as it is in the picture.

Once it is assembled hit the button ( You need to stand at least one block away from the button for the event to trigger. ) and the system will confirm that the stargate is properly made. If you don't see a "wormhole design valid" message you did not create the gate properly.
If you did see the message, you simply type /wormhole complete <name> to finish and name the gate. A name sign with the gates name should appear on the gate. You can optionally type /wxcomplete <name> <idc=[IDC]> (idc = iris deactivation code, or the code needed to use the gate) - this will make your gate password protected.

Now if you hit the button again it will "activate" the gate to be dialed.

To Dial (after hitting the button) you type "/dial <remote_gate_name>" and the gate will open and fill with water! (You can change the portal material by using /wormhole material) The gates currently don't by default timeout after dialing. If the remote gate has an iris code you will need to type "/dial <name> <idc>" to activate the remote gate.

Hitting the button again from the gate that dialed out will deactivate the gate. Pressing the button on a gate that has been dialed in to will do nothing because you can't activate a gate that is remotely activated. (Tried to keep it just like the show haha).

Name Sign Dialing (Public Gate System):

• NOTE: This is an alternate way to BUILD a gate. Currently existing gates will not work by simple placing a sign next to the activation button. You will need to /wormhole remove first and then re-complete the gate using this system.
• Place a second obsidian "pillar" next to the main DHD and place a sign on it. Put the name of the gate on the top line.
• Gates with this sign can only be dialed via the sign now. You will only see other gates that have a sign.
• Gate without a sign can dial IN to a sign gate.
• AGAIN : If you make a gate without a sign it will NOT be on the list of gates.
• To cycle through possible gates use right click - Sometimes it takes a click or two for it to work
• See here for sign dialer gate example:
• 
• Note - unless you have STARGATE_FULL_ACCESS or "wormhole.remove" you will be unable to destroy any blocks that are part of the gate.
• Networks!
  • If you put any text on the second line of the sign, it will be the "network" the gate is on.
  • You will only be able to dial other gates on the same network as you
  • Currently you cannot change the network, so make sure you type it correctly!
  • By default (if nothing is put on the second line) a gate will be part of the "Public" network.

Basic configuration settings (open) Basic configuration settings (close)

Configuration:

• All configuration is now stored in a file /plugins/WormholeXTreme/Settings.txt
  • All descriptions of the settings will be found in that file with the settings.
• You can change some options while the server is running:
  • /wormhole activate_timeout <optional_timeout>
    • This is the length of time after activating but before dialing that the gate deactivates.
    • This does not affect sign dialed gates.
  • /wormhole shutdown_timeout<optional_timeout>
    • Setting to 0 means portal only closes after something goes through, and then immediately closes.
    • This setting is how long after a player dials a gate before the gate shuts down.

Permissions plugin settings (open) Permissions plugin settings (close)

Permissions:

• This plugin works with the Permissions plugin. (Currently 2.5+ Only)
  • Changing the built in permissions will not change the Permissions plugin at all.

• Without the Permissions plugin you can use the built-in permissions (disabled by default)

• /wormhole perms - for more information
• to enable/disable default perms /wormhole perms active <true|false>
• When built-in permissions are active:
  • Default OPs get all access
  • Default all other users get USE only

Permissions Plugin Nodes: (Controlled by settings.txt - SIMPLE_PERMISSIONS)
SIMPLE_PERMISSIONS = false
Complex Mode:
wormhole.use.sign - lets a user use sign gates.
wormhole.use.dialer - lets a user use '/dial' gates
wormhole.use.compass - lets a user use '/wxcompass' command.
wormhole.remove.own - lets a user remove a gate that they own
wormhole.remove.all - lets a user remove any gate
wormhole.build - Able to build new wormholes
wormhole.config - Able to configure settings like material and timeout
wormhole.list - Able to use '/wxlist' command to list wormholes
wormhole.network.use.NETWORKNAME - Able to use wormholes on NETWORKNAME
wormhole.network.build.NETWORKNAME - Able to build wormholes on NETWORKNAME
wormhole.go - allows user to use '/wxgo' command.
wormhole.build.groupone - Part of build restriction group one.
wormhole.build.grouptwo - Part of build restriction group two.
wormhole.build.groupthree - Part of build restriction group three.
wormhole.cooldown.groupone - Part of wormhole use cooldown group one.
wormhole.cooldown.grouptwo - Part of wormhole use cooldown group two.
wormhole.cooldown.groupthree - Part of wormhole use cooldown group three.

SIMPLE_PERMISSIONS = true
Simple Mode:
wormhole.simple.use - Lets a user use wormholes.
wormhole.simple.build - Lets a user build wormholes.
wormhole.simple.remove - Lets a user remove wormholes.
wormhole.simple.config - Lets a user configure WormholeXTreme settings

Help plugin settings (open) Help plugin settings (close)

Help:

• Currently there are no configuration options for Help the help plugin. It is just plug and play. If you want to change the help text, you are able to do such via the Help plugin override build into the Help plugin.

As always please let us know of any bugs! Just remember, some bugs are in vanilla and craftbukkit itself, so we may not be able to address them easily.


Devs: Lologarithm & alron

 

Yes, that is b271 is build 271. You probably need to update.

I've had good luck with git-Bukkit-0.0.0-404-g51fc7b4-b322 (build 322) using version 0.71 of WormholeXTreme.

 

Im trying to set the permissions in game and this is what i keep getting

When I try to set my permission i enter

After I enter it i dont recieve a conformation and when i try to turn on the stargate i get

I know this would be a lot easier to do with the Permissions Plug in but that is way more complicated than the in game permissions are

 

That typo is my fault - it should be "/wormhole perms indiv <name> <permission_level>" - that old message was from my old format of doing perms. All in all I would recommend using the permissions plugin.
--- merged: Feb 14, 2011 4:36 AM ---
Just released v0.72 - fixing Iris' and making them work! Also lets you use double quotes now to add/remove gates!

 

So it should be

 

Ya, I fixed that permission message to be correct in v0.72 that I just released.

 

Hmm well i just downloaded the update and i still keep getting Invalid Format

 

Works great somewhat.

One bug that doesn't cause any MAJOR problems:

When you dial a gate with an iris in place without giving the IDC password, it dumps the following error. (craftbukkit 322)

Feb 13, 2011 8:46:11 PM org.bukkit.plugin.SimplePluginManager callEvent
SEVERE: Could not pass event PLAYER_COMMAND to WormholeXTreme
java.lang.ArrayIndexOutOfBoundsException: 2
2011-02-13 20:46:11 [INFO] alrondm issued server command: dial "Alron Mount"
2011-02-13 20:46:11 [INFO] Unknown console command. Type "help" for help.
Feb 13, 2011 8:46:27 PM org.bukkit.plugin.SimplePluginManager callEvent
SEVERE: Could not pass event PLAYER_COMMAND to WormholeXTreme
java.lang.ArrayIndexOutOfBoundsException: 2
2011-02-13 20:46:27 [INFO] alrondm issued server command: dial "Alron Mount"
--- merged: Feb 14, 2011 5:04 AM ---
Also I had a wormhole break when one of my users toggled the button a few times after I had just finished dialing.

Looks like it is really easy to get portals stuck in a "remotely activated" state. Just toggle the iris a few times and dial a few gates. Should end up with gates that show the wormhole water. But don't actually wormhole.

 

I figured out the permissions plugin thank you for your help

 

Looks like the big trigger for locking gates is the IRIS. With IRIS in place my gates will lock when dialing from the IRIS location. With IRIS turned off (lever off) they never lock from normal operation. (By locking gates I mean gates that break and have to be re-added)

Hope this helps track down the bug.

 

i was wondering if you could make the installation of a wormhole a little more difficult. It currently only took me 45 minutes

 

The first issue is an easy fix. The second issue, you saying that if you toggle a gate too many times while also toggling the Iris a gate can become stuck activated?

 

If you dial a gate while the IRIS is closed on the dialing side, it locks both gates and requires both being removed and added again (this includes removing the water from the gate itself). The IRIS visually works properly after the lockup too.

The other problem was when an other user hit the gate button a few times after (or during ) my dialing of a gate. Locked the dialing gate and required rebuilding it. Remote gate was fine. No water in it for this type of lockup.

 

Sorry it took so long - what was your trouble?
--- merged: Feb 14, 2011 7:27 AM ---

Well, i fixed the Iris code to not allow you to dial until you have deactivated the iris (which makes sense anyway). I fixed the array index error (just wasn't checking to see if you had sent a long enough message).

I am going to have to spend a little time and see if I can figure out the cause of the other issue. I have a little suspicion of something it might be but I am going to try to actually repro the issue before making sweeping changes without knowing the real cause.

 

Awesome. I'm seeing if I can trigger the second bug a bit more reliably.
--- merged: Feb 14, 2011 7:43 AM ---
Ack, sorry. False alarm on the second one.

Looks like it wasn't a bug(unless this is not a desired feature). My user deactivated my gate on me after I had finished a /dial, then reactivated it. When the user activated the gate but didn't dial the gate it wouldn't let me use the gate until they actually dialed it.

45 seconds later or when the user actually dials, the gate starts working for everyone else again.

 

I also just added something small I hope helps (this will be in the next release). When a gate is "active" (either dialed in or out) the block behind the button will be glowstone instead of obsidian. When the gate shutsdown the block goes back to obsidian. Hopefully this will help debug when a gate is actually stuck in the active state.
--- merged: Feb 14, 2011 7:46 AM ---

That is actually a feature and a configurable one. It is the 'activate_timeout' setting in the settings file. That allows you to configure how long a player has to use their /dial until the gate automatically times out.

 

Yep, it just can be a little annoying when users can cancel a gate you activated and dialed and sit around making the gate unusable by activating it, but not dialing it.

 

It was designed so that someone else wouldn't dial in while you are trying to dial out - I could possibly allow for a value of 0, meaning that the gate is never 'active' until you actually do the /dial. Other people could possibly dial in while yhou are trying to /dial out.

 

Hi...

I have a little Problem with the HSQLDB JDBC driver. Since Yesterday when Bukkit go up to:

This server is running Craftbukkit version git-Bukkit-0.0.0-405-gf77e79e-b323

I get following Severe Problem:

[SEVERE] ERROR: failed to load HSQLDB JDBC driver.

I tried to download the actual Driver from hsqldb.org, but it doesn't works. So i'm wait for the 0.72 Version, but that
doens't work too.

The only other Plugins I'm using are Permissions, Antibuild and the Basic Essentials Plugin.
With the Version 400 it works great, but since then nothing will work.

Hope you can help me, cause i love Stargate and this is my favorite Warp plugin... Warping with Style ^^

Greetings

Seaumais aka Night

 

and the other gate says

but hitting the switch to activate the gate does nothing

 

Attached to the first post is a .zip file that contains the HSQLDB jar file. Simply place that in the main directory with your craftbukkit.jar. At some point I plan to move that to a more standard location like the /lib directory but for now make sure its in the directory with craftbukkit.jar.
--- merged: Feb 14, 2011 8:07 AM ---

What do you mean by nothing? Is there anything in your server logs?

 

Yeah it works... I love you ^^ so for now i can create my gate to P3X-774

 

How do you link a gate to another world? And can you explain the gate dialing system a bit more

Here is my sign

Line1: -Spawn-
Line2: Blank (3 and 4 are the same)

That is the name of the gate on the first line. But right clicking the sign does nothing (There is another gate with a sign as well)

Thanks, This is a great plugin

 

Read the first post, but I can give a quick summary here:

1. creating a sign-dialer you have to place another obsidian post next to the button (before you create the gate). You place a sign on that post and put the name of the gate on the first line and an optional 'network' the gate is on the second line.
2. press the button to finish the gate and now its a sign dialer gate!
--- merged: Feb 14, 2011 8:10 AM ---

Awesome! Feel free to post screenshots/videos of your awesome gates

 

I asked before - how do you link to another world. i.e the nether.

Thanks again

(I wasn't hitting the button before)

 

Well when i try to activate the Gate the switch does not activate and right clicking on the sign makes the message Dialer set to <gate name>
here os what is happening server side

 

Now a nice feature with the whole Iris/IDC thing would be the ability to remotely activate the Iris. Or some kind of gate configurable autolock timer that kicks in when you leave through the gate.

That way I can use my gates without leaving them unlocked when I've left via them.

Just an idea, a feature request, I know, but one doesn't always want to leave their gate unlocked when they are away from home.
--- merged: Feb 14, 2011 8:25 AM ---

What version of craftbukkit? Also, any mods that interfere with the BLOCK_INTERACT event?

 

Can you give the output of /version. looking for the number after the b. Like on mine git-Bukkit-0.0.0-404-g51fc7b4-b322 is build 322.

From the date stamps on all of your plugins I'm willing to bet you're running an old CraftBukkit.

Thanks

 

You need to update your craftbukkit. You are probably running something over a week old becaues that class (BukkitScheduler) was added about a week ago to craftbukkit.

The number in parentheses in the title of this thread is the minimum craftbukkit version I recommend. You can type /version while playing or 'version' in your console to see what verison you are running.
--- merged: Feb 14, 2011 8:42 AM ---

Now that I think about it, maybe I should find out how to setup a 'minimum' version so that people will get a good error message if they are running an old craftbukkit...

 

Might be a good idea. Seems lots of people find a version they liked and have stuck with it.