SimplyVanish
This project has been continued by @jeikobu__
on spigotmc.org (here: @Woozie321). Handover/what of this project page pending.
- New project page: https://www.spigotmc.org/resources/simplyvanish.20252/
- Former front page of this plugin: https://dev.bukkit.org/bukkit-plugins/simplyvanish/pages/less-old-description/
- Former repository (discontinued): https://github.com/asofold/SimplyVanish (https://github.com/asofold/SimplyVanish/network)
you could see invisible players before 1.1-R4 in hacked clients
16:15:12 [SEVERE] [SimplyVanish] hidePlayer failed (hide Oversector1 from AlessioDiaz): null 16:15:12 [SEVERE] java.lang.NullPointerException 16:15:12 [SEVERE] at org.bukkit.craftbukkit.entity.CraftPlayer.hidePlayer(CraftPlayer.java:608) 16:15:12 [SEVERE] at asofold.simplyvanish.SimplyVanishCore.hidePlayer(SimplyVanishCore.java:669) 16:15:12 [SEVERE] at asofold.simplyvanish.SimplyVanishCore.doVanish(SimplyVanishCore.java:432) 16:15:12 [SEVERE] at asofold.simplyvanish.SimplyVanishCore.setVanished(SimplyVanishCore.java:517) 16:15:12 [SEVERE] at asofold.simplyvanish.SimplyVanish.setVanished(SimplyVanish.java:160) 16:15:12 [SEVERE] at asofold.simplyvanish.command.SimplyVanishCommand.onCommand(SimplyVanishCommand.java:127) 16:15:12 [SEVERE] at asofold.simplyvanish.SimplyVanish.onCommand(SimplyVanish.java:150) 16:15:12 [SEVERE] at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40) 16:15:12 [SEVERE] at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:166) 16:15:12 [SEVERE] at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:473) 16:15:12 [SEVERE] at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.java:821) 16:15:12 [SEVERE] at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:781) 16:15:12 [SEVERE] at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:764) 16:15:12 [SEVERE] at net.minecraft.serverhook.NetServerHandlerProxy.a(NetServerHandlerProxy.java:140) 16:15:12 [SEVERE] at net.minecraft.server.Packet3Chat.handle(Packet3Chat.java:34) 16:15:12 [SEVERE] at net.minecraft.server.NetworkManager.b(NetworkManager.java:229) 16:15:12 [SEVERE] at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:113) 16:15:12 [SEVERE] at net.minecraft.serverhook.NetServerHandlerProxy.a(NetServerHandlerProxy.java:83) 16:15:12 [SEVERE] at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78) 16:15:12 [SEVERE] at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:551) 16:15:12 [SEVERE] at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:449) 16:15:12 [SEVERE] at net.minecraft.server.ThreadServerApplication.run(SourceFile:492)
@Zakor1138
Admittedly i had that in mind first, but... i needed the features :)
When i vanish i want to not interact with anything else to just check on stuff, that is why now made the default behavior such that you can do nothing, basically. Further i had in mind letting other players vanish or reappear, that are not wanted to be able to change anything while being vanished.
To solve this:
You set your flags once, such that you can do what you want, they will be saved so that you don't need to set them again.
You can also set up a flag-set in the "flag-sets" section of the configuration, like:
Then you can always restore your favourite flags with "/vanflag *x", so you won't take damage or become target of mobs but be able to do all sorts of things.
So when are you guys renaming the plugin? Oh... So you're not changing the name to, "NotSoSimplyVanish"? Damn, I could have sworn you were heading in that direction.
I liked being able to chat and open doors, place/break blocks etc while being invisible without having to go through any arduous set up (chat flag? what the hell?). For features like these, I could instead use something like "VanishNoPacket" but I wanted a simple vanish plugin and this plugin was exactly that an update ago so why did everything have to change?
@HCMadHunter
Most likely a permissions setup problem...
what permissions Plugin are you using ?
You could send me your permissions setup file (if using a file)...
Hi, I am a noob :). LOL I have installed your plugin and set permissions I know I missed something because I figured out that my guest have the ability to use vanish when they are not to have access to it. I read through all posting and googled to see how to resolve this issue. I guess I must be doing something wrong. using craftbukkit 1.2.5 with this plugin.
Thank You HCMadHunter
@Goldknight5
"Prevented by hooks" should mean that another plugin cancelled the vanishing or hiding action, which is unlikely but not impossible. I had such issue too for a short time once, but it disappeared after one restart.
I need more information in order to see what might be the case:
Further i would need to know:
This plugin is telling me "action prevented by hooks!" It is really making me mad that this plugin is not working! Maybe some instructions of how to fix this would help. Thanks- Goldknight5
@bigscary
2. What version of SimplyVanish and CraftBukkit were you using? There indeed have been changes. And to suppress join/quit messages or add fake ones you need to set the corresponding flags in the configuration, provided your version supports that - if you use the latest pre version (4), those things should work, as i have tested them.
1. The fake-permissions entries are for people that do not use any permission plugins. So there is no need to use these, if you use permissions anyway. Vault can not help there :), but the concept has been very useful in the past also for DarkTrace, to allow fine grained control without having a permissions plugin, and also to test, if problems arise from the permissions plugin or not. There will be a configuration flag soon, to prevent auto-adding extended configuration options like fake-permissions or command aliases on reloading.
3. For dropping items the latest versions support "/vanflag +drop" and /vanflag -drop" to control it.
4. To opt out from auto-vanish you can either deactivate it completely in the configuration, or use "/vanflag -auto" to disable it just for yourself.
If you want to support groups, the best option is to hook into Vault so that you can support many group systems without implementing each one individually. In my opinion, trying to support permission groups directly in your config file will cause you a big headache later, and at best, will result in a config file format that's unfamiliar to many users who are accustomed to handling permission groups via their permissions plugin and its config, rather than individually in each plugin that supports groups. It will be easier for you if you just define the permissions you need, and let permissions plugins deal with assigning permissions by group.
I'm going to update to the latest version, but I just wanted to mention that previously I had a couple of problems:
1. I would log out visible, then log back in and be invisible. 2. After using /reappear, I'd still not show in the player list. /reload wouldn't fix it. 3. Even when invisible, players still get my connect and disconnect messages.
Maybe you're already aware of these and have fixed them. :) If not, maybe it's worth looking into. Thanks again for the cool plugin!
@asofold
I see, thank you very much :)
edit:
just tested it and it works great! thank you!
@Snipe77
Ok i t is added in the "pre-release": SimplyVanish 0.4.0-PRE-4
The configuration is different to what i initially suggested, you have to define "sets" with lists for both players and permissions:
This shows an example similar to the defualt configurations example entries. You can add the permissions leaving out the "simplyvanish." prefix.
@asofold
It would be great to have "fake" permissions.
I hope the update will come soon :)
Thank you!
@Snipe77
Then how would you distinguish between yourself (op?) and other ops ?
It will end at "something like permissions"...
So i will add "fake" permissions, like configuration entries looking similar to:
The difference to using permissions is not so big anymore form there on, though.
So under players you have the action/permission and a list of players.
@asofold I am not using any permissions plugin.
@Snipe77
Creating a ticket is not so bad :) but the messages are few yet, so one can still follow here too.
I am planning to add an op-permissions flag, so ops do not have all permissions by default.
If you use permissions of any sort, that should solve the problem (allow them to vanish but not "simplyvanish.see-all".
If you do not have permissions, then it would be difficult (i could add fake permission entries in the configuration, as i did with DarkTrace, to specify players directly) because you are op and they are op, then how to distinguish....
Are you using permissions ?
An idea:
being invisible to OPs too because I would like to test new OPs and see how they are doing.
info:
to add ingame or config option for being invisible to OPs too.
would help testing OPs and watching them closely.
P.S: I love your plugin and wish to see this option in the future. Thank you :)
P.S.S: does your plugin vanish the player from TAB menu too? ( the players list )
@BarnabyD
No problem, does RSP work with GroupManager+Vault in general?
I am of course interested in such information, also if plugins pose problems for testing, for it is good to know and i can't test every single permissions plugin by myself (at least not rightaway).
@asofold
We use GroupManager, only some Staff are op.
To test stuff I would normally drop into a defualt user and remove my op, but for some reason it now still lets me do the things as I could before, even when reopening mc. I tested it on a different account, all works well.
Thanks, sorry to bother you.
@BarnabyD
What permissions plugin do you use?
Usually permissions should work, if you plugin supports superperms - but that everyone can use /vanish is very strange, i guess that has to do with the permissions setup.
Is everyone op ? Ops can use SimplyVanish by default, currently, i will add a configuration flag for that in one of the next version, though.