SHARE
TWEET

Untitled

a guest Jun 14th, 2017 56 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. # PremiumVanish v1.9.5 - Configuration
  2.  
  3. ##################################################
  4. ############# Invisibility Features ##############
  5. ##################################################
  6. InvisibilityFeatures:
  7.   # Should invisible players get night vision? (client-side; Requires ProtocolLib)
  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)
  25.   OpenChestsSilently: true
  26.   # Should invisible players be able to open a player's inventory by right-clicking the player?
  27.   # Permission: pv.openplayerinv
  28.   OpenPlayerInventoryOnRightClick: true
  29.   # Should invisible players be able to edit inventories (including their own) even if they're in spectator mode?
  30.   # Permission: pv.spectatoreditinv
  31.   AllowSpectatorInventoryEdit: true
  32.   # Should invisible players not be able to trigger pressure plates and tripwire?
  33.   # If this feature is enabled invisible players can't trigger pressure plates and tripwire.
  34.   DisablePressurePlates: true
  35.   # Should invisible players not be able to push other players or be able to be pushed?
  36.   # WARNING: Uses the scoreboard and may conflict with other plugins!
  37.   DisablePush: true
  38.   # Should invisible players be hidden in the tablist?
  39.   # Note: Not every player hider supports showing invisible players
  40.   # in the tablist, please use the ProtocolLib hider to be able to turn this off
  41.   # (see the INVISIBILITY METHOD section below)
  42.   HideInTablist: true
  43.   # If HideInTablist is turned off, should players who can't see you not be able to
  44.   # see you as a spectator in the tablist even if you are in spectator mode?
  45.   HideSpectatorMode: true
  46.   # Should vanished players pick up items by default? This can be changed individually with /pv tipu
  47.   DefaultPickUpItemsOption: false
  48.   # The commands to execute when a player vanishs (online or offline)
  49.   # These commands are ran by console by default, you can use %p to get the player's name.
  50.   # You can also prefix the command with [P] to make the player run the command
  51.   # instead of the console (player online only)
  52.   # You can remove the brackets and make it a list if you'd like to enable this
  53.   VanishCommands: []
  54.   # The commands to execute when a player reappears (online or offline)
  55.   # These commands are ran by console by default, you can use %p to get the player's name.
  56.   # You can also prefix the command with [P] to make the player run the command
  57.   # instead of the console (player online only)
  58.   # You can remove the brackets and make it a list if you'd like to enable this
  59.   ReappearCommands: []
  60.   # For how many seconds should players not be able to take environmental damage after they reappear?
  61.   # e.g. fall damage or lava damage; Set to 0 to disable it
  62.   DisableEnvironmentalDamageAfterReappear: 5
  63.  
  64. ##################################################
  65. ############# Vanish State Features ##############
  66. ##################################################
  67. VanishStateFeatures:
  68.   # Should players with the permission 'pv.joinvanished' join vanished all the time?
  69.   # Doesn't work if you use GroupManager for permissions
  70.   AutoVanishOnJoin: true
  71.   # Should invisible players reappear automatically when they change their world?
  72.   ReappearOnWorldChange: false
  73.   # Should invisible players reappear automatically when they leave the server?
  74.   ReappearOnQuit: false
  75.   # Should invisible players reappear automatically
  76.   # when they change their world and don't have the permission 'pv.use' anymore?
  77.   CheckPermissionOnWorldChange: false
  78.   # Should invisible players reappear automatically
  79.   # when they leave the server and don't have the permission 'pv.use' anymore?
  80.   CheckPermissionOnQuit: false
  81.   # Should invisible players reappear automatically
  82.   # when they join the server and don't have the permission 'pv.use' anymore?
  83.   # Doesn't work if you use GroupManager for permissions
  84.   CheckPermissionOnLogin: false
  85.  
  86. ##################################################
  87. ############## Indication Features ###############
  88. ##################################################
  89. IndicationFeatures:
  90.   LayeredPermissions:
  91.     # Should players with the permission 'pv.see' be able to see invisible players in the tablist & in-game?
  92.     EnableSeePermission: true
  93.     # Should pv.use and pv.see be layered? => pv.use.levelX, pv.see.levelX
  94.     # Higher levels override; more information on Spigot
  95.     # Note: Layered permission levels are only updated on player join
  96.     LayeredSeeAndUsePermissions: true
  97.     # What should be the highest level for both permissions?
  98.     # Lower amounts might improve performance with more players since they reduce the amount of permission checks
  99.     MaxLevel: 100
  100.     # If LayeredSeeAndUsePermissions is enabled, should /pv list only show players which the command sender is
  101.     # allowed to see and should players only be able to toggle the invisibility of players which they are allowed
  102.     # to see (Only affects online players)?
  103.     HideInvisibleInCommands: true
  104.     # Should PremiumVanish iterate through all the permissions of a player instead of checking for all
  105.     # possible layered permissions? Enabling this may or may not improve PV's performance.
  106.     AlternatePermissionChecking: true
  107.   # Should vanished players show up dark gray in the tablist and should only their head be visible?
  108.   # Only players who are allowed to see the player will see this effect; this helps other staff with
  109.   # differentiating them from players they should talk to (Requires Combined or ProtocolLib hider)
  110.   MarkVanishedPlayersAsSpectators: false
  111. ##################################################
  112. ########### Survival Friendly Features ###########
  113. ##################################################
  114. SurvivalFriendlyFeatures:
  115.  
  116.   Fly:
  117.     # Should invisible players be able to fly even if they aren't in creative/spectator mode?
  118.     Enable: true
  119.     # Should invisible players WITHOUT the permission 'pv.fly' lose the ability to fly on reappear?
  120.     DisableOnReappear: true
  121.  
  122.   GameMode:
  123.     # The gamemode which players will get when they vanish
  124.     # 'Default' applies for every world which isn't mentioned below
  125.     # !! Warning: World names are case-sensitive !!
  126.     # Available gamemodes: SURVIVAL, ADVENTURE, CREATIVE, SPECTATOR, KEEP
  127.     # KEEP won't change the gamemode in any way
  128.     ChangeToOnVanish:
  129.       Default: SPECTATOR
  130.       ExampleWorld123: SPECTATOR
  131.     # The gamemode which players will get when they reappear
  132.     # 'Default' applies for every world which isn't mentioned below
  133.     # Available gamemodes: SURVIVAL, ADVENTURE, CREATIVE, SPECTATOR, KEEP
  134.     # KEEP won't change the gamemode in any way
  135.     ChangeToOnReappear:
  136.       Default: SURVIVAL
  137.       AnotherExampleWorld2: SURVIVAL
  138.     # Should PV update the gamemode 1 tick after a player joins/changes their world?
  139.     # The new gamemode will depend on the player's new world, as defined above
  140.     # Helpful if you want to force players to be in a gamemode in a specific world
  141.     # or if another plugin interferes with PV.
  142.     ReApplyGameModeChangeOnWorldChange: true
  143.     ReApplyGameModeChangeOnJoin: true
  144.     # Should the gamemode change when you join vanished *because of* your pv.joinvanished permission?
  145.     # Ignores the two settings above.
  146.     AlwaysApplyOnJoinVanished: true
  147.  
  148.   Location:
  149.     # Should vanished players be teleported back to where they vanished when they reappear?
  150.     # The location is saved in the playerdata.yml file and is therefore safe in case of a restart/crash
  151.     # Bypass permission: pv.bypassteleportback
  152.     TeleportBackOnReappear: false
  153.  
  154. ##################################################
  155. ################ Message Options #################
  156. ##################################################
  157. MessageOptions:
  158.  
  159.   FakeJoinQuitMessages:
  160.     # Should PV broadcast a fake quit message when a player vanishs?
  161.     # You can change this message in the messages.yml file.
  162.     BroadcastFakeQuitOnVanish: false
  163.     # Should PV broadcast a fake join message when a player reappears?
  164.     # You can change this message in the messages.yml file.
  165.     BroadcastFakeJoinOnReappear: false
  166.     # Should players with the permission 'pv.see' get a different message when a player vanishs/reappears?
  167.     # You can change this message in the messages.yml file.
  168.     AnnounceVanishReappearToAdmins: false
  169.     # Should only players with the permission 'pv.see' receive fake join/quit messages?
  170.     SendMessageOnlyToAdmins: false
  171.     # Should only players without the permission 'pv.see' receive fake join/quit messages?
  172.     SendMessageOnlyToUsers: false
  173.  
  174.   # Should PV hide the real join/leave messages of invisible players?
  175.   HideRealJoinQuitMessages: true
  176.   # Should PV hide leave messages for invisible players if 'VanishStateFeatures->ReappearOnQuit' is turned on?
  177.   # Overrides 'HideRealJoinQuitMessages'
  178.   ReappearOnQuitHideLeaveMsg: true
  179.   # If the setting above is turned on, should players with the permission 'pv.see' get
  180.   # a message when an invisible player joins/quits?
  181.   AnnounceRealJoinQuitToAdmins: true
  182.   # Should PV remind players who join the server vanished of being invisible (in chat)?
  183.   # You can change the message in the messages.yml file.
  184.   RemindVanishedOnJoin: true
  185.   # Should invisible players have an action bar which tells them that they're invisible?
  186.   # You can change the action bar in the messages.yml file.
  187.   DisplayActionBar: true
  188.  
  189. ##################################################
  190. ############## Restrictive Options ###############
  191. ##################################################
  192. RestrictiveOptions:
  193.   # Should invisible players not be able to break blocks?
  194.   # Bypass permission: pv.breakblocks
  195.   PreventBlockBreaking: false
  196.   # Should invisible players not be able to place blocks?
  197.   # Bypass permission: pv.placeblocks
  198.   PreventBlockPlacing: false
  199.   # Should invisible players not be able to interact with doors, levers, buttons, note blocks, etc?
  200.   # Doesn't prevent opening containers
  201.   # Bypass permission: pv.useblocks
  202.   PreventBlockUse: false
  203.   # Should invisible players not be able to interact with anything
  204.   # (blocks, buttons, pressure plates, chests, block breaking/placing, noteblocks, doors, ...)
  205.   # This setting overrides the three settings above
  206.   # Bypass permission: pv.interact
  207.   PreventInteract: false
  208.   # Should invisible players not be able to damage players or mobs?
  209.   # Bypass permission: pv.damage
  210.   PreventHittingEntities: false
  211.   # Should invisible players not be able to drop items?
  212.   # Bypass permission: pv.dropitems
  213.   PreventDroppingItems: false
  214.   # Should invisible players not be able to modify their own inventory?
  215.   # Bypass permission: pv.modifyowninv
  216.   PreventModifyingOwnInventory: false
  217.   # Should invisible players not be able to modify containers or other player's inventories?
  218.   # Overrides InvisibilityFeatures.AllowSpectatorInventoryEdit
  219.   # Bypass permission: pv.modifyotherinv
  220.   PreventModifyingOtherInventory: false
  221.   # Should invisible players not be able to tp to other players using the spectator menu?
  222.   # Bypass permission: pv.spectatortp
  223.   PreventSpectatorTeleporting: false
  224.   # Should invisible players in creative mode not be able to cheat items?
  225.   # Bypass permission: pv.creativeitems
  226.   PreventCreativeItemGrab: false
  227.   # Should invisible players not be able to view their coordinates? (client-side; Requires ProtocolLib)
  228.   # Bypass permission: pv.viewcoords
  229.   HiddenCoordinates: false
  230.  
  231.   Commands:
  232.     # Which commands should vanished players not be able to use?
  233.     # This blocks the 'plugin:command' syntax too but not aliases
  234.     # Bypass permission: pv.bypasscmd
  235.     VanishedCommandBlacklist:
  236.     - examplecommand123test
  237.     # Should vanished players only be able to use the commands listed above instead?
  238.     UseAsWhitelist: false
  239.  
  240. ##################################################
  241. ############# External Invisibility ##############
  242. ##################################################
  243. ExternalInvisibility:
  244.  
  245.   ServerList:
  246.     # The following features require ProtocolLib.
  247.     # Please use PremiumVanish's bungeecord configuration instead if you use Bungeecord.
  248.     #
  249.     # Should this plugin adjust the amount of players in the serverlist? (-1 per invisible player)
  250.     AdjustAmountOfOnlinePlayers: true
  251.     # Should this plugin hide invisible players in the list of logged in players?
  252.     # You can view this list when your mouse hovers over the amount of online players.
  253.     AdjustListOfLoggedInPlayers: true
  254.  
  255. ##################################################
  256. ############### Scoreboard Options ###############
  257. ##################################################
  258. ScoreboardOptions:
  259.   # Disable this if you don't need PremiumVanish's scoreboard features
  260.   # Note: If you are disabling this because it causes problems with other scoreboards/prefixes
  261.   # then you probably want to disable 'DisablePush' above as well since it uses the scoreboard too
  262.   Enable: true
  263.  
  264.   # Should players require the permission pv.scoreboard to view the scoreboard?
  265.   Permission: false
  266.  
  267.   Sidebar:
  268.     # The header/title of the scoreboard, you can use color codes here, default: '&6>       PremiumVanish       <'
  269.     # The length cannot be longer than 32 characters(including color codes) but will cause flickering
  270.     # if it isn't longer than the things below it
  271.     ScoreboardHeader: "&2>       &6MCSG&3Vanish       &2<"
  272.     # Should the scoreboard show the ping of the target?
  273.     ShowPing: true
  274.     # Should the scoreboard show the TPS(ticks per second, aka server lag) of the server?
  275.     ShowTPS: true
  276.     # Should the scoreboard show the current time and date?
  277.     # This uses the timezone of the server.
  278.     ShowTimeAndDate: true
  279.     # The format for the time and date if the setting above is enabled
  280.     # An explanation of what each alphabetic character means is here:
  281.     # http://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html
  282.     # You cannot use color codes here, the default syntax is: hh:mma | yyyy/MM/dd
  283.     TimeAndDateFormat: "hh:mma | yyyy/MM/dd"
  284.     # Should the scoreboard show the health of the target? (in hitpoints)
  285.     ShowHealth: true
  286.     # The interval between each update of the info on the scoreboard
  287.     # in ticks, decreasing this might decrease performance slightly
  288.     # 20 ticks equals to 1 second, default: 5
  289.     InfoUpdateInterval: 5
  290.  
  291.   Targeting:
  292.     # Should the scoreboard show information about the closest player automatically?
  293.     # If you're spectating, this option would always show the info of the player you're currently spectating.
  294.     AutoTargetClosestPlayer: true
  295.     # Should you target players when you right-click them?
  296.     # If both this option and 'OpenInventoryOnRightclick' is enabled then you
  297.     # are still able to lock a player by sneaking and right-clicking the player.
  298.     # (In spectator mode you can press space and shift at the same time for the same effect)
  299.     # If 'AutoTargetClosestPlayer' is enabled then it will stop targeting the closest player when
  300.     # you right-click a player until you type '/pv rs', same for /pv target <player> even if this option is disabled
  301.     TargetOnRightClick: true
  302.  
  303. ##################################################
  304. ################## Hook Options ##################
  305. ##################################################
  306. HookOptions:
  307.   # Should PV hide invisible players in /who, /list, /online, /near, etc?
  308.   # Note: Players with the permission essentials.vanish.interact can still see invisible players in these commands
  309.   # Important: You have to reload both PV and Essentials if you change this setting (reload PV first)
  310.   EnableEssentialsHook: true
  311.   # Should PV hide invisible players on your dynamic map and broadcast join/leave messages if you use Dynmap?
  312.   EnableDynmapHook: true
  313.   # Should PV send fake join/leave messages in dynmap's web-chat?
  314.   # You can configure the join/leave messages in the messages.yml file
  315.   DynmapSendJoinLeaveMessages: true
  316.   # Should PV prevent players from being invisible and disguised at the same time? (LibsDisguises commands)
  317.   # It's recommended to keep this turned on to prevent incompatibility.
  318.   EnableLibsDisguisesHook: true
  319.   # Should PV prevent players from being invisible and disguised at the same time? (DisguiseCraft commands)
  320.   # It's recommended to keep this turned on to prevent incompatibility.
  321.   EnableDisguiseCraftHook: true
  322.   # Should PV hook into TrailGUI and disable trails while you're vanished?
  323.   EnableTrailGUIHook: true
  324.   # Should PV hook into SuperTrails and disable trails while you're vanished?
  325.   EnableSuperTrailsHook: true
  326.   # Should PV hook into PlaceholderAPI and add new placeholders to PV + register its own ones for other plugins?
  327.   # Own ones: isvanished, vanishedplayers, playercount, bungeeplayercount
  328.   # Format: %premiumvanish_<placeholder>%
  329.   EnablePlaceholderAPIHook: true
  330.   # Should PV hook into MVdWPlaceholderAPI to add its own placeholders to Maxim's plugins?
  331.   # Own ones: isvanished, vanishedplayers, playercount, bungeeplayercount
  332.   # Format: {premiumvanish_<placeholder}
  333.   EnableMVdWPlaceholderAPIHook: true
  334.   # Should PV stop NPCs from greeting or talking about hidden players?
  335.   EnableCitizensHook: true
  336.   # Should PV hook into CustomParticleEffects and disable particles while you're vanished?
  337.   EnableCustomParticleEffectsHook: true
  338.   # Should PV use NametagEdit's API for prefixes and suffixes in the tablist?
  339.   EnableNametagEditHook: true
  340.   # Should PV hook into FeatherBoard to prevent incompatibilities with its scoreboard?
  341.   EnableFeatherBoardHook: true
  342.  
  343. ##################################################
  344. ############## Invisibility Method ###############
  345. ##################################################
  346. InvisibilityMethod:
  347.   # The method of hiding players; Available methods: Bukkit, ProtocolLib, Combined
  348.  
  349.   # 'Bukkit': Uses Bukkit's API to hide players, this is an extremely reliable method if other plugins don't break it.
  350.   # This method ALWAYS hides invisible players in the tablist for players that can't see them.
  351.   # The chance that another plugin breaks this method is medium depending on the amount and type of plugins.
  352.   # > Recommended if other hiders kick you with an exception in bungee; other plugins can break this method though
  353.   # (Accuracy: 95%) (Plugin compatibility: 90%)
  354.  
  355.   # 'ProtocolLib': Uses ProtocolLib to hide players. Takes the whole packet stuff into its own hands to cancel every
  356.   # single packet of hidden players.
  357.   # This method CAN show invisible players in the tablist for players who can't see them if that's enabled.
  358.   # Hard to break, however, other plugins might not provide direct support for this hider; Use 'Bukkit' if this kicks you
  359.   # > Obviously requires ProtocolLib; Recommended if you want to show invisible players in the tablist
  360.   # (Accuracy: 90%) (Plugin compatibility: 95%)
  361.  
  362.   # 'Combined: Uses both ProtocolLib and Bukkit's API to hide players, this method does NOT support showing players
  363.   # in the tablist but it contains two layers of security and is therefore an extremely effective method.
  364.   # The chance that another plugin breaks this method is extremely small; Use 'Bukkit' if this kicks you
  365.   # > Requires ProtocolLib; Default hider; Recommended if you don't want to show invisible players in the tablist
  366.   # (Accuracy: 100%) (Plugin compatibility: 98%) - DEFAULT
  367.  
  368.   PlayerHider: "Combined"
  369.  
  370.   # Note: Even 'Combined' can't stop players from figuring out whether invisible players are online if another
  371.   # plugin tells them but players will never be able to see them at all or figure out their location
  372.   # (Essentials is 99% compatible)
  373.  
  374.   # Should the Combined and ProtocolLib hiders intercept Scoreboard Team packets too? It prevents
  375.   # non-existing but theoretically possible hacked clients from figuring out whether an invisible
  376.   # player is online however it can also cause problems with tablist player prefixes and suffixes
  377.   # by other plugins.
  378.   StrictInvisibility: true
  379.  
  380.   # Should the Combined and Bukkit hiders force players into being invisible every tick (Bukkit) or every
  381.   # second (Combined)? This may cause lag if there are lots of players on the server.
  382.   ForcedInvisibility: true
  383.  
  384. ##################################################
  385. ############# Compatibility Options ##############
  386. ##################################################
  387. CompatibilityOptions:
  388.   # This section is for advanced users only!
  389.   # The event priority which PremiumVanish should use for the specific event.
  390.   # Allowed values are LOWEST, LOW, NORMAL, HIGH, HIGHEST and MONITOR
  391.   # Higher priorities might override other plugins while lower ones might not
  392.  
  393.   # The priority for removing the join message
  394.   PlayerJoinEventPriority: HIGH # <- keep HIGH if you use Essentials to modify join/quit messages !!
  395.   # The priority for removing the quit message
  396.   PlayerQuitEventPriority: HIGH
  397.   # The priority for cancelling chat messages
  398.   AsyncPlayerChatEventPriority: HIGH
  399.   # The priority for cancelling commands
  400.   PlayerCommandPreprocessEventPriority: HIGH
  401.  
  402.   # Should the Combined and ProtocolLib method of hiding players not intercept tab packets?
  403.   # Fixes players getting kicked from the server when they tab-complete and BungeeCord is installed and
  404.   # another plugin messes around with packets too
  405.   DisableHandlingOfTabulatorPackets: false
  406.  
  407. ##################################################
  408. ############# Miscellaneous Options ##############
  409. ##################################################
  410. MiscellaneousOptions:
  411.  
  412.   Bungeecord:
  413.     # Should PremiumVanish store its data in a MySQL-Database and enable Bungeecord support?
  414.     # Bungeecord is not required for this feature but it's recommended!
  415.     # PremiumVanish will be disabled if this is enabled and the connection to the database failed.
  416.     Enable: true
  417.     # The ip of your database server
  418.     Ip: "hidden"
  419.     # The port of your database, usually 3306; just leave it empty if there is no specific port
  420.     Port: "hidden"
  421.     # The name of your database user
  422.     User: "hidden"
  423.     # The password of your database user
  424.     # WARNING: Make sure only people who are allowed to know the password can access this file
  425.     Password: "hidden"
  426.     # You can make PremiumVanish ignore all of the options above and use a direct URI to connect instead
  427.     CustomURI: ""
  428.     # The name of the database which PremiumVanish should create its tables in
  429.     # Note: PremiumVanish won't create this database, it must be pre-created using eg. phpMyAdmin
  430.     Database: "hidden"
  431.  
  432.   AntiSpam:
  433.     # Should PV prevent spamming commands which can cause lag or spam the console?
  434.     # Bypass permission: pv.bypassspam
  435.     # ("/pv list" (if mysql is enabled), "/pv [on|off] <Player>" (mysql), "/pv reload" (+5secs), "/pv printstacktrace")
  436.     AntiSpamCheck: true
  437.     # If so, how many seconds should players have to wait before running such a command again?
  438.     AntiSpamDelay: 1
  439.     # Should AntiSpam always cover actions which toggle vanish? e.g. /pv, /pv <Player>
  440.     AlwaysCoverVanish: false
  441.  
  442.   Command:
  443.     # What should be premiumvanish's main command?
  444.     Name: "pv"
  445.     # A list of possible aliases
  446.     Aliases:
  447.     - "premiumvanish"
  448.     # Replaces Essentials' standard vanish commands, you can still use them by doing /ev or /evanish
  449.     - "v"
  450.     - "vanish"
  451.     # Used as an alias for /pv list
  452.     - "vlist"
  453.     # Should the aliases defined above override ANY commands of other plugins instead of just other aliases?
  454.     ForceOverrideForAliases: true
  455.  
  456.   UpdateChecker:
  457.     # Should PV check for updates on spigot regularly?
  458.     Enable: false
  459.     # Should players with the permission 'pv.notify' get notified if the current version of PV is outdated?
  460.     NotifyAdmins: false
  461.  
  462. ##################################################
  463. ################# Do Not Touch ###################
  464. ##################################################
  465. ConfigVersion: 1.9.5
RAW Paste Data
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
 
Top