API tools faq
paste
Guest User

PV Config v2.9.23

a guest
Jun 29th, 2025
604
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 32.18 KB | None | 0 0
raw download clone embed print report
  1. # PremiumVanish v2.9.23 - 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! Not recommended to use anymore.
  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.  
  169. Fly:
  170. # Should invisible players with the permission pv.fly be able to fly even if they aren't in creative/spectator mode?
  171. Enable: true
  172. # Should invisible players WITHOUT the permission 'pv.keepfly' lose the ability to fly on reappear?
  173. DisableOnReappear: true
  174.  
  175. GameMode:
  176. # The gamemode which players will get when they vanish
  177. # 'Default' applies for every world which isn't mentioned below
  178. # !! Warning: World names are case-sensitive !!
  179. # Available gamemodes: SURVIVAL, ADVENTURE, CREATIVE, SPECTATOR, KEEP
  180. # KEEP won't change the gamemode in any way
  181. ChangeToOnVanish:
  182. Default: KEEP
  183. ExampleWorld123: SPECTATOR
  184. # The gamemode which players will get when they reappear
  185. # 'Default' applies for every world which isn't mentioned below
  186. # Available gamemodes: SURVIVAL, ADVENTURE, CREATIVE, SPECTATOR, KEEP
  187. # KEEP won't change the gamemode in any way
  188. ChangeToOnReappear:
  189. Default: KEEP
  190. AnotherExampleWorld2: SURVIVAL
  191. # Should PV update the gamemode 1 tick after a player joins/changes their world?
  192. # The new gamemode will depend on the player's new world, as defined above
  193. # Helpful if you want to force players to be in a gamemode in a specific world
  194. # or if another plugin interferes with PV.
  195. ReApplyGameModeChangeOnWorldChange: true
  196. ReApplyGameModeChangeOnJoin: true
  197. # Should the gamemode change when you join vanished *because of* your pv.joinvanished permission?
  198. # Ignores the two settings above.
  199. AlwaysApplyOnJoinVanished: true
  200. # Whether to require the permission pv.gamemode to change the player's gamemode with the settings above
  201. RequirePermission: false
  202.  
  203. Location:
  204. # Should vanished players be teleported back to where they vanished when they reappear?
  205. # The location is saved in the data.yml file and is therefore safe in case of a restart/crash
  206. # Bypass permission: pv.bypassteleportback
  207. TeleportBackOnReappear: false
  208.  
  209. ##################################################
  210. ################ Message Options #################
  211. ##################################################
  212. MessageOptions:
  213.  
  214. MessagesOnVanishReappear:
  215. # Should PV broadcast any kind of announcement (fake quit or player vanished) when a player vanishes?
  216. # You can change the messages in the messages.yml file.
  217. BroadcastMessageOnVanish: true
  218. # Should PV broadcast any kind of announcement (fake join or player reappeared) when a player reappears?
  219. # You can change the messages in the messages.yml file.
  220. BroadcastMessageOnReappear: true
  221. # Should players with permission to see the player get an announcement instead of a fake join/quit message?
  222. # The vanishing/reappearing player will always get the fake join/quit message.
  223. AdminsGetAnnouncementInstead: true
  224. # Should there only be announcements and no fake join/quit messages?
  225. # This means players without permission to see the player don't get any message.
  226. DontSendFakeJoinQuit: false
  227. # Should there only be fake join/quit messages and no announcements?
  228. # This means players with permission to see the player don't get any message.
  229. DontSendAdminAnnouncements: false
  230.  
  231. MessagesOnJoinQuit:
  232. # Should PV hide the real join/quit messages of invisible players?
  233. HideRealJoinQuitMessages: true
  234. # Should players with permission to see a vanished player get an announcement when they actually join/quit?
  235. AnnounceRealJoinQuit: true
  236. # Should PV still hide quit messages for invisible players if 'VanishStateFeatures->ReappearOnQuit' is turned on?
  237. # Overrides 'HideRealJoinQuitMessages'
  238. ReappearOnQuitHideMessage: true
  239. # Should PV remind players who join the server vanished of being invisible (in chat)?
  240. # You can change the message in the messages.yml file.
  241. RemindVanishedOnJoin: true
  242.  
  243. # Should invisible players have an action bar which tells them that they're invisible?
  244. # You can change the action bar in the messages.yml file.
  245. DisplayActionBar: true
  246.  
  247. ##################################################
  248. ############## Restrictive Options ###############
  249. ##################################################
  250. RestrictiveOptions:
  251. # Should invisible players not be able to break blocks?
  252. # Bypass permission: pv.breakblocks
  253. PreventBlockBreaking: false
  254. # Should invisible players not be able to place blocks?
  255. # Bypass permission: pv.placeblocks
  256. PreventBlockPlacing: false
  257. # Should invisible players not be able to interact with doors, levers, buttons, note blocks, etc?
  258. # Doesn't prevent opening containers
  259. # Bypass permission: pv.useblocks
  260. PreventBlockUse: false
  261. # Should invisible players not be able to interact with anything
  262. # (blocks, buttons, pressure plates, chests, block breaking/placing, noteblocks, doors, ...)
  263. # This setting overrides the three settings above
  264. # Bypass permission: pv.interact
  265. PreventInteract: false
  266. # Should invisible players not be able to damage players or mobs?
  267. # Bypass permission: pv.damage
  268. PreventHittingEntities: false
  269. # Should invisible players not be able to drop items?
  270. # Bypass permission: pv.dropitems
  271. PreventDroppingItems: false
  272. # Should invisible players not be able to modify their own inventory?
  273. # Bypass permission: pv.modifyowninv
  274. PreventModifyingOwnInventory: false
  275. # Should invisible players not be able to modify containers or other player's inventories?
  276. # Overrides InvisibilityFeatures.AllowSpectatorInventoryEdit
  277. # Bypass permission: pv.modifyotherinv
  278. PreventModifyingOtherInventory: false
  279. # Should invisible players not be able to tp to other players using the spectator menu?
  280. # Bypass permission: pv.spectatortp
  281. PreventSpectatorTeleporting: false
  282. # Should invisible players in creative mode not be able to cheat items?
  283. # Bypass permission: pv.creativeitems
  284. PreventCreativeItemGrab: false
  285. # Should invisible players not be able to view their coordinates? (client-side)
  286. # Bypass permission: pv.viewcoords
  287. HiddenCoordinates: false
  288.  
  289. Commands:
  290. # Which commands should vanished players not be able to use?
  291. # This blocks the 'plugin:command' syntax too but not aliases
  292. # Bypass permission: pv.bypasscmd
  293. VanishedCommandBlacklist:
  294. - examplecommand123test
  295. - anotherexamplecommand123
  296. # Should vanished players only be able to use the commands listed above instead?
  297. UseAsWhitelist: false
  298.  
  299. ##################################################
  300. ############# External Invisibility ##############
  301. ##################################################
  302. ExternalInvisibility:
  303.  
  304. ServerList:
  305. # Please use PremiumVanish's bungeecord configuration instead if you use Bungeecord.
  306. #
  307. # Should this plugin adjust the amount of players in the serverlist? (-1 per invisible player)
  308. AdjustAmountOfOnlinePlayers: true
  309. # Should this plugin hide invisible players in the list of logged in players?
  310. # You can view this list when your mouse hovers over the amount of online players.
  311. AdjustListOfLoggedInPlayers: true
  312.  
  313. ##################################################
  314. ############### Scoreboard Options ###############
  315. ##################################################
  316. ScoreboardOptions:
  317. # Disable this if you don't need PremiumVanish's scoreboard features
  318. # You can also toggle your scoreboard with the '/pv scoreboard' command
  319. #
  320. # Note: If you are disabling this because it causes problems with other scoreboards/prefixes
  321. # then you probably want to disable 'DisablePush' above as well since it uses the scoreboard too
  322. Enable: true
  323.  
  324. # Should players require the permission pv.scoreboard to view the scoreboard?
  325. Permission: false
  326.  
  327. Sidebar:
  328. # The header/title of the scoreboard, default: '&6> PremiumVanish <'
  329. # The length cannot be longer than 32 characters(including color codes) but can cause flickering
  330. # if it isn't longer than the lines below it
  331. ScoreboardHeader: "&6> PremiumVanish <"
  332. # The lines of PremiumVanish's scoreboard
  333. # Prefix a line with a # if it should only show up if there is a target (the placeholders will
  334. # also be based on the target)
  335. # A line can never be longer than 32 characters (watch out for player names, which can be up to 16 chars long)
  336. # All general placeholders that work in the messages.yml file work here, too.
  337. # Additionally to the messages.yml placeholders you can use %target% and %locked% (if the target has been fixed).
  338. Lines:
  339. - ""
  340. - "&aTarget: &f%target% %locked%"
  341. - "#"
  342. # The color of the ping is based on how good the ping is, use %plain_ping% for no colors; same with tps
  343. - "#&aPing: &f%ping%"
  344. - ""
  345. - "&aTPS: &f%tps%"
  346. - "#"
  347. - "#&aHealth: &f%health%/%maxhealth%hp"
  348. - ""
  349. - "&aTime: &f%time{hh:mma | yyyy/MM/dd}%"
  350. - ""
  351. # The interval between each update of the info on the scoreboard
  352. # in ticks, decreasing this might decrease performance slightly
  353. # 20 ticks equals to 1 second, default: 5
  354. InfoUpdateInterval: 5
  355. Targeting:
  356. # Should the scoreboard show information about the closest player automatically?
  357. # If you're spectating, this option would always show the info of the player you're currently spectating.
  358. # Permission to be exempted from being targeted automatically: pv.exempttarget
  359. AutoTargetClosestPlayer: true
  360. # Should you target players when you right-click them?
  361. # If both this option and 'OpenPlayerInventoryOnRightClick' is enabled then you
  362. # are still able to lock a player by sneaking and right-clicking the player.
  363. # (In spectator mode you can press space and shift at the same time for the same effect)
  364. # If 'AutoTargetClosestPlayer' is enabled then it will stop targeting the closest player when
  365. # you right-click a player until you type '/pv unlock', same for /pv target <player> even if this option
  366. # is disabled
  367. TargetOnRightClick: true
  368. # Should your current target glow (only you see this effect)?
  369. # This feature is currently not supported on 1.19.3 or higher.
  370. TargetGlows: true
  371.  
  372. ##################################################
  373. ################## Hook Options ##################
  374. ##################################################
  375. HookOptions:
  376. # Should PV hide invisible players in /who, /list, /online, /near, etc?
  377. # Note: Players with the permission essentials.vanish.interact can still see invisible players in these commands
  378. # Important: You have to reload both PV and Essentials if you change this setting (reload PV first)
  379. EnableEssentialsHook: true
  380. # Should PV hide invisible players on your dynamic map and broadcast join/leave messages if you use Dynmap?
  381. EnableDynmapHook: true
  382. # Should PV send fake join/leave messages in dynmap's web-chat?
  383. # You can configure the join/leave messages in the messages.yml file
  384. DynmapSendJoinLeaveMessages: true
  385. # Should PV prevent players from being invisible and disguised at the same time? (LibsDisguises commands)
  386. # It's recommended to keep this turned on to prevent incompatibility.
  387. EnableLibsDisguisesHook: true
  388. # Should PV prevent players from being invisible and disguised at the same time? (DisguiseCraft commands)
  389. # It's recommended to keep this turned on to prevent incompatibility.
  390. EnableDisguiseCraftHook: true
  391. # Should PV hook into TrailGUI and disable trails while you're vanished?
  392. EnableTrailGUIHook: true
  393. # Should PV hook into SuperTrails and disable trails while you're vanished?
  394. EnableSuperTrailsHook: true
  395. # Should PV hook into PlaceholderAPI and add new placeholders to PV + register its own ones for other plugins?
  396. # Own ones: isvanished, vanishprefix, vanishsuffix, vanishedplayers, playercount, bungeeplayercount, bungeeplayercount@<server>,
  397. # playercountwithoutshowintab, target, uselevel, seelevel
  398. # Format: %premiumvanish_<placeholder>%
  399. #
  400. # The bungee placeholders require PV to be installed on bungee and set up with a MySQL database on all servers.
  401. # They neither account for the showintab flag nor for the amount of vanished players that you are allowed to see.
  402. #
  403. # The result of the isvanished placeholder can be edited by changing HelpConsoleYes/No in the messages.yml file.
  404. EnablePlaceholderAPIHook: true
  405. # Should PV hook into MVdWPlaceholderAPI and add new placeholders to PV + register its own ones for other
  406. # plugins?
  407. # Own ones: isvanished, vanishprefix, vanishsuffix, vanishedplayers, playercount, bungeeplayercount, bungeeplayercount@<server>,
  408. # playercountwithoutshowintab, target, uselevel, seelevel
  409. # Format: {premiumvanish_<placeholder>}
  410. #
  411. # The bungee placeholders require PV to be installed on bungee and set up with a MySQL database on all servers.
  412. # They neither account for the showintab flag nor for the amount of vanished players that you are allowed to see.
  413. #
  414. # The result of the isvanished placeholder can be edited by changing HelpConsoleYes/No in the messages.yml file.
  415. EnableMVdWPlaceholderAPIHook: true
  416. # Should PV stop NPCs from greeting or talking about hidden players?
  417. EnableCitizensHook: true
  418. # Should PV hook into CustomParticleEffects and disable particles while you're vanished?
  419. EnableCustomParticleEffectsHook: true
  420. # Should PV use NametagEdit's API to prevent incompatibilities with its prefixes/suffixes?
  421. EnableNametagEditHook: true
  422. # Should PV hook into FeatherBoard to prevent incompatibilities with its scoreboard?
  423. EnableFeatherBoardHook: true
  424. # Should PV hook into EnjinMinecraftPlugin to prevent vanished players from showing up on its website?
  425. EnableEnjinMinecraftPluginHook: true
  426. # Should PV hook into CMI to prevent vanished players from entering AFK state?
  427. EnableCMIHook: true
  428. # Should PV hook into DiscordSRV to broadcast fake join/quit messages on Discord?
  429. EnableDiscordSRVHook: true
  430. # Should PV hook into TitleManager to prevent incompatibilities with its scoreboard?
  431. EnableTitleManagerHook: true
  432. # Should PV hook into RedisChat to add a vanish integration?
  433. EnableRedisChatHook: true
  434. # Should PV hook into Pl3xMap to hide vanished players in its online map?
  435. EnablePl3xMapHook: true
  436. ##################################################
  437. ############## Invisibility Method ###############
  438. ##################################################
  439. InvisibilityMethod:
  440. # The method of hiding players; Available methods: Prevention, Interception, Hybrid
  441.  
  442. # 'Prevention': Uses Bukkit's API to hide players, this is an extremely reliable method if other plugins don't break it.
  443. # This method ALWAYS hides invisible players in the tablist for players that can't see them.
  444. # The chance that another plugin breaks this method is low depending on the amount and type of plugins.
  445. # > Recommended if other hiders cause issues; other plugins can break this method though
  446. # (Accuracy: 95%) (Plugin compatibility: 95%) (Uses game layer invisibility)
  447.  
  448. # 'Interception': Uses ProtocolLib to hide players. Takes the whole packet stuff into its own hands to cancel every
  449. # single packet of hidden players. This option is currently not supported on 1.19.3 or higher.
  450. # This method CAN show invisible players in the tablist for players who can't see them if that's enabled.
  451. # Hard to break, however, other plugins might not provide direct support for this hider
  452. # It's important to note that Essentials might not recognize vanished players as vanished in its commands with this hider.
  453. # > Recommended if you want to show invisible players in the tablist
  454. # (Accuracy: 95%) (Plugin compatibility: 90%) (Uses protocol layer invisibility)
  455.  
  456. # 'Hybrid: Uses both ProtocolLib and Bukkit's API to hide players, this method does NOT support showing players
  457. # in the tablist but it contains two layers of security and is therefore an extremely effective method.
  458. # The chance that another plugin breaks this method is extremely small
  459. # > Default hider; Recommended if you don't want to show invisible players in the tablist
  460. # (Accuracy: 100%) (Plugin compatibility: 98%) (Uses game and protocol layer invisibility) - DEFAULT
  461.  
  462. PlayerHider: "Hybrid"
  463.  
  464. # Note: Even 'Hybrid' can't stop players from figuring out whether invisible players are online if another
  465. # plugin tells them but players will never be able to see them at all or figure out their location
  466. # (Essentials is 99% compatible)
  467.  
  468. Advanced:
  469. # Advanced section which affects the protocol layer invisibility for the Interception and Hybrid hiders
  470.  
  471. # Which protocol layer invisibility modules should be disabled?
  472. # You can disable some modules here if they are causing issues or aren't supported on
  473. # your server after an update or if you are using the Interception hider and simply don't want players
  474. # to be invisible in some regards.
  475. # You are unlikely to note invisibility changes here if you are using the Hybrid hider since it also has
  476. # game layer invisibility which isn't affected here
  477. # It's recommended to instead use the HideInTablist/Game options if that's what you want to change
  478. DisabledInvisibilityModules:
  479. # Physical appearance in the game
  480. # - GeneralEntity
  481. # Sounds in the world
  482. # - NamedSoundEffect
  483. # Tablist entry (includes hide spectator mode feature)
  484. # Please uncomment this if you are using Maximvdw's Tab or AnimatedNames plugin and have issues with nametags
  485. # - PlayerInfo
  486. # Info about player prefixes, suffixes, etc (formerly 'StrictInvisibility'); this is
  487. # disabled by default since it is very likely to cause issues with nametag/prefix plugins
  488. # Comment this out (enable it) if it doesn't cause issues, since it can prevent vanished player information leaks
  489. - ScoreboardTeam
  490. # Tab completion suggestions (formerly 'DisableHandlingOfTabulatorPackets')
  491. # Enable this module if you don't use bungeecord. It's disabled by default to prevent issues with bungee
  492. - TabComplete
  493. # Particles in the world
  494. # - WorldParticles
  495.  
  496. ##################################################
  497. ############# Compatibility Options ##############
  498. ##################################################
  499. CompatibilityOptions:
  500. # This section is for advanced users only!
  501. # The event priority which PremiumVanish should use for the specific event.
  502. # Allowed values are LOWEST, LOW, NORMAL, HIGH, HIGHEST and MONITOR
  503. # Higher priorities might override other plugins while lower ones might not
  504.  
  505. # The priority for removing the join message
  506. PlayerJoinEventPriority: HIGH # <- keep HIGH if you use Essentials to modify join/quit messages !!
  507. # The priority for removing the quit message
  508. PlayerQuitEventPriority: HIGH
  509. # The priority for cancelling chat messages
  510. AsyncPlayerChatEventPriority: HIGH
  511. # The priority for cancelling commands
  512. PlayerCommandPreprocessEventPriority: HIGH
  513. # A whitelist of command usages where it should be allowed to tab-complete vanished players that you can't see.
  514. # You can use this for commands that generally tab-complete any player, online or not.
  515. # This section is for advanced users only and uses regular expressions.
  516. # For changes to apply you need to change this on all spigot servers and on the bungee if you're using bungee.
  517. TabCompleteWhitelist:
  518. - "/(ps|plotsquared|p2|2|plotme|plot|p)\\s(visit|v|tp|teleport|goto|warp).*"
  519.  
  520. ##################################################
  521. ############# Miscellaneous Options ##############
  522. ##################################################
  523. MiscellaneousOptions:
  524.  
  525. Bungeecord:
  526. # Should PremiumVanish store its data in a MySQL-Database and enable Bungeecord support?
  527. # Bungeecord is not required for this feature but it's recommended!
  528. # PremiumVanish will be disabled if this is enabled and the connection to the database failed.
  529. #
  530. # Important: Please make sure that ip-forwarding is enabled on your Bungee AND your Bukkit servers.
  531. # It's also important that your database is firewalled so it's not accessible from the internet.
  532. Enable: false
  533. # The ip of your database server
  534. Ip: ""
  535. # The port of your database, usually 3306; just leave it empty if there is no specific port
  536. Port: "3306"
  537. # You can make PremiumVanish ignore the two options above and use a direct URI to connect instead
  538. # Format for MySQL servers: jdbc:mysql://<yourIp>:<yourPort>/<yourDatabase>?useSSL=false
  539. CustomURI: ""
  540. # The name of your database user
  541. User: ""
  542. # The password of your database user
  543. # WARNING: Please make sure only people who are allowed to know the password can access this file
  544. Password: ""
  545. # The name of the database which PremiumVanish should create its tables in
  546. # Note: PremiumVanish won't create this database, it must be pre-created using eg. phpMyAdmin
  547. Database: ""
  548. # Not recommended; Makes PV use the standard JDBC connector instead of the more powerful multi-pooled HikariCP one
  549. # You can give this a try if you have strange problems with connecting to your database
  550. BasicDatabaseConnector: false
  551.  
  552. AntiSpam:
  553. # Should PV prevent spamming commands which can cause lag or spam the console?
  554. # Bypass permission: pv.bypassspam
  555. # ("/pv list" (if mysql is enabled), "/pv [on|off] <Player>" (mysql), "/pv reload" (+5secs), "/pv printstacktrace")
  556. AntiSpamCheck: true
  557. # If so, how many seconds should players have to wait before running such a command again?
  558. AntiSpamDelay: 1
  559. # Should AntiSpam always cover actions which toggle vanish? e.g. /pv, /pv <Player>
  560. AlwaysCoverVanish: false
  561.  
  562. Command:
  563. # What should be PremiumVanish's main command?
  564. Name: "pv"
  565. # A list of possible aliases
  566. Aliases:
  567. - "premiumvanish"
  568. - "v"
  569. - "vanish"
  570. # Should the aliases defined above override equally-named commands of other plugins?
  571. ForceOverrideForAliases: true
  572.  
  573. UpdateChecker:
  574. # Should PV check for updates on spigot regularly? There is no automatic update; this just informs you
  575. Enable: true
  576. # Should players with the permission 'pv.notify' get notified if the current version of PV is outdated?
  577. NotifyAdmins: true
  578.  
  579. ##################################################
  580. ################# Do Not Touch ###################
  581. ##################################################
  582. ConfigVersion: 2.9.23
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!