[ADMN/SEC] VanishNoPacket 3.14.2 - Invisibility made easy! [BukkitDev]

Discussion in 'Archived: Plugin Releases' started by mbaxter, Aug 16, 2011.

  1. Offline

    md_5

    I understand you may be angry with some of the changes to this plugin, however here is not the correct place to vent your frustration. I suggest you double check your configuration as described above, and if further issues arise, a polite pm to the author may be a better course of action than venting your frustration here.

    Thanks
    md_5
     
  2. Offline

    IAMWIN

    im using group manager and my admin and owner group have the '*' command so everytime we log on we cant unvanish unless they toggle the lightning off which is a pain and i dont want to do ALL of the permissions for 30 plugins just to use something to check on characters n my game... if i do the - -vanish.example will that work with the '*' still in the group or do i have to change it all?????



    yep that worked :3
     
  3. Offline

    Londogne

    Can this interoperate with MobDisguise? As in, if I disguise myself as Notch, then send a fake join, will it say "Notch has joined the game" or "[My IGN] has joined the game"?
     
  4. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı Retired Staff

    This plugin doesn't touch mobdisguise, it would (hopefully, unless mobdisguise does some terrible dark things) say your real nickname not 'notch'
     
  5. Offline

    APhilosopher

    i have alot of plugins, as an op it is so much easier to give myself the *.* perm, this has always been nice, until this update with your new lightning effects, now for the first time, there is a perm that i do not want,

    i tried adding -vanish.effects and -vanish.effects.* to the perms for my group and yet still *.* overrules it and forces lightning enabled anyway, so now my only option is to add (plugin).* for every plugin to my group until i get to vanish, in order to specify only some of vanish perms rather then all

    summary this one lightning feature means i must completly rewrite my perms for the admin group, since *.* over rules -vanish.effect

    it would be nice if this was an option i could just turn off in the config, would make sense too, so much so that it was the first place i looked,
     
  6. Offline

    Mojokojo

    Vanish is not a place to show off his ability to add lightning and explosions in an invisibility plugin.
     
  7. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı Retired Staff

    Ask the folks behind your permissions plugin for help. There should be a way to remove the permission node in one line. You probably ordered it wrong (I've seen a lot of troubles due to ordering lines wrong in permission files)

    The lightning and explosions were actual feature requests. They're great for turning on, scaring the pants off of griefers.

    I would ask you to please stop replying to this thread unless it's a support request.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Jul 14, 2016
  8. Offline

    APhilosopher

    im using PEX which i have hooked into mcmyadmin 2, i added the perm -vanish.effect (note the dash -) wich did not disable it i also tried this perm -vanish.effect.*

    yet still i have that perm and the lightning still occurs,

    is there some other way of typeing -vanish.effect that i have not tried yet?

    as it is when you first log in the lightning effect is enabled (when u have its perm or *.*) and as you say it is most useful for scareing griefers, why then not just set it to auto disabled? if an admin is seeing a griefer that they want to spook its not hard for them to /v t lightning before they /v fj

    and then no one would have any complaints about the feature and no perm rewriting needs be done :D :)

    for now im hotkeying a button to just type /v t lightning /v fj for me both at one press of a key, so i can have my simple log ins back :)

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Jul 14, 2016
  9. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı Retired Staff

    It is auto disabled. Giving yourself "*" means you are enabling it. Don't give yourself nodes you don't want.
     
  10. Offline

    APhilosopher

    but i do want the node *.* because it encompasses hundreds of nodes to just type *.* the first time there has ever been a perm involved with *.* that i did not want, is this plugins lightning/boom effect,, and thats after 2 years of running a server.

    obviously when someone has the perm it is then auto enabled, i said that in my last post, my point is, if you would still leave it disabled even AFTER they have that perm then the ones who want it enabled could enable it themselves with /v t lightning, could also just throw that option in the config,

    as it is, the only way i can now log into my server without lightning and a boom is to
    A: type /v t lightning /v t boom /v fj every time i log in,
    or
    B: remove the *.* perm node from the admin/op group and add these perms instead for the sole purpose of ensureing i do not have the vanish.effects perm
    here is my NEW list of admin perm nodes which will allow me the same ability as the simple node *.* with the exception of being able to disable lightning and booms upon log in

    lagmeter.*
    Orebfuscator.*
    foundboxx.*
    worldedit.*
    trp.*
    nocheatplus.*
    iConomy.*
    dimensiondoor.*
    mcbans.*
    pex.*
    lwc.*
    mcmmo.*
    mobdisguise.*
    worldguard.*
    essentials.*
    worldborder.*
    chestshop.*
    modifyworld.*
    vanish.op


    there, so in order to negate one perm i must remove the all encompessing perm i use now and replace it with 19 perms, and thats if i didnt miss any.


    anyhow i asked you last post
    and just now before posting this post, as if taking a hint from the thought of that question, i went and double checked the wiki for PEX on the issue of negating a perm and found the answer to my issue, here it is burried on this page under sub topic Important File Back-End Notes https://github.com/PEXPlugins/PermissionsEx/wiki/Basic-Permissions-Setup

    "PEX reads the file in a 'top to bottom' manner when checking group and user permission nodes. Similar to a network firewall, once it finds a node that matches what it is looking for, it stops searching. What this means in practice is that if a node gives access to a main group and all subgroups, PEX will find the node that allows access then stop checking, never reaching the negation node."

    this is the answer to the question i asked you last post that you did not asnwer in your reply rather you opted for the snide comment of "Don't give yourself nodes you don't want." theres never been a node that someone doesnt want till this, is there any other plugin out there that uses nodes as the toggle to activate a feature? cause until now i've always seen nodes were to enable the option to toggle the feature not to outright enable it to start.

    that PEX factiode answers my question in that i removed the *.* from my group then added -vanish.effects then readded *.* and now it works to negate that one node. you must put negating nodes in your perms first before you put an enabling one like *.*

    that was the one detail i and so many others were not aware of that caused all this fuss and hassle
     
  11. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı Retired Staff

    APhilosopher

    I'm sorry, but it's not my job to keep track of how to utilize permissions plugins. There are half a dozen different popular plugins and tons of more obscure ones, and I simply can't track how they handle fake nodes (* doesn't exist in bukkit's API), or negating nodes, or granting nodes. If you're unaware of how PEX handles negation, then it's either that you didn't read the PEX documentation or the PEX documentation isn't very clear on the matter. Judging from the number of PEX complaints I get compared to other plugins (nearly none) I suspect it's poor documentation. But again that's something outside of my control. :/

    As for nodes enabling features, that's how mcmmo enables skills.
     
    Justin The Cynical likes this.
  12. Offline

    5000 People

    how to get rid of lightning? i dotn want to burn my fuckign palce down because of one plugin thats for admins not griefing
     
  13. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı Retired Staff

    1) The lightning is fake, doesn't cause real fires. There is a client glitch where it looks like a fire has started.

    2) You gave yourself the permission node vanish.effects.lightning. Remove that node and you're all set! :)
     
  14. Offline

    5000 People

    i do not want to give my self ALL PERMISSIONS NODES except one, i have a tone of plugisn and right now i jsut use "*" coudl make an option to diable it completely in the config plz???
     
  15. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı Retired Staff

    The way to disable it is to not grant yourself that node. Read your perm plugin's documentation for how to do this.
     
  16. Offline

    APhilosopher

    lol

    remove the *.* node from ur perms, then add -vanish.effects.* node after that re-add the *.* node back in, do this in this order and you should have all your perms except the lightning of vanish.

    worked for me anyway

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Jul 14, 2016
    mbaxter likes this.
  17. (For the record, I'm not offend in any way, I know I am far from perfect in my abilities. Tech writing is not my day job. ;) )

    As the person that rewrote large sections of the PEX wiki, the number of people who still ask the same question over and over, as well asking where the wiki is, makes me feel that it's more a lack of people bothering to read the documentation that does exist (good example of this is what you replied to) for PEX as, for better or worse, it does some things differently than other permission plugins, and those things have been mentioned time and time again.

    But that may just be me. Otherwise, spot on with the rest of it. Further discussion of the pros/cons/quality (or lack thereof) of the wiki is OT for the thread, any further comments should be done via PM.

    Thank you mbaxter for a great vanishing plugin, I can't see ever running a server without it.
     
  18. Offline

    AppleDev

    Why when you do /vanish does it send of like 5 bolts of lightning?
     
  19. Offline

    puyttre

    Hi,
    I have a fix for people with problems in the recent update:

    Remove Effects when typing /vanish:
    Code:
    permissions:
        - -vanish.smokin
        - -vanish.explode
        - -vanish.lightningbarrage
        - '*'
    TO FIX IN THE RECENT VERSION:
    Permission nodes have been updated in VanishNoPacket!
    Code:
    permissions:
        - -vanish.effects.explode
        - -vanish.effects.smoke
        - -vanish.effects.lightning
        - '*'
    To exclude all effects easily:
    Code:
    permissions:
        - -vanish.effects.*
        - '*'
    Also, in your config file remove this line:
    effects:
    lightning:
    count: 30

    or set it to 0 (note: will only prevent fire):
    effects:
    lightning:
    count: 0

    **The -vanish.example permissions MUST BE BEFORE THE '*' NODE! (according to the PermissionsEx documentation)

    Stop joining the game vanished / leaving vanished:
    The -vanish.example permissions MUST BE BEFORE THE '*' NODE! (according to the PermissionsEx documentation)
    Your config must look like this:
    Code:
    permissions:
        - -vanish.fakeannounce
        - '*'
    People see vanished people open chests:
    You need to add this permission:
    Code:
    permissions:
        - vanish.silentchests
    Quicklink:
    http://vanishnopacket.github.com/
     
  20. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı Retired Staff

    You have given yourself vanish.effects.lightning


    puyttre

    The effects.lightning.count option will always equal a value at least one, and if deleted will default to 30. So, that section won't help anything.
     
  21. Offline

    littleMe

    I can't figure out how to:
    1. Turn off lightning thing
    2. Fix so so that when you join you are visible
     
  22. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı Retired Staff

    If you are doing eitherof those you've given yourself the permission nodes for it. Read the permissions documentation on this first :) http://vanishnopacket.github.com/permissions/
     
  23. Offline

    littleMe

    Is there a command to toggle lightning thing?
    And what's the config file you have to change so you don't start with vanish? =S
     
  24. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı Retired Staff

    Read the permissions node documentation and only grant the nodes you want. http://vanishnopacket.github.com/
     
  25. Offline

    Squirzy

    I'm getting fustrated.

    I have this is my PEX permissions:
    Code:
        - -vanish.effects.explode
        - -vanish.effects.smoke
        - -vanish.effects.lightning
        - '*'
    
    But Im still being exploded, striked and smoked.................and yes I'm on latest version.
     
  26. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı Retired Staff

    That does sound frustrating. Those are the right nodes. Ask the PEX folks what's going wrong, so they can fix things (I don't use pex, so I can't be sure on the exact setup)
     
  27. Offline

    dannyflame11

    how do you make it so only people who are op'd vanish when join?:)
     
  28. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı Retired Staff

    Give those folks the permission node to join vanished. Here's the full permissions documentation: http://vanishnopacket.github.com/permissions/
     
  29. Offline

    MatthewDMerrill

    How do I take the lightning off?
     
  30. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı Retired Staff

    Better question is, why did you put it on?

    Read the permissions documentation and only assign the nodes you want. ;)
    http://vanishnopacket.github.com/permissions/
     

Share This Page