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

Discussion in 'Inactive/Unsupported Plugins' started by Ben Echols, Jan 24, 2011.

  1. Offline


    This is now inactive - 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)

    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)

    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; '', '', and ''. If you have an '*' on any user/group, remember to '' 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.
      • All configuration values associated with these are gone now.
      • Gate shapes without these default to
    • 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. :p
    • 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)

    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.

    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'.

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

    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.

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

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

    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.

    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

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

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

    Install directions (open)

    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:
    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:
    • 2011-01-25_02.15.31.png
    • 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)

    • 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)

    • 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)
    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 - 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 - Able to use wormholes on NETWORKNAME - Able to build wormholes on NETWORKNAME
    wormhole.go - allows user to use '/wxgo' command. - Part of build restriction group one. - Part of build restriction group two. - 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 Mode:
    wormhole.simple.use - Lets a user use wormholes. - 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)

    • 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

    Attached Files:

  2. Offline


    I was just moving a piece of information I found over there to here for those who didn't see it. Even if it helps one person I think it is worth doing. Doing something is better than doing nothing and considering I took the time to bring it to a thread I don't/probably wont be using just to be helpful I'd appreciate a slightly more polite response in future.

    I've sung your praises in the past @Redyugi while you were maintaining here but perhaps my opinion is misplaced judging by your "insult" to me. Also as far as being stupid a word of warning, you should be careful who you are rude to in this community. Common courtesy and manners go a long long way.
  3. Offline


    I have been playing with Linux since I was 13. But I know many who don't know what Linux is, and couldn't follow those instructions easily.
    I didn't say it wasn't useful. I would use it.
    I wasn't trying to insult you. It was an observation. And the person whose praises you are singing hasn't been using manners and courtesy, so please don't say that to me without saying it to him. I am usually very kind, but my pain meds make it hard to say what I really mean in the way I want it.

    Again, guys, lets just leave this thread to die. It has run it's course, and unless I or someone else besides lycano fork this, you should only be using his thread.
  4. Offline


    I'm aware you have a broken/fractured/damaged leg in some way... however I don't take kindly to being called stupid (especially for helping). Last time I checked "an observation" doesn't include a "Dont be stupid". A simple apology would have been better than an excuse. I'm fully aware of what medication does (it's my job). That is all.
  5. Offline

    Psycho Robot

    Don't be stupid.
  6. Offline


    I don't see any insult from him to you in this thread at all...
  7. Offline


    Hey i have a problem. When i go trough the stargate i get kicked and it says: You moved to fast, hacking?
    Please help me with this problem!
  8. Offline


    @Mentioum First of all i want to thank you for your support. Im glad that even one in this thread sees the greater good than riding on a path for excueses and licensing reminders.

    Note: Everyone who reads past this line should read carefully and slow and clear its mind to be as much as neutral as possible. And read at least the last line ;) and keep in mind this is not against you this is one explanation and background info. Not meant to insult anyone!

    (Im grabbing this just for an example. The text below applies to all named.)

    K maybe there was a slight misunderstanding in what you read and what i ment. Let me explain it slowly.

    In my post about "dont giving permission to fork ___AAAANNDDD____ release it here in the forums as a simple copy with just under the same name including my work done to it"

    I can say this because this is a community and see example later on. Other rules apply here. Shurely you can fork it and modify it in the terms of the GPL and post it elswhere on your page or whatever cause i assume if you submit your forked project here with the same name under my namespace that your submission would be denied. @CuZnDragon was stating "meh its GPL i can do whatever i want" No you cant! The same goes for you @but2002 .

    You can modify the program the source an redistribute it but this doesnt include the namespace because this is java legal stuff and my right to say so and is not included in GPL. Thats because they name it "program" not source.

    Many ppl dont understand this term. Seems like all of them who just say "its GPL i can do what i want". Also there is another link in the GPL section "Fair use"

    Is it fair to just copy my work knowing that maybe some users may be confused cause of the naming and spam each other with different error messages? Cause this would be the case! You would receive error messages from my fork and i would receive it from your community. Thats because this is a community not a simple google code hoster or github.

    (It is fair to ask the author first for permission or offer suggestions first not acting like "i dont care i just do" otherwise it will probably end up like in Drakias thread (Stargate plugin))

    Example and background for namespaces: de.luricos.bukkit is my namespace i've chosen. As this is my namespace i clearly stated with this sentence (and i have full rights say so) "dont use my namespace i dont give you the permission" because usage of my resources is not GPL just the program and source code "the program / functionality". You are free to modify/redistribute the source wich means you can copy the whole stuff and publish this under another fork doing modifcations and stuff. I thought you would know what i mean when i say so but it seems you didnt got the point.

    But and now comes the tricky part. (e.g. namespace, usage of resources) There are restrictions.
    The pom.xml is not a program its a script that advises maven to compile the program thus informations in it like my namespace my resource link to my private jenkins server and artifactory are restricted to my use only. Shure its public but that is just because i decided to let this public for easy publishing not for abuse. I could furthermore add authentication methods to prevent this from happening thus they had to enter a password or username.

    In addition to this if you dont change the pom.xml, package.xml, namespace and publish your simply forked project others would compile it with maven and fetch their dependencies from my server. Fair hum?

    I can say "you are not allowed to do so" or just changing my repo-s name with a random trigger to let it change every x times. But im diving away from the point ... the main part is as i said namespace/ressource usage. Did anyone just thought about that a minute? NO! "Its GPL i can do whatever i want ..." meh please all of you who said that please think one step further and ask yourself one question "what would that mean if it would really be that way".

    Conclusion: You are free to start your own fork but you have to change namespace and naming when you want to go public and maybe accept the fact that the same name would not be accepted in plugin submissions. Only because i have permission from the author this was accepted.

    Furthermore changing all maven descriptors would be correct and needed. Additionally if you fork it you would loose minecart mania support or you have to ask him if he adds support for it.

    In addition to that just think about the work you may have to do if you want to apply my changes every time i do an update. You would be forced to apply them manually or maintain it by yourself.

    If you decide to do so good luck with it. You could just have asked me "Do you plan to integrate a converter later?" As i said i had to push this release cause there was need for it and i wanted to get rid of bugs first. Usability is later added after refactoring/code improvements.

    Personal feelings:
    Im feeling a bit sad about this outcome currently. I thought continuing an almost dead plugin by offering my support and ressources would be a great addition for the communnity so they can use it again. Plus those who have problems could just simply contact me via IRC, conversation, Github .. plently of ways to contact me ... but instead yours prefer to battle each other instead of working together :/

    You remember? I am open for suggestions im not that douchebag who simply says "Go away this it is my work i decide" No this is for the community and i do this because its fun and i like to code. Furthermore i clearly stated who are the authors and that all credit goes to them not me. Thats why i call it maintaining not "my plugins".

    Shure i have spent hours of work in refactoring and i will probably spent more in it but well who cares i decided to do so and its for a greater good. When this is done the plugin will be more flexible, faster, structured! and contain lesser code and can be maintained by someone else if there is a need for it.

    End note: i hope you just dont start arguing about some details/different opinions if you have something to say about it i suggest all of you to contact me via conversation. All who are intresting in complaining about some details regarding to GPL can do so i dont want to fight a war here in this forum thus currently there are four involved not the whole community.

    Suggestion: Start a conversation to not fill up this thread about too much offtopic stuff.

  9. Offline


    Whoa, this blew up a bit over the weekend... Just my 2p:
    • Someone asked if I wanted to maintain a forked version of 0.854. Sorry, I don't have the time to maintain this plugin, cool as it is.
    • Best of luck to @lycano with it. Although I'll be holding off on using it till a few wrinkles are sorted out (mainly SQL conversion of gates - I have many - and Minecart Mania support, which I understand Afforess is working on)
    • But give lycano a chance. And for anyone else who is considering forking it - you have the right to do so (it's GPL software after all), but you don't have the right to call your forked software Wormhole X-Treme, or use lycano's Java namespace.
    • Chill out, everybody.
  10. Offline


    Uh...dump the data, setup the new database, convert, re-import.

    I don't know, since that will vary based on your skill as a developer. If you're just writing the code to scratch your own itch that's fine. However, no matter why you're writing it once you have released it and offered it up for others to use there are some generally accepted practices for doing new software releases. You are free to violate them, but you have to understand that it will provide a disincentive for using your software, and if nobody is using it - what exactly is your motivation for writing it?

    Sorry, this just doesn't matter to me. Doing this just means instead of having a self-contained Minecraft application that I can quickly and simply move around I now have to tie it to a local mysql install, which I now also have to maintain and backup - and potentially migrate should I need to move servers. It also increases the hardware requirements for an installation.

    Because the issue is (first and foremost) the way you implemented it, not that you did it. Specifically that you simply made wide ranging and radical changes in a single release - including the backend - which also made it incompatible with previous releases and required reworking all of the stargates in a given world.

    Well, not to be rude, but I don't believe you really have the rights to say you can't re-publish. This code has to be released under specific terms to be posted on GitHub, so your rights to control how it is used (especially in a fork) are severely limited.

    Obviously, if it were to fork and continue the right thing to do would be to label it as a fork, and give it a new name to avoid any confusion between the two. You are correct that should a fork be made, reasonable efforts should be made to avoid confusion that could result in either project being asked to support the other's plugin.

    EDIT: I saw where you posted below and clarified your position. As I noted here, yes, using different namespaces/resources, and a different thread and name are all obvious needs. However, you were not exactly clear, and you can't take an attitude with people for objecting when you state you do not give permission to publish a fork here, when that could easily be taken to mean "in the forums". You act offended people don't understand you, but lets be honest, your english is not exactly easy to follow. I assume it's a second language for you, and that's fine, but you're going to have to have some grace with people who are trying to understand it.

    Heh. That's not an attack, it's not even close. I simply pointed out that you made some unwise choices in the way you handled this release, and as a consumer of the product you've created it's not appreciated. In addition, I don't particularly like the direction you're taking the plugin. That's my own opinion, and others may not agree. If they want the changes you're going to then that's great. I don't begrudge you the right to take this in your own direction or others their right to appreciate and enjoy that end product.

    In the same way, I am free to have my own contrary opinion, and to prefer to have a plugin that follows in the path of the one I was already using, that is self-contained and whose developers are committed to less radical changes where possible, and ensuring confidence in a stable upgrade path in the long term.


    Thank you for that. You're right, that's good and useful information.

    @lycano, you should consider updating the primary post on this thread to have that information for people downloading this.

    @desht, thank you for the work you did. I completely understand your not being able to take this on. No worries.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Jul 18, 2016
    Redyugi likes this.
  11. Offline


    766 -> inactive
  12. Offline


    @Shamgar i cant update the primary post cause im not the owner of this thread.
  13. Offline


    @Shamgar well said. @lycano we do appreciate all the work you have done on the plugin and keeping it alive as you have previously stated. What we don't appreciate is your attitude, not necessarily your product. The message I am getting from all of your posts thus far is "screw you guys, I don't care what you think." Whether or not that was your intention, it is how me and several others are probably taking it. If you really want the community to step up and work together on this as you claim, then I am sorry, but that is not a good position to take. Anyway, that's just my two cents.
  14. Offline


    @pachex what? did you even read my post? is this because Shamgar repeats stuff that i didnt even said and you read only his posts?
  15. Offline


    You can't claim he repeats stuff you didn't say, considering he's quoting your posts (perhaps not the entire post at once, but that would just be rude and cause gigantic quote pyramids and nobody wants that, and the originals are obviously right there).
    So, by switching to sqlite/mysql, that means you don't have to package extra files (ie: hsqldb.jar or whatever it was called in that /lib/ folder)?
  16. Offline


    Why is it that i get disconnected from my server?.. "It says: You are moving to fast! Hacking? :("
    Please someone help!
  17. Offline


    You sir, need to go to lycano's new thread, and get the new version, and stay off of the INACTIVE one. :)
  18. So I didn't check this for a long while, and then I just popped back in and saw this crazy **** storm. What happened to Alron and Lolgarithm?
  19. Offline


  20. Offline


    Since you dragged me publicly into this follow up post I am responding in kind.

    If you are going to quote yourself you should actually quote what you said and not what you meant. It wasn't just what you said but the way you went about saying it.

    Also I did not say he could do whatever he wanted to, the GPL restricts him the same way it does you. I just said you couldn't stop him from forking it and publishing his code. I don't work with java so I have no idea what would be involved in forking a java project. But I work on other projects and I am on one that forked so I am aware of the work that was involved in forking it. Much was similar to what you ranted on about. Changing the name, setting up the repository etc.

    I said nothing about the work you did or how you went about it. I may still use your mod if I decide it is worth it for me. I was just offended by what and how you said about the forking.

    I won't respond to the rest of what you said as it isn't relevant to me.
  21. Offline



    I have a problem when I use the stargate. I'm kicked. That's said me : you move too kickly (hacking).
    What's the problem ? Is the problem become from my server or is it from your pluggin ??
  22. Offline


  23. Offline


    ok thank you NightKev to answer me :)
  24. I might look abit like a noob now, im hiring a server from Clanfroge and i got Wormhole E-xtreme & Wormhole E-xtreme world. so i created another world and it works fine as OP but for evryone who got rank thrue the Permission wont keep it in the new world and they cant use the Gate. so they get stuck in the new world. got any idea how to fix it? ive been trying and looking for days now.
  25. Offline


    @dannedemon This plugin's been dead for a while. Go to the new thread for the updated version.

    Don't ask me for links, use search!
  26. Offline


    i have noticed that the newer permissions cause a bit of a problem with multi-worlds, even when going to the nether on this one server i play on people tend to lose privileges my suggestion would be to check with the permissions plugin you use and maybe trying to set up permissions for that world as if it were seperate (btw idk how to do that last part)
  27. Offline


    Sorry for the necro post.
    Any chance of updating this?
  28. Offline


    Read the first line on the first post...
  29. Offline


    Next question, any chance on someone taking it over?
  30. Offline


  31. Offline


    say i wanted to make the iris out of lapis lazuli how would i do that?

Share This Page