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)
@Sigong
For "vanilla-style" messages without special prefixes it is already possible, you just have to enable it in the configuration.
Below is a part of the default configuration, you just would set then enabled flag in the "fake:" section to true, and it will show that message. By default the yellow vanilla messages are used, but it is possible to set other colors or use %displayname instead of %name.
You should add a toggleable fake leaving message. Other than that it's awesome!
gonna try this vanish !! see how it goes,
ps:keep it simple and nice like it is !!! :)
@asofold
lol that's funny. i hear ya man. this is hobby stuff so life gets in the way a good bit i'm sure. We are getting things figured out. I dunno if i was just overlooking things but it took a good bit for me to get the propper permissions setup to allow full control to my staff. Seems to work as intended now though.
Thanks again for the new features. Can't bitch to much as there are plenty of authors that dont update much at all :)
Digi
@Digitalink2008
Yes !
I should have added a clear notice about how to quickly restore the old state, though i did not get too many requests, which at 3000+ downloads for a version seems almost surprising, i was expecting more complaints faster. Still it seems to be users of the first hours complaining, in any case i take this seriously.
I intended to invest a little more time into this transition, but also got caught with other stuff a bit, so could not bring in the things that make ingame use most efficient.
So i will add configurable presets for the default flag states to allow for very simple use according to the servers needs, and i will also consider to use permission based bypasses that are active when flags are toggled on , so that one can differentiate a good bit who can do what when vanished.
My initial intention was not to make it "simple" in the first place, though that makes sense 100%, and yet i can claim to have called it SimplyVanish and not SimpleVanish, but i will not try to make jokes on the users of this plugin, be sure!
SimplyVanish now renamed DifficultlyVanish.
Ok, now for some serious talk. I like the ideas here asofold but the execution has gotten in the way. I think it would serve you well to set the "defaults" to allow what we were used to expecting. You've done a lot of work and it really looks cool but i think we were ( or at least I was ) caught off guard and are scrambling to get our admins / mods back to the state we had them at.
Thanks for the hard work man :) Digi
@hawkfalcon
I have no idea what you are referring to, but i guess it has been my breaking my own paradigm "all additions from now on are thought of as configurable add-ons", while i was using the paradigm "break things!" to have a consistent out of the box thing.
I am planning to bring in configurable default flag states, such that a normal /van call or /vanflag *clear wil always restore that configured state instead of the "out of the box defaults". This and possibly other adjustments should make it easier to ensure ease of use under different scenarios of use.
@hawkfalcon
Could you be more specific ?
Maybe it wil influence the future design ...
The decision to have vanish prevent everything will probably not be changed, for it is the only consistent approach that i can see here, but i might adjust other stuff to make it more simple to differentiate for different groups. One example is bypass-permissions for use with -cmd as a flag.
Very annoying update, I must say.:(
@Avantiii1
You can not change it by configuration, but ingame:
Use /vanflag +interact (or /vanflag +int) to allow breaking and placing blocks.
You might also add +pickup if you want to pick up blocks.
The flags get saved to disk, so there is no need to set them after eeach server restart. To reset the flag you can do it individually with the "-" version fo the flag, say "/vanflag -int" or you just clear flags to default with "/vanflag *clear".
You can also add the flags to /van and /rea commands, if you normally don't want to build but this time you could do "/van +int +pick" to spare a command. Actually for the most flags two letter abbreviations should also work.
If you have a couple of flags to set for something you often do, but you also want to reset often then the advanced way could be to define a flag set in the configuration with an abbreviation of your choice and the flags to set.
I can't build while vanished, can you show me how to change that in the config?
@xXdaslofreekXx
That might be slightly difficult if you don't use permissions.
But depending on your setup it is possible in different ways.
Do you use a permissions plugin at all ?
Do you have many ops?
If you don't use permissions and have few ops then you could set allow-ops and superperms to false and make a set entry with the player names in the permissions section in the configuration of SImplyVanish (drawbacks are, that this can not be changed in-game and that the players keep the access to vanishing even if not op anymore...) , example to just let them vanish and reappear and display their own flags, don't forget to add yourself and your admins into the set with the "all" permission:
How do I change the config to where ops can't see vanished players?
@asofold
Thanks! You're right, I didn't notice that option in the config. I guess I just assumed that since it wasn't on by default, it didn't exist at all. Anyway now my players are totally creeped out - in addition to being online or not at any time, I also get their whispers (griefprevention) and see all their sign placements in a log.
"I'm watching u!" =D I like to think it keeps them in line. It wouldn't be possible without your plugin.
@Headsuphunter
The "now" version was intended to indicate that you change the visibility, the "still" version was to indicate still being of the state. Would you prefer to have just one message for both cases?
I am also considering making the messages configurable on the medium term.
Suggestion: When someone does /van have it say "You are currently [type]" instead of "You are now [type]" I can see this will confuse new people that aren't sure of the commands.
@bigscary
I uploaded an experimental version to github:
https://github.com/asofold/SimplyVanish/downloads
It adds a tell flag which allows incoming messages by the also newly added command /vantell. /vantell is the same as tell, just as an extra command. You can further add "tell" to the command alias list for vantell, to replace tell by vantell. It changes the messages slightly but respects the tell flag and allows for logging vantell to the console.
The permission for using vantell is "simplyvanish.cmd.vantell", it is not given by default.
There are bypass permissions to allow using vantell to vanished players that you can not see: simplyvanish.vantell.bypass or for a specific player simplyvanish.vantell.bypass.player.<player name in lower case> .
@bigscary
Interesting :)
2. It should be possible to suppress join and quit messages for vanished players by the configuration. The flags to true for the section messages -> suppress -> join/quit (i have to update the config page for better readability).
1. Actually CraftBukkit prevents the whispers, and as far as i know i can not change it directly. It might be possible to intercept the tell command and put it through to a vanished player "if desired". The main problem would be, that potentially many people will not want the chat or cmd flags to allow others use tell to vanished players. Introducing a new flag might be the best option, though that sizes up the flag section once more, on the other hand the flag is only shown if it is set to non-default, so for most people it wouldnt matter.
3. I was contemplating about "/vangod", having all the events monitored anyway a simple god mode using the same flags just not being vanished : What would people say to that ?
Hey asofold I know I've told you I love this plugin before, but I'm telling you again. I'm a bit of a minimalist - I only run four plugins on my server, and yours is one of the two "non-essential, but too good to resist" plugins. I especially appreciate your update to allow me to drop items while invisible, which is super handy for some administrative tasks. I have two small requests!
1. Players complain that they can't /tell me. I understand why you'd block whispers when I'm invisible so that players can't test to see if I'm online, but even when I opt-in to chat (making my presence obvious by chatting), I still have this problem. It's ugly to work around because players have to tell me in public chat that they want to whisper me, then I have to /reappear, then tell them to try again, then receive their message, and finally /vanish again. In my opinion, opting-into chat should also open me up to whispers. Or if you don't like that, a separate flag for whispers would satisfy me. :)
2. Even though I log out as invisible, players know when I log back in because they get the "so and so joined the server" default server message. Can you block that message when I'm invisible, or at least camouflage it by changing it to something else so that players don't realize I've logged in or logged out?
@polo3400
Now it is not that hard anymore - just updated the information a little bit :)