Advertisement
Guest User

PV Config v2.8.0

a guest
Dec 18th, 2022
1,420
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
YAML 31.82 KB | None | 0 0
  1. # PremiumVanish v2.8.0 - Configuration
  2.  
  3. ##################################################
  4. ############# Invisibility Features ##############
  5. ##################################################
  6. InvisibilityFeatures:
  7.  # Should invisible players get night vision?
  8.   NightVisionEffect: true
  9.   # Should PV disable damage for invisible players?
  10.   DisableDamage: true
  11.   # Should PV disable hunger for invisible players?
  12.   DisableHunger: true
  13.   # Should PV prevent mobs from targeting invisible players?
  14.   DisableMobTarget: true
  15.   # Should invisible players not be able to stop the placement of blocks at their location?
  16.   # While this stops other players from revealing invisible players by spamming blocks around them
  17.   # it can also be abused since it allows placing blocks at impossible locations
  18.   DisablePreventBlockPlacement: true
  19.   # Should invisible players only be able to send chat messages if the message ends with the following character?
  20.   # You can set this to 'deny' to cancel the message in any case.
  21.   # Please leave this empty if you'd like to disable the feature.
  22.   RequireChatMessageSuffix: "/"
  23.   # Should invisible players open chests and shulker boxes without the animation and sound?
  24.   # This makes them go into spectator mode temporarily. It's better to only give access to this feature
  25.   # to staff members since a server crash can cause players to stay in spectator mode.
  26.   # Permission: pv.silentchest
  27.   OpenChestsSilently: true
  28.   # Should invisible players be able to open a player's inventory by right-clicking the player?
  29.   # Permission: pv.openplayerinv
  30.   OpenPlayerInventoryOnRightClick: true
  31.   # Should invisible players be able to edit inventories (including their own) even if they're in spectator mode?
  32.   # Permission: pv.spectatoreditinv
  33.   AllowSpectatorInventoryEdit: true
  34.   # Should invisible players not be able to trigger pressure plates and tripwire?
  35.   # If this feature is enabled invisible players can't trigger pressure plates and tripwire.
  36.   DisablePressurePlates: true
  37.   # Should invisible players not be able to push other players or be able to be pushed?
  38.   # WARNING: Uses the scoreboard and may conflict with other plugins!
  39.   DisablePush: false
  40.   # Should invisible players be hidden in the tablist? This feature is currently not supported on 1.19.3 or higher.
  41.   # IMPORTANT: Not every player hider supports showing invisible players
  42.   # in the tablist, please use the Interception hider to be able to turn this off and to activate the -t flag
  43.   # (see the INVISIBILITY METHOD section below)
  44.   #
  45.   # If this is true, you can still be visible in the tablist using the "/pv -t" command flag (Requires pv.showintab).
  46.   # You can combine it with "-s" (Requires pv.silent) to silently vanish without being hidden in tab.
  47.   HideInTablist: true
  48.   # Should players who vanished with the -t (showInTab) flag be fully hidden again after a rejoin?
  49.   # This feature is currently not supported on 1.19.3 or higher.
  50.   # Command flags are stored locally and only affect the server you vanished on.
  51.   ResetShowInTabOnQuit: true
  52.   # Should invisible players be hidden in the game? This feature is currently not supported on 1.19.3 or higher.
  53.   # IMPORTANT: Not every player hider supports showing invisible players
  54.   # in the game, please use the Interception hider to be able to turn this off
  55.   # (see the INVISIBILITY METHOD section below)
  56.   #
  57.   # Please note that not hiding players in-game but hiding them in tab will lead to them being
  58.   # visible in the tablist for a split second whenever they move into viewing range.
  59.   # This is needed since the skin information of a player is transferred with the tablist packets.
  60.   HideInGame: true
  61.   # If HideInTablist is turned off, should players who can't see you not be able to
  62.   # This feature is currently not supported on 1.19.3 or higher.
  63.   # see you as a spectator in the tablist even if you are in spectator mode?
  64.   HideSpectatorMode: true
  65.   # Should vanished players pick up items by default? This can be changed individually with /pv tipu
  66.   DefaultPickUpItemsOption: false
  67.   # The commands to execute when a player vanishes (online or offline)
  68.   # These commands are ran by console by default, you can use %p% to get the player's name.
  69.   # You can also prefix the command with [P] to make the player run the command
  70.   # instead of the console (player online only)
  71.   # You can remove the # to make it a list if you'd like to enable this
  72.   VanishCommands:
  73. #  - examplecommand
  74. #  - examplecommand2
  75.  
  76.   # The commands to execute when a player reappears (online or offline)
  77.   # These commands are ran by console by default, you can use %p% to get the player's name.
  78.   # You can also prefix the command with [P] to make the player run the command
  79.   # instead of the console (player online only)
  80.   # You can remove the # to make it a list if you'd like to enable this
  81.   ReappearCommands:
  82. #  - examplecommand
  83. #  - examplecommand2
  84.  
  85.   # You can make any command not execute and instead return a custom message if an argument is a vanished
  86.   # player's name. Useful for faking 'Player not found' messages if there are unsupported plugins.
  87.   # You can use <vanished> as a placeholder for any vanished player's name.
  88.   # Any message which STARTS WITH the text you define below (case-insensitive) will
  89.   # be cancelled and will instead send the sender of the command a message you specify.
  90.   # The /plugin:command syntax is covered automatically.
  91.   # This is server-sided, for bungeecord commands go to the Bungee's PV config
  92.   CustomCommandMessages:
  93.     '/examplemsg1 <vanished>': "&cPlayer not found"
  94.   # For how many seconds should players not be able to take environmental damage after they reappear?
  95.   # e.g. fall damage or lava damage; Set to 0 to disable it
  96.   DisableEnvironmentalDamageAfterReappear: 5
  97.   # Should vanished players not be required to sleep for other players to wake up?
  98.   SetSleepingIgnored: true
  99.   # Should vanished players switch between their current gamemode and spectator mode when they
  100.   # press shift twice? Permission: pv.switch
  101.   SwitchGamemode: true
  102.   # Should advancement announcements of vanished players only be shown to players who can see the vanished player?
  103.   HideAdvancements: true
  104.   # Should vanished players be unable to trigger the vibration of a sculk sensor?
  105.   PreventSculkSensorActivation: true
  106.  
  107. ##################################################
  108. ############# Vanish State Features ##############
  109. ##################################################
  110. VanishStateFeatures:
  111.  # Should players with the permission 'pv.joinvanished' join vanished all the time?
  112.   # Might not work if you use GroupManager for permissions
  113.   AutoVanishOnJoin: false
  114.   # Should invisible players reappear automatically when they change their world?
  115.   ReappearOnWorldChange: false
  116.   # Should invisible players without 'pv.bypassreappearonquit' reappear automatically when they leave the server?
  117.   ReappearOnQuit: false
  118.   # Should invisible players reappear automatically
  119.   # when they change their world and don't have the permission 'pv.use' anymore?
  120.   CheckPermissionOnWorldChange: false
  121.   # Should invisible players reappear automatically
  122.   # when they leave the server and don't have the permission 'pv.use' anymore?
  123.   CheckPermissionOnQuit: false
  124.   # Should invisible players reappear automatically
  125.   # when they join the server and don't have the permission 'pv.use' anymore?
  126.   # Doesn't work if you use GroupManager for permissions
  127.   CheckPermissionOnLogin: false
  128.  
  129. ##################################################
  130. ############## Indication Features ###############
  131. ##################################################
  132. IndicationFeatures:
  133.   LayeredPermissions:
  134.    # Should players with the permission 'pv.see' be able to see invisible players in the tablist & in-game?
  135.     EnableSeePermission: true
  136.     # Should pv.use and pv.see be layered? => pv.use.levelX, pv.see.levelX
  137.     # Players can see a vanished player if their see level is higher or equal to the other player's use level
  138.     # Note: You have to rejoin for changes to take effect if you changed those permissions while being online
  139.     LayeredSeeAndUsePermissions: false
  140.     # What should be the highest level for both permissions?
  141.     # Lower amounts might improve performance with more players since they reduce the amount of permission checks
  142.     MaxLevel: 100
  143.     # If LayeredSeeAndUsePermissions is enabled, should /pv list only show players which the command sender is
  144.     # allowed to see and should players only be able to toggle the invisibility of players which they are allowed
  145.     # to see (Only affects online players)?
  146.     HideInvisibleInCommands: false
  147.     # Should PremiumVanish iterate through all the permissions of a player instead of checking for all
  148.     # possible layered permissions? Enabling this may or may not improve PV's performance.
  149.     # Warning: Enabling this may break PV depending on your permissions plugin
  150.     AlternatePermissionChecking: false
  151.     # Should you require the permission pv.setlevel.level<LEVEL> to set your level to <LEVEL>?
  152.     # Example: The permissions 'pv.setlevel' and 'pv.setlevel.level3' are required to use '/pv setlevel 3'
  153.     StrictSetLevelPermissionChecking: false
  154.   # Should vanished players show up dark gray in the tablist and should only their head be visible?
  155.   # This feature is currently not supported on 1.19.3 or higher.
  156.   # Only players who are allowed to see the player will see this effect; this helps other staff with
  157.   # differentiating them from players they should talk to
  158.   # If this feature causes conflicts with tablist/nametag plugins, you can try the next setting instead
  159.   MarkVanishedPlayersAsSpectators: true
  160.   # Should vanished players show up as glowing? It's recommended to turn off the TargetGlows option of the
  161.   # scoreboard to avoid conflicts when using this
  162.   # This feature is currently not supported on 1.19.3 or higher.
  163.   MarkVanishedPlayersWithGlow: false
  164. ##################################################
  165. ########### Survival Friendly Features ###########
  166. ##################################################
  167. SurvivalFriendlyFeatures:
  168.   Fly:
  169.    # Should invisible players with the permission pv.fly be able to fly even if they aren't in creative/spectator mode?
  170.     Enable: true
  171.     # Should invisible players WITHOUT the permission 'pv.keepfly' lose the ability to fly on reappear?
  172.     DisableOnReappear: true
  173.  
  174.   GameMode:
  175.    # The gamemode which players will get when they vanish
  176.     # 'Default' applies for every world which isn't mentioned below
  177.     # !! Warning: World names are case-sensitive !!
  178.     # Available gamemodes: SURVIVAL, ADVENTURE, CREATIVE, SPECTATOR, KEEP
  179.     # KEEP won't change the gamemode in any way
  180.     ChangeToOnVanish:
  181.       Default: KEEP
  182.       ExampleWorld123: SPECTATOR
  183.     # The gamemode which players will get when they reappear
  184.     # 'Default' applies for every world which isn't mentioned below
  185.     # Available gamemodes: SURVIVAL, ADVENTURE, CREATIVE, SPECTATOR, KEEP
  186.     # KEEP won't change the gamemode in any way
  187.     ChangeToOnReappear:
  188.       Default: KEEP
  189.       AnotherExampleWorld2: SURVIVAL
  190.     # Should PV update the gamemode 1 tick after a player joins/changes their world?
  191.     # The new gamemode will depend on the player's new world, as defined above
  192.     # Helpful if you want to force players to be in a gamemode in a specific world
  193.     # or if another plugin interferes with PV.
  194.     ReApplyGameModeChangeOnWorldChange: true
  195.     ReApplyGameModeChangeOnJoin: true
  196.     # Should the gamemode change when you join vanished *because of* your pv.joinvanished permission?
  197.     # Ignores the two settings above.
  198.     AlwaysApplyOnJoinVanished: true
  199.  
  200.   Location:
  201.    # Should vanished players be teleported back to where they vanished when they reappear?
  202.     # The location is saved in the data.yml file and is therefore safe in case of a restart/crash
  203.     # Bypass permission: pv.bypassteleportback
  204.     TeleportBackOnReappear: false
  205.  
  206. ##################################################
  207. ################ Message Options #################
  208. ##################################################
  209. MessageOptions:
  210.   MessagesOnVanishReappear:
  211.    # Should PV broadcast any kind of announcement (fake quit or player vanished) when a player vanishes?
  212.     # You can change the messages in the messages.yml file.
  213.     BroadcastMessageOnVanish: true
  214.     # Should PV broadcast any kind of announcement (fake join or player reappeared) when a player reappears?
  215.     # You can change the messages in the messages.yml file.
  216.     BroadcastMessageOnReappear: true
  217.     # Should players with permission to see the player get an announcement instead of a fake join/quit message?
  218.     # The vanishing/reappearing player will always get the fake join/quit message.
  219.     AdminsGetAnnouncementInstead: true
  220.     # Should there only be announcements and no fake join/quit messages?
  221.     # This means players without permission to see the player don't get any message.
  222.     DontSendFakeJoinQuit: false
  223.     # Should there only be fake join/quit messages and no announcements?
  224.     # This means players with permission to see the player don't get any message.
  225.     DontSendAdminAnnouncements: false
  226.  
  227.   MessagesOnJoinQuit:
  228.    # Should PV hide the real join/quit messages of invisible players?
  229.     HideRealJoinQuitMessages: true
  230.     # Should players with permission to see a vanished player get an announcement when they actually join/quit?
  231.     AnnounceRealJoinQuit: true
  232.     # Should PV still hide quit messages for invisible players if 'VanishStateFeatures->ReappearOnQuit' is turned on?
  233.     # Overrides 'HideRealJoinQuitMessages'
  234.     ReappearOnQuitHideMessage: true
  235.     # Should PV remind players who join the server vanished of being invisible (in chat)?
  236.     # You can change the message in the messages.yml file.
  237.     RemindVanishedOnJoin: true
  238.  
  239.   # Should invisible players have an action bar which tells them that they're invisible?
  240.   # You can change the action bar in the messages.yml file.
  241.   DisplayActionBar: true
  242.  
  243. ##################################################
  244. ############## Restrictive Options ###############
  245. ##################################################
  246. RestrictiveOptions:
  247.  # Should invisible players not be able to break blocks?
  248.   # Bypass permission: pv.breakblocks
  249.   PreventBlockBreaking: false
  250.   # Should invisible players not be able to place blocks?
  251.   # Bypass permission: pv.placeblocks
  252.   PreventBlockPlacing: false
  253.   # Should invisible players not be able to interact with doors, levers, buttons, note blocks, etc?
  254.   # Doesn't prevent opening containers
  255.   # Bypass permission: pv.useblocks
  256.   PreventBlockUse: false
  257.   # Should invisible players not be able to interact with anything
  258.   # (blocks, buttons, pressure plates, chests, block breaking/placing, noteblocks, doors, ...)
  259.   # This setting overrides the three settings above
  260.   # Bypass permission: pv.interact
  261.   PreventInteract: false
  262.   # Should invisible players not be able to damage players or mobs?
  263.   # Bypass permission: pv.damage
  264.   PreventHittingEntities: false
  265.   # Should invisible players not be able to drop items?
  266.   # Bypass permission: pv.dropitems
  267.   PreventDroppingItems: false
  268.   # Should invisible players not be able to modify their own inventory?
  269.   # Bypass permission: pv.modifyowninv
  270.   PreventModifyingOwnInventory: false
  271.   # Should invisible players not be able to modify containers or other player's inventories?
  272.   # Overrides InvisibilityFeatures.AllowSpectatorInventoryEdit
  273.   # Bypass permission: pv.modifyotherinv
  274.   PreventModifyingOtherInventory: false
  275.   # Should invisible players not be able to tp to other players using the spectator menu?
  276.   # Bypass permission: pv.spectatortp
  277.   PreventSpectatorTeleporting: false
  278.   # Should invisible players in creative mode not be able to cheat items?
  279.   # Bypass permission: pv.creativeitems
  280.   PreventCreativeItemGrab: false
  281.   # Should invisible players not be able to view their coordinates? (client-side)
  282.   # Bypass permission: pv.viewcoords
  283.   HiddenCoordinates: false
  284.  
  285.   Commands:
  286.    # Which commands should vanished players not be able to use?
  287.     # This blocks the 'plugin:command' syntax too but not aliases
  288.     # Bypass permission: pv.bypasscmd
  289.     VanishedCommandBlacklist:
  290.    - examplecommand123test
  291.     - anotherexamplecommand123
  292.     # Should vanished players only be able to use the commands listed above instead?
  293.     UseAsWhitelist: false
  294.  
  295. ##################################################
  296. ############# External Invisibility ##############
  297. ##################################################
  298. ExternalInvisibility:
  299.   ServerList:
  300.    # Please use PremiumVanish's bungeecord configuration instead if you use Bungeecord.
  301.     #
  302.     # Should this plugin adjust the amount of players in the serverlist? (-1 per invisible player)
  303.     AdjustAmountOfOnlinePlayers: true
  304.     # Should this plugin hide invisible players in the list of logged in players?
  305.     # You can view this list when your mouse hovers over the amount of online players.
  306.     AdjustListOfLoggedInPlayers: true
  307.  
  308. ##################################################
  309. ############### Scoreboard Options ###############
  310. ##################################################
  311. ScoreboardOptions:
  312.  # Disable this if you don't need PremiumVanish's scoreboard features
  313.   # You can also toggle your scoreboard with the '/pv scoreboard' command
  314.   #
  315.   # Note: If you are disabling this because it causes problems with other scoreboards/prefixes
  316.   # then you probably want to disable 'DisablePush' above as well since it uses the scoreboard too
  317.   Enable: true
  318.  
  319.   # Should players require the permission pv.scoreboard to view the scoreboard?
  320.   Permission: false
  321.  
  322.   Sidebar:
  323.    # The header/title of the scoreboard, default: '&6>       PremiumVanish       <'
  324.     # The length cannot be longer than 32 characters(including color codes) but can cause flickering
  325.     # if it isn't longer than the lines below it
  326.     ScoreboardHeader: "&6>       PremiumVanish       <"
  327.     # The lines of PremiumVanish's scoreboard
  328.     # Prefix a line with a # if it should only show up if there is a target (the placeholders will
  329.     # also be based on the target)
  330.     # A line can never be longer than 32 characters (watch out for player names, which can be up to 16 chars long)
  331.     # All general placeholders that work in the messages.yml file work here, too.
  332.     # Additionally to the messages.yml placeholders you can use %target% and %locked% (if the target has been fixed).
  333.     Lines:
  334.    - ""
  335.     - "&aTarget: &f%target% %locked%"
  336.     - "#"
  337.     # The color of the ping is based on how good the ping is, use %plain_ping% for no colors; same with tps
  338.     - "#&aPing: &f%ping%"
  339.     - ""
  340.     - "&aTPS: &f%tps%"
  341.     - "#"
  342.     - "#&aHealth: &f%health%/%maxhealth%hp"
  343.     - ""
  344.     - "&aTime: &f%time{hh:mma | yyyy/MM/dd}%"
  345.     - ""
  346.     # The interval between each update of the info on the scoreboard
  347.     # in ticks, decreasing this might decrease performance slightly
  348.     # 20 ticks equals to 1 second, default: 5
  349.     InfoUpdateInterval: 5
  350.   Targeting:
  351.    # Should the scoreboard show information about the closest player automatically?
  352.     # If you're spectating, this option would always show the info of the player you're currently spectating.
  353.     # Permission to be exempted from being targeted automatically: pv.exempttarget
  354.     AutoTargetClosestPlayer: true
  355.     # Should you target players when you right-click them?
  356.     # If both this option and 'OpenPlayerInventoryOnRightClick' is enabled then you
  357.     # are still able to lock a player by sneaking and right-clicking the player.
  358.     # (In spectator mode you can press space and shift at the same time for the same effect)
  359.     # If 'AutoTargetClosestPlayer' is enabled then it will stop targeting the closest player when
  360.     # you right-click a player until you type '/pv unlock', same for /pv target <player> even if this option
  361.     # is disabled
  362.     TargetOnRightClick: true
  363.     # Should your current target glow (only you see this effect)?
  364.     # This feature is currently not supported on 1.19.3 or higher.
  365.     TargetGlows: true
  366.  
  367. ##################################################
  368. ################## Hook Options ##################
  369. ##################################################
  370. HookOptions:
  371.  # Should PV hide invisible players in /who, /list, /online, /near, etc?
  372.   # Note: Players with the permission essentials.vanish.interact can still see invisible players in these commands
  373.   # Important: You have to reload both PV and Essentials if you change this setting (reload PV first)
  374.   EnableEssentialsHook: true
  375.   # Should PV hide invisible players on your dynamic map and broadcast join/leave messages if you use Dynmap?
  376.   EnableDynmapHook: true
  377.   # Should PV send fake join/leave messages in dynmap's web-chat?
  378.   # You can configure the join/leave messages in the messages.yml file
  379.   DynmapSendJoinLeaveMessages: true
  380.   # Should PV prevent players from being invisible and disguised at the same time? (LibsDisguises commands)
  381.   # It's recommended to keep this turned on to prevent incompatibility.
  382.   EnableLibsDisguisesHook: true
  383.   # Should PV prevent players from being invisible and disguised at the same time? (DisguiseCraft commands)
  384.   # It's recommended to keep this turned on to prevent incompatibility.
  385.   EnableDisguiseCraftHook: true
  386.   # Should PV hook into TrailGUI and disable trails while you're vanished?
  387.   EnableTrailGUIHook: true
  388.   # Should PV hook into SuperTrails and disable trails while you're vanished?
  389.   EnableSuperTrailsHook: true
  390.   # Should PV hook into PlaceholderAPI and add new placeholders to PV + register its own ones for other plugins?
  391.   # Own ones: isvanished, vanishprefix, vanishsuffix, vanishedplayers, playercount, bungeeplayercount, bungeeplayercount@<server>,
  392.   #           playercountwithoutshowintab, target, uselevel, seelevel
  393.   # Format: %premiumvanish_<placeholder>%
  394.   #
  395.   # The bungee placeholders require PV to be installed on bungee and set up with a MySQL database on all servers.
  396.   # They neither account for the showintab flag nor for the amount of vanished players that you are allowed to see.
  397.   #
  398.   # The result of the isvanished placeholder can be edited by changing HelpConsoleYes/No in the messages.yml file.
  399.   EnablePlaceholderAPIHook: true
  400.   # Should PV hook into MVdWPlaceholderAPI and add new placeholders to PV + register its own ones for other
  401.   # plugins?
  402.   # Own ones: isvanished, vanishprefix, vanishsuffix, vanishedplayers, playercount, bungeeplayercount, bungeeplayercount@<server>,
  403.   #           playercountwithoutshowintab, target, uselevel, seelevel
  404.   # Format: {premiumvanish_<placeholder>}
  405.   #
  406.   # The bungee placeholders require PV to be installed on bungee and set up with a MySQL database on all servers.
  407.   # They neither account for the showintab flag nor for the amount of vanished players that you are allowed to see.
  408.   #
  409.   # The result of the isvanished placeholder can be edited by changing HelpConsoleYes/No in the messages.yml file.
  410.   EnableMVdWPlaceholderAPIHook: true
  411.   # Should PV stop NPCs from greeting or talking about hidden players?
  412.   EnableCitizensHook: true
  413.   # Should PV hook into CustomParticleEffects and disable particles while you're vanished?
  414.   EnableCustomParticleEffectsHook: true
  415.   # Should PV use NametagEdit's API to prevent incompatibilities with its prefixes/suffixes?
  416.   EnableNametagEditHook: true
  417.   # Should PV hook into FeatherBoard to prevent incompatibilities with its scoreboard?
  418.   EnableFeatherBoardHook: true
  419.   # Should PV hook into EnjinMinecraftPlugin to prevent vanished players from showing up on its website?
  420.   EnableEnjinMinecraftPluginHook: true
  421.   # Should PV hook into CMI to prevent vanished players from entering AFK state?
  422.   EnableCMIHook: true
  423.   # Should PV hook into DiscordSRV to broadcast fake join/quit messages on Discord?
  424.   EnableDiscordSRVHook: true
  425.   # Should PV hook into TitleManager to prevent incompatibilities with its scoreboard?
  426.   EnableTitleManagerHook: true
  427. ##################################################
  428. ############## Invisibility Method ###############
  429. ##################################################
  430. InvisibilityMethod:
  431.  # The method of hiding players; Available methods: Prevention, Interception, Hybrid
  432.  
  433.   # 'Prevention': Uses Bukkit's API to hide players, this is an extremely reliable method if other plugins don't break it.
  434.   # This method ALWAYS hides invisible players in the tablist for players that can't see them.
  435.   # The chance that another plugin breaks this method is low depending on the amount and type of plugins.
  436.   # > Recommended if other hiders cause issues; other plugins can break this method though
  437.   # (Accuracy: 95%) (Plugin compatibility: 95%) (Uses game layer invisibility)
  438.  
  439.   # 'Interception': Uses ProtocolLib to hide players. Takes the whole packet stuff into its own hands to cancel every
  440.   # single packet of hidden players. This option is currently not supported on 1.19.3 or higher.
  441.   # This method CAN show invisible players in the tablist for players who can't see them if that's enabled.
  442.   # Hard to break, however, other plugins might not provide direct support for this hider
  443.   # It's important to note that Essentials might not recognize vanished players as vanished in its commands with this hider.
  444.   # > Recommended if you want to show invisible players in the tablist
  445.   # (Accuracy: 95%) (Plugin compatibility: 90%) (Uses protocol layer invisibility)
  446.  
  447.   # 'Hybrid: Uses both ProtocolLib and Bukkit's API to hide players, this method does NOT support showing players
  448.   # in the tablist but it contains two layers of security and is therefore an extremely effective method.
  449.   # The chance that another plugin breaks this method is extremely small
  450.   # > Default hider; Recommended if you don't want to show invisible players in the tablist
  451.   # (Accuracy: 100%) (Plugin compatibility: 98%) (Uses game and protocol layer invisibility) - DEFAULT
  452.  
  453.   PlayerHider: "Hybrid"
  454.  
  455.   # Note: Even 'Hybrid' can't stop players from figuring out whether invisible players are online if another
  456.   # plugin tells them but players will never be able to see them at all or figure out their location
  457.   # (Essentials is 99% compatible)
  458.  
  459.   Advanced:
  460.  # Advanced section which affects the protocol layer invisibility for the Interception and Hybrid hiders
  461.  
  462.     # Which protocol layer invisibility modules should be disabled?
  463.     # You can disable some modules here if they are causing issues or aren't supported on
  464.     # your server after an update or if you are using the Interception hider and simply don't want players
  465.     # to be invisible in some regards.
  466.     # You are unlikely to note invisibility changes here if you are using the Hybrid hider since it also has
  467.     # game layer invisibility which isn't affected here
  468.     # It's recommended to instead use the HideInTablist/Game options if that's what you want to change
  469.     DisabledInvisibilityModules:
  470.    # Physical appearance in the game
  471. #    - GeneralEntity
  472.     # Sounds in the world
  473. #    - NamedSoundEffect
  474.     # Tablist entry (includes hide spectator mode feature)
  475.     # Please uncomment this if you are using Maximvdw's Tab or AnimatedNames plugin and have issues with nametags
  476. #    - PlayerInfo
  477.     # Info about player prefixes, suffixes, etc (formerly 'StrictInvisibility'); this is
  478.     # disabled by default since it is very likely to cause issues with nametag/prefix plugins
  479.     # Comment this out (enable it) if it doesn't cause issues, since it can prevent vanished player information leaks
  480.     - ScoreboardTeam
  481.     # Tab completion suggestions (formerly 'DisableHandlingOfTabulatorPackets')
  482.     # Enable this module if you don't use bungeecord. It's disabled by default to prevent issues with bungee
  483.     - TabComplete
  484.     # Particles in the world
  485. #    - WorldParticles
  486.  
  487. ##################################################
  488. ############# Compatibility Options ##############
  489. ##################################################
  490. CompatibilityOptions:
  491.  # This section is for advanced users only!
  492.   # The event priority which PremiumVanish should use for the specific event.
  493.   # Allowed values are LOWEST, LOW, NORMAL, HIGH, HIGHEST and MONITOR
  494.   # Higher priorities might override other plugins while lower ones might not
  495.  
  496.   # The priority for removing the join message
  497.   PlayerJoinEventPriority: HIGH # <- keep HIGH if you use Essentials to modify join/quit messages !!
  498.   # The priority for removing the quit message
  499.   PlayerQuitEventPriority: HIGH
  500.   # The priority for cancelling chat messages
  501.   AsyncPlayerChatEventPriority: HIGH
  502.   # The priority for cancelling commands
  503.   PlayerCommandPreprocessEventPriority: HIGH
  504.   # A whitelist of command usages where it should be allowed to tab-complete vanished players that you can't see.
  505.   # You can use this for commands that generally tab-complete any player, online or not.
  506.   # This section is for advanced users only and uses regular expressions.
  507.   # For changes to apply you need to change this on all spigot servers and on the bungee if you're using bungee.
  508.   TabCompleteWhitelist:
  509.    - "/(ps|plotsquared|p2|2|plotme|plot|p)\\s(visit|v|tp|teleport|goto|warp).*"
  510.  
  511. ##################################################
  512. ############# Miscellaneous Options ##############
  513. ##################################################
  514. MiscellaneousOptions:
  515.   Bungeecord:
  516.    # Should PremiumVanish store its data in a MySQL-Database and enable Bungeecord support?
  517.     # Bungeecord is not required for this feature but it's recommended!
  518.     # PremiumVanish will be disabled if this is enabled and the connection to the database failed.
  519.     #
  520.     # Important: Please make sure that ip-forwarding is enabled on your Bungee AND your Bukkit servers.
  521.     # It's also important that your database is firewalled so it's not accessible from the internet.
  522.     Enable: false
  523.     # The ip of your database server
  524.     Ip: ""
  525.     # The port of your database, usually 3306; just leave it empty if there is no specific port
  526.     Port: "3306"
  527.     # You can make PremiumVanish ignore the two options above and use a direct URI to connect instead
  528.     # Format for MySQL servers: jdbc:mysql://<yourIp>:<yourPort>/<yourDatabase>?useSSL=false
  529.     CustomURI: ""
  530.     # The name of your database user
  531.     User: ""
  532.     # The password of your database user
  533.     # WARNING: Please make sure only people who are allowed to know the password can access this file
  534.     Password: ""
  535.     # The name of the database which PremiumVanish should create its tables in
  536.     # Note: PremiumVanish won't create this database, it must be pre-created using eg. phpMyAdmin
  537.     Database: ""
  538.     # Not recommended; Makes PV use the standard JDBC connector instead of the more powerful multi-pooled HikariCP one
  539.     # You can give this a try if you have strange problems with connecting to your database
  540.     BasicDatabaseConnector: false
  541.  
  542.   AntiSpam:
  543.    # Should PV prevent spamming commands which can cause lag or spam the console?
  544.     # Bypass permission: pv.bypassspam
  545.     # ("/pv list" (if mysql is enabled), "/pv [on|off] <Player>" (mysql), "/pv reload" (+5secs), "/pv printstacktrace")
  546.     AntiSpamCheck: true
  547.     # If so, how many seconds should players have to wait before running such a command again?
  548.     AntiSpamDelay: 1
  549.     # Should AntiSpam always cover actions which toggle vanish? e.g. /pv, /pv <Player>
  550.     AlwaysCoverVanish: false
  551.  
  552.   Command:
  553.    # What should be PremiumVanish's main command?
  554.     Name: "pv"
  555.     # A list of possible aliases
  556.     Aliases:
  557.    - "premiumvanish"
  558.     - "v"
  559.     - "vanish"
  560.     # Should the aliases defined above override same-named commands of other plugins?
  561.     ForceOverrideForAliases: true
  562.  
  563.   UpdateChecker:
  564.    # Should PV check for updates on spigot regularly? There is no automatic update; this just informs you
  565.     Enable: true
  566.     # Should players with the permission 'pv.notify' get notified if the current version of PV is outdated?
  567.     NotifyAdmins: true
  568.  
  569. ##################################################
  570. ################# Do Not Touch ###################
  571. ##################################################
  572. ConfigVersion: 2.8.0
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement