Bukkit

@broman349

First of all you have to make sure which version you are using, and if it supports the features. 0.4.0-PRE-3 (or any newer pre-version) will support all that in general.

The configuration entries are explained below, if you have them, it should work.

1. To activate the fake join and leave messages you have to set the configuration flag messages.fake.enabled to true:

messages:
  # ...
  fake:
    enabled: true
    join: '&e%name joined the game.'
    quit: '&e%name left the game.'
  # ...

You might also want to suppress the ordinary join/quit messages for vanished player, in that case set the messages.suppress.join and quit to true:

messages:
  # ...
  suppress:
    join: true
    quit: true
  # ...

(Be sure to only have one 'messages' section.)
2. You "spawn invisivle" - you are talking of that you leave the server visible and when you reconnect you are invisible? Then "it resets" are you refering to the ingame flag -auto or the configuration section of auto-vanish ?
You can prevent auto-vanish with /vanflag -auto (or /simplyvanish -auto), the state should get saved and would be remembered for later logins.

@Damimad

I will attempt to add something for that.

Update:

For DisguiseCraft use the new pre release version or newer (dev-jar).

@Wannab007

SimplyVanish just checks for the permission and if the player is op - so there is little that can go wrong on that side.

Your permission plugin must be SuperPerms compatible - GroupManager is, as far as i know.

It looks like a permission configuration problem.

@bigscary

Ok, the current dev versions should be ok (...).

@bigscary

I deactivated the download for the dev version because we a re experiencing trouble with visibility which i am not sure about if it comes from the dev version or CraftBukkit.

I will recheck the code and then put up a new version, hopefully this weekend.

@bigscary

You can soon set the flag for drop with /simvan +drop or with /vanish +drop ...

@Damimad

To make sure that i am understanding what you say:

1. You are disguised as a mob using the Disguisecraft plugin. 2. You use /vanish ... 3. You are not vanished, the mob is still showing up.

If so , then there is a simple explanation... Disguisecraft puts a mob into your position which does not vanish because showing or hiding players from each other does not manipulate mobs. Disguisecraft seems to "mess" with CraftBukkit internals to manipulate and add data sent to each client, so i will hardly be able to offer full compatibility.

Actually this is a pretty specialized request (if seen as a feature/fix request) on the other hand Disguisecraft does provide an API, i could offer to allow a simple hook for disguisecraft such as to disable the mob disguise when vanishing, but i do not want to keep track of if players want to be mob disguised after reappearing for now (later if there should be savable vanish-configurations, one might consider having a "simple"switch to do such but currently SimplyVanish is simply doing the API based vanishing stuff)...

@bigscary

There is a toggle! you can use /tvanish /vanisht or shorter: /tvan and /vant .

There is a command to drop the item in hand: /simplyvanish drop or /simvan drop - given the new chat features of minecraft it might even be ok to use :) - i might bring in such features in a more convenient way lateron.

@sejbr

The message is shown for the involved players, on each time hide or show is attempted - of course it should only show up, if the server claims them not to be online at the given moment.

So it is possible the the player to be hidden or shown appears multiple times, and that other online players appear too, to whom this player should be hidden or shown.

Surprising is that the messages appear at all - it means that the player actually is not hidden/shown, because this has been a crash-prevention - and it was added as a wild guess for what might be related to reported server crashes on show/hide for players.

If you are really using version 0.3.3 or above, then this should really be an indication for a CraftBukkit bug of serious nature, so what will i do:

• I will add an option to force-hiding/showing on that error, so you can see if your server crashes if SimplyVanish attempts to hide or show a player in such a situation, instead of aborting.

I still have to ask:

• Does that happen more often (how often approximately? Each time? Only for reappear?)
• Your CraftBukkit version (Best would be the version string, to have more precision than 1.2.3 or so. )?
• Do you use Spout or other plugins that go deep into CraftBukkit to change things? [I personally don't think that is the reason...]
• Are there any other information available for the moment when that happens, like "many players logged in/out just before or after the messages" or "high/low server load", "other exceptions showing up shortly before..." ?
• You did make sure to run Simplyvanish 0.3.3 or 0.4.0-DEV-X (/version SimplyVanish)?

@Nicomang070

I added the command "/nosee or /tnosee" to toggle if you see or not see vanished, for a dev version (see above: Dev jar).

@DjScream3

Thank you for reporting!

Fixed in SimplyVanish 0.3.3 !

I am sorry - that is a bug with versions before 0.3.3 for the most cases. The message is supposed to show a somewhat critical inconsistency if it should happen, but accidentally the message gets shown every time a player is hidden or shown to another player.

@Nicomang070

Command:

That i can add, it makes sense, for not everyone has the option or likes to manipulate permissions in-game...

I just have to decide how to show it to the player that he can or can not see other vanished players, but it is on schedule.

Quit/kick:

Yes it should work with the newest versions to set the configuration flags:

• messages.suppress.quit: true
  This should prevent quit and kick messages for vanished players..
• messages.suppress.join: true
  This should prevent join messages for vanished players.

For vanishing or reappearing while online, you can also set vanilla style fake join and quit messages by configuration, as long as those dont use player- or group- prefixes it should be possible to set them in thee config, you can use %namefor the name and %displayname for the display-name, while colors can be done with &0 ... &f

It might be that another plugin sets the quit/join messages as well, i have set SImplyVanish to modify those on the highest priority, i.e. more or less the last moment, however if your chat plugin uses that priority as well, then we have a problem here.

I abbreviated the configuration paths with x.y.z, see Configuration for the current configuration, i add it to the bottom of the page, it should be somewhat more plain then.