Bukkit

@QweSteR2221

your using a permissions system with a wildcard probably, they work fine for me on groupmanager.

perms does not work. all players сan create gates...

Thank you sir, your a gem. This is my personal favorite gate plugin, no commands, nothing super-fancy, just quick and dirty, the way I like it.

Did Cayorion Stop Working On The Plugin ? Its A Great Plugin to Start Off With and If So The Stoped With the plugin can someone else take it plz ?

Yet another followup - i have worked around all my original issues bar the redstone powering - and i would still like some permissions way to make extra fine control of existing gates, but I have gotten around the issues for now -  thanks if you were paying attention.

-----
Hi again - followup on my original post below, solved issue 1, but permissions remain a problem.  Updated notes below -
Original Message:
Hi,
Firstly I like this, pity the name stargate is already taken!

I have two odd issues. And one request.

Request:
I created a stargate dialler - Uses pistons to change block configurations or to break the circle, block combinations vary depending what "Buttons" i press.  Current design gives me roughly 64 dial combinations, although only 4 go anywhere, i have to manually open the gate each time tho - any chance of making the gate open/close when powering the diamond block? It would need to accept power from below to be able to hide the redstone.

Of course this makes permissions tricky - since it would be nice if players can activate/deactivate and travel on EXISTING gates, but if they try to create a new one (with clock or redstone) without permission it should deny them.
(My suggestion is use the clock to "register" a gate maybe(it sorta does this now), then once registered it will work with redstone on/off)  Permissions wise this means, you need a .create(allows register/open gate with clock) .destroy(allows breaking/de-register the diamond block) .travel(allows travelling through) .operate(allows open/close with redstone but should re-evaluate the blocks on open before linking, similar to clocking the diamond block does now, except wont write the gate to file)

The existing behavior where the gate simply collapses if a block changes(by piston movement or redstone powering the lamp block) prior to walking through the circle is fine.

Now my issues -
Issue 1:
My first gates worked fine -
---- I worked out the issue here, the horizontally adjacent blocks to the diamond block must be the same level, so even if you had a step block it breaks the gate from allowing a return trip.   The reason they were one way is i could activate the one with steps next to it, but the steps prevent the return trip working.  Handy thing to keep in mind if you DELIBERATELY want to make some gates one way (Muahahah) just put a step block each side of the diamond.  ( ..... are players started making random gates all over the place (my original 5 gates rapidly became 34+) which leads me to - )

Issue 2:
Permissions!!  i use a fairly recent bPermissions build, but when creativegates loads it says "no permissions plugin found"  which means i have random players everywhere making stupid portals (that go 4 blocks away, or chain linking 5 or more of the same gate to save them opening doors, walking  etc etc) instead of building stairs or using the existing elevator plugin.  I was hoping to make stargates only available to higher rank (ie responsible) players.   

If you struggle with this - option B here, is make a config file, where you can restrict certain actions by user group maybe?  eg (yaml version of this maybe but i am using ini format for my own clarity and sanity)
[general]
accesstype=group (or accesstype=permissions)
opsaccess=true/false (default all ops have full access or not - false meaning they need a group or perm instead)
[permissions] (section ignored if accesstype = group)
default=true/false  (true all permissions default to true and you need to ^.negate)
(false all permissions default to false and you need to give a .permission to use)

[group] (section ignored if accesstype=permissions)
travel=default,technician,moderator,admin (or all?)
create=technician,moderator,admin
destroy=technician,moderator,admin
operate=default,technician,moderator,admin (or all?)

I have many portals, but only 1 of them fails. And that one who fails is made with diamond block and lapis lazuli block.

@Tonkovich

Great news, looking forward to it. :)

I would LOVE to see this updated for 1.2.5... please? :)

Is there a solution to have a difference between 2 wools portals ? I've lot of map connected with this plugin, each map have a color from a wool color. I create a 2 blue wool portals, it works. I add 2 pink wool portals and they are connected with the blue wool portal because the plugin don't care about the wool color, only the kind of material.

I resolve this pb by adding another material to the portal but this is not a nice solution.

Regards, thanks for this plugin easiest than multiverse portal.