• You can always go on a Server with the mod installed and see how they setup the mod and how it works
• I offer a Test Version for Advanced Groups for 30€ so you can test everything you want on your own server for 2 weeks
• You can also buy my mod. You will not regret it ;)

• Try to contact Discord to recover access to your account

• Create a new account and use the new account to login on my website. To transfer the products to the new account, you can claim them on the customer panel by entering the servername and license key you should have received via Email after you purchased the mod. If you did not receive any email, you can send me an email to confirmation@lbmaster.de from the same email you used to purchase the mods. Also include proof of buying the mods like a screenshot of the paypal transaction and which mods you had. Then I will send you the license key and servernames you need to claim the products. For how the claim process works exactly, check out This FAQ Entry

• PayPal account
• Credit Card

• Credit Card
• Apple Pay
• Google Pay (Only in google chrome when logged in to Google Pay)
• WeChat Pay
• EPS
• iDeal

• The Testserver is clearly marked as one by having something like "Test Server" in the Servers hostname
• The Testserver has a password, which is not publicly known
• The Max players are limited to a maximum of 10 players
• The IP of the Testserver is whitelisted on the Customer Panel if it is different from the IP of your Main Server

• bold make the text bold
• underline (currently not implemented) will make the text underlined
• italic make the text italic
• argb(A,R,G,B) replace A,R,G and B with the ARGB color values from 0 to 255 to change the color of the text in this line
• rgb(R,G,B) same as above, but alpha channel will be 255 (full) by default
• size(PX) set the size of the text in pixels. Default size is 16
• left Sets the text alignment to left (default alignment)
• right Sets the text alignment to right
• center Sets the text alignment to center
• outline(A,R,G,B,SIZE) add a colored outline around the text with the ARGB color values and the size (0-10)
• shadow(A,R,G,B,SIZE,OPACITY,OFFSET_X,OFFSET_Y) add a text shadow with the ARGB color values, the size (0-10), Opacity (0.0 - 1.0), X Offset (0.0 - 10.0) and Y Offset (0.0 - 10.0). The last 3 values are optional
• sectionStart(INDENT,OPEN) starts a new section of text, which can be expanded (INDENT in pixels how far the new section will be moved in, OPEN (0 = closed by default, 1 = open by default). The line where the sectionStart argument is in, will be the line, which can be clicked to open and close the section
• sectionEnd must be placed into the arguments list of the last element, which should be in the current opened section. Do not Start and End a section in the same line
• img(PATH) or img(PATH,WIDTH,HEIGHT) PATH is the path to the image. Width and height are in pixels. To automatically calculate the height or the width based on the image size to not stretch it, you can use a as an argument for the width and set the height ot what you need. Same works for when setting the height to a. The img(PATH) is equal to img(PATH,a,a). Example: img(LBmaster_Groups/gui/images/heavy_crafting.paa,a,250)

• $args(size(30),center,rgb(255,0,0));Rules: "Rules" displayed in red, centered and with a size of 30 pixels

Spaces in the Playername should be replaced by _
Name of the Player is caseinsensitive.
!mute [PlayerName] [Time in Minutes]
!muteid [Steamid or BIUID] [Time in Minutes]
!unmute [PlayerName]
!unmuteid [Steamid or BIUID]
!mutechannel [Channelname]
!unmutechannel [Channelname]
!mutereloadconfig
mutereloadconfig rereads the current ChatConfig.json. Which makes it possible to add Chat Admins while the Server is running or Change Prefix Colors or add Channels ...

!mutevote [PlayerName] -> All Players can vote for a player to be muted without admin. Important ChatConfig Variables: 
  - "enableMuteVote" enable / disable voting
  - "muteVoteMinPlayers" minimal Players for voting
  - "muteVotePercentile" amount of players, that need to vote for the player (e.g. 30 Players online and 50% need to vote -> 15 Players need to vote for the player)
  - "muteVoteMuteTimeMins" time the player will be muted if vote was successful

Example:
!mute LBmaster 20 -> Mute Player LBmaster for 20mins
!muteid 76561198141097113 20 -> Mute Player With Steamid "76561198141097113" for 20 mins (would find LBmaster)
!muteid 4e6J9rBov9EChLGlp-ckzyAbUh_tvlzXXBrFR7pSS-4= 20 -> Mute Player With Bohemia Interactive UID "4e6J9rBov9EChLGlp-ckzyAbUh_tvlzXXBrFR7pSS-4=" for 20 mins (would find LBmaster)

1. Download the MapIconFix_Original_Icons.pbo from here. This is on your own risk, because this PBO contains the original VPP Map Icons I asked DaOne, the creator of the Mod, if I can use his Icons or if he can fix it, but for me it seemed, he doesn't care. I would suggest leaving him a PM if you add this PBO to your Serverpack.
2. Download the MapIconFix_Empty_Icons.pbo from here. This does not contain any material from the original VPP Map. I replaced every Icon with a invisible texture. So you don't have the white boxes, but also You don't have any special Icons.

• This System only extends the functionality of the vanilla TerritoryFlag item and does not add any new Items
• This mod requires Advanced Groups and is designed to assign each Flag one group, so they don't have to add members manually like with other Mods
• This mod should not be used together with other territory Mods like Basic Territories
• Before you install it, make sure no TerritoryFlag exists on the Map or wipe the server completely

• All items around will be refreshed. That means, all items with a higher lifetime will never despawn as long as the flag is up, because the lifetime it reset to the max when this timer runs out, before the lifetime of the object could run out.
• This is the time when the Flag is visually updated. So that's the point where the flag will go down a bit. So be aware, that having this value set too high relative to the Uptime duration, you might end up with flags jumping from 100% to 50% in one go.

• The flagUptimeDuration should be at least 5 to 10 times the flagLifetimeRefreshTime to not have too big steps when the flag is lowering.
• All items, which should not be refreshed have a lower lifetime than the flagLifetimeRefreshTime.
• All items, which should be refreshed have a higher lifetime than the flagLifetimeRefreshTime. Don't forget the TerritoryFlag must have a higher lifetime too !

• The flag will lower 10% every 3 Days (3 Days / 30 Days = 0.1 = 10%)
• All Basebuilding items will be protected from despawning for 30 Days unless someone raises the flag again to start the 30 Days again.
• Once the Flag is lowered to 0% after the 30 Days or someone lowered it manually, all items will be refreshed once more leaving the base with 4 remaining days until everything despawns.
• In total the Base will remain at least 34 Days when not touched (flag raised or lowered) again by a player

1. Go to your Discord Server
2. Create a Channel where you want the messages to be sent to or just use an existing channel
3. Edit the Channel and navigate to Integrations
4. Click on New Webhook or use an existing one
5. Click on the Webhook, give it a name and icon
6. Click on Copy Webhook URL and paste it ingame via CTRL + V while editing the URL

Achievement Basics

• Achievements can come in many different forms
  • Hidden achievements
  • Single achievements
  • Stacking achievements with incremental difficulty (kill 5 players, kill 10 players, ...)
  • Achievements with multiple triggers
• In this guide I will go over all the different types and how to create them and when to use which. These types are not exclusive and can be combined, but it will make more sense when you fully read each description

Hidden Achievements

• Hidden achivements are not visible to the player until he unlocked it
• They are just a simple value enabled for an achievement "hidden": 1, but are basically normal achievements
• Description, Title and Image of the Achievement are hidden until unlocked
• They can be used to hide special achievements

Single Achievements

• Single achievements are created by setting the number in the config for the achievement to -1. So "number": -1
• These achievements automatically hide the progress bar and progress text
• This can be used for achievements like open your inventory, reach a certain location etc.

Stacking achievements

• Achievements are stacked when they use the same trigger. So to create an achievement with kill 5 players and 10 players together, you need to create 2 achievements, but change the number, title and description. The first trigger must be the same. You can also add a dummy trigger, which does not exist to artificially group achievements together (e.g. "dummy:fishing" as the first entry for all achievements you want to group together). Check the default config. It has a lot of these kinds of achievements
• Stacked Achievements will appear in one line in the achievements menu and should not exceed 10 achievements. Each stage can be accessed by the player by clicking on the box appeaing on the right in the achievements menu
• Very useful for achievements with progress and you don't just want a single achievement, but achievements should be harder to get each time
• Make sure to properly sort the achivements. Start with the achievement with the lowest number first in the config

Achievements with multiple triggers

• as you might have noticed, achievements take a list of triggers in the config and not just one trigger.
• All trigger values are accumulated and compared to the number set for the achievement
• This can be used to do things like "spawn at all 3 spawns possible", "eat all types of food available". For these achievements you would use the :once suffix for each trigger and set the number to the amount of triggers you have. There are also examples for this kind of achievements in the default config to check out

What are triggers?

• Triggers are basically numerical counters with a name. These counters are individual for each player and saved in their players achievement file.
• Achievements can have multiple triggers, which are accumulated to give a total value
• Each trigger has a trigger with the same name, but ending with ":once". This is recommended if the achievement is a one time achievement anyways to save performance. This trigger is either 0 or 1. This allows for various different options explained later. For example "kill:player" can be anything from 0 to infinity, but "kill:player:once" will only change to 1 and can never exceed this value

What is possible with triggers?

• Triggers can be executed when an action by the player is executed.
  • The simplest trigger is the action:CLASSNAME where the CLASSNAME is the classname of the Action. For example action:ActionOpenDoors
  • You can be a bit more specific with the triggers though. action:CLASSNAME:ruined-target would only execute when the target is ruined after the action finished. This can be used for detecting when a player chopped down a tree. action:ActionMineTree:ruined-target would be the trigger here
  • This is also possible with :ruined-hands. (They cannot be combined!). So action:ActionHackVehicle:ruined-hands would be triggered when someone breaks into a vehicle with a Lockpick and the Lockpick is ruined after the action
  • There are also 3 additional things you can do.
    • action:CLASSNAME:item:ITEMNAME checks for the itemname of the item in hands (be aware, that this doesn't support baseclasses)
    • action:CLASSNAME:hologram:ITEMNAME checks for the classname of the hologram for example for placing actions
    • action:CLASSNAME:target:ITEMNAME checks for the target itemname
    • action:CLASSNAME:target-obj:ITEMNAME checks for the object targeted and does not try to get the parent. The Harvest Action has a few exceptions. To check for an item being harvested, use this trigger like action:ActionHarvestCrops:target-obj:ITEMNAME. Itemname could for example be CP_Plant_CannabisSkunk from the CP mod
• There are also more triggers:
  • kill:zombie will count any direct zombie kill
  • bullet:shot will cound each time a weapon is shot by a player
  • distance:walk Distance a player traveled by foot on ground (counted in full km)
  • distance:drive Distance a player traveled in a ground vehicle or boat (couned in full km)
  • distance:boat Distance a player traveled by boat (counted in full km)
  • distance:fly Distance a player traveled in air (counted in km and only full km will count). A player is flying, when 20m above the air and he traveled a larger distance, so this might not be 100% accurate
  • kill:player Triggered for the killer of a player (this counts bots too). These must be direct kills with weapons (grenades or other indirect damage is not counted)
  • kill:player:no-bot Triggered for the killer of a player (this only counts real human controlled players). These must be direct kills with weapons (grenades or other indirect damage is not counted)
  • kill:player:bot Triggered for the killer of a bot player (not human controlled players)
  • kill:animal Counts Anything, that inherits AnimalBase (Everything except for zombies. This includes predatory Animals)
  • kill:animal:ITEMNAME Counts Animal kills matching the ITEMNAME exactly. This must inherit AnimalBase (Everything except for zombies. This includes predatory Animals)
  • kill:animal-hostile Counts all hostile animals like Wolves or Bears. Checks if IsDanger() for the Animal is true. Modded Animals might not properly support this
  • kill:animal-friendly Counts all hostile animals like Wolves or Bears. Checks if IsDanger() for the Animal is false. Modded Animals might not properly support this
  • kill:zombie Counts any zombie kill. This includes modded entities inheriting the ZombieBase class.
  • kill:zombie:ITEMNAME Counts zombie kills, which match exactly this itemname.
  • kill:zombie-silent Counts any stealth zombie kill. This includes modded entities inheriting the ZombieBase class.
  • kill:zombie-silent:ITEMNAME Counts stealth zombie kills, which match exactly this itemname.
  • looted:parent:ITEMNAME Counted when an item is looted from a container (this is only counted once per container. Once a player looted a container, it will not trigger again for the same or for other players to prevent farming this trigger). Can be used for things like looting Airdrops
  • looted:parent-classname:CLASSNAME same as above with the difference, that CLASSNAME might not exactly be the same like the ITEMNAME. If the item doesn't have a script class, the Classname will be the highest Classname found, which kind of works like a Baseclass.
  • looted:item:ITEMNAME Counted when an item is looted and was freshly spawned by the CE. Sadly this information is lost when the server restarts, so the item must spawn and be looted in the same restart, otherwise it's not counted
  • looted:item-classname:CLASSNAME Same as above, but with the Classname of the item instead of the itemname
  • inventory:open triggered once the player has opened his inventory (only triggered once, so the inventory:open:once trigger will behave the same)
  • crafting:CLASSNAME Triggered each time a Recipe is crafted. it needs the Classname of the recipe like crafting:CraftSalineBagIV Be aware, that some recipes are reversable, so players could abuse this
  • crafting:item:ITEMNAME Triggered for each of the spawned output items. This is independent of the Classname of the recipe. If multiple recipes produce the same item, this will count both. Be aware, that this does not work with base classes, so the itemname must match exactly
  • ag:group:created a player created a group with advanced groups
  • atm:robbed when a player robbed an ATM from Enhanced Banking
  • bank:transfer triggered when a player transfers money to another player. Only triggered for the player sending the money
  • bank:balance:personal Set Trigger saving the highest bank balance for the players personal account (only checked when withdrawing or depositing money)
  • bank:balance:group Set Trigger saving the highest bank balance for the players group account (only checked when withdrawing or depositing money)
  • spawnselect:spawn-bag Triggered when a player it spawning at his sleeping bag
  • spawnselect:spawn Triggered when a player spawns at a spawn point, which is not a sleeping bag or a house
  • spawnselect:spawn:POSITION_NAME Triggered when a player spawns at a spawn with a specific name from the config
  • spawnselect:spawn-house Triggered when a player spawns at his house (Only available with TB Real Estate)
  • player:killstreak Triggered when a player reached a killstreak. This is counted when the Killfeed mod by me is installed, which keeps track of killstreaks
  • fishing:junk Triggered when a player is fishing a junk item
  • fishing:junk:ITEMNAME Triggered when a player is fishing a junk item exactly matching the ITEMNAME
  • fishing:success Triggered when a player is fishing a fish or otherwise considered successful fishing attempt
  • fishing:success:ITEMNAME Triggered when a player is fishing a fish or otherwise considered successful fishing attempt of exactly the ITEMNAME item
  • fishing:ITEMNAME Triggered when a player is fishing this exact item (doesn't check if it is junk or not)
• Some Triggers require an extra pbo from the OptionalContent folder in the Client Zip you download from my website. Make sure to read the ReadMe.txt before installing any of the plugins!
  • quests:finished Triggered when any Quest from Expansion Quests is finished no matter which
  • quests:finished:ID ID is the ID of the quest. Only triggered when the quest with this ID is finished
  • trader:sold Triggered when an item is sold at a Trader (does not trigger multiple times when items are sold when attached!)
  • trader:sold:ITEMNAME Triggered when a specific item is sold with the ITEMNAME being replaced with the itemname
  • trader:bought Triggered when any item is bought (not triggered for attachments automatically spawned with the item)
  • trader:bought:ITEMNAME Triggered when a specific item is bought (not triggered for attachments)
• There are also some trigger handlers you can already use (note: trigger handlers always start with a $ infront of the trigger name):
  • $position:X,Y,Z,RADIUS Checks for the position of the player every second to match the specified position and radius. Example: $position:100.0,200.0,453.45,20.0 would check for the player being in a radius of 20m around 100.0,200.0,453.45. You can also use the :once suffix
  • $position2d:X,Z,RADIUS Same as the above, but ignores the Y axis when checking the distance
  • $kill:WEAPON:MIN_DIST:MAX_DIST:COUNT_HUMANS:COUNT_BOTS This one is a bit more complicated. It's a powerful trigger, which can check various differen things:
    • WEAPON is the classname of the weapon the killer must have in his hands. This supports Baseclasses unlike the other triggers. If you just leave it empty, any weapon will be accepted
    • MIN_DIST The minimum distance both players need to be away from eachother. This is a float value in meters. Leave it empty for no minimum distance
    • MAX_DIST Same as MIN_DIST, but kills further than this distance are not counted
    • COUNT_HUMANS either 0 or 1 to count human controlled players. Default if left empty is 1
    • COUNT_BOTS either 0 or 1 to count non human controlled players. Default if left empty is 1
    • Examples:
      • $kill::700::1:0 would trigger for each kill done on a human controlled player, who is further away than 700m. This could be used for an Achievement where someone has to snipe another player
      • $kill::5:50:1:0 would trigger for kills on human controlled players between 5m and 50m for example when you want to only count close Quarters kills
      • $kill:SVD:::1:1 would trigger for all Kills done with an SVD on any player

What is possible with extra scripting work?

• Since triggers are just strings, they are limited in their functionality
• Trigger via script:
  • Another thing you can do with some extra scripting is to add your own triggers. Check out the Modding Guide on how to trigger your own triggers
• TriggerHandler class
  • One thing to keep in mind is, that doing something like "pickup:Weapon_Base" as a trigger is not possible without a special "TriggerHandler" explained in detail later. The problem is, that the game would for example trigger a "pickup:M4A1", but since they are just simple strings, there is no information about the M4A1 also inheriting the Weapon_Base class. This trigger would not work. This is a case where a special TriggerHandler would be needed
  • Also positions are a difficult thing. For example you want to trigger an achievement when a player enters a room somewhere on the map. How do you tell the trigger, that the position with a specific radius should trigger it? "position:X,Y,Z,RADIUS" where each of them is replaced by a value like "position:1000,200,403.0,20.0" would be something that comes to your mind. But we run into the same problem as before. Triggers are just strings, so checking the position of each player and triggering a trigger based on the position will not work, because we cannot check for a specific Trigger. This is also a case for a TriggerHandler. This is acually implemented in the mod by default through the LBTriggerHandlerPosition class you can check out

What is not possible with triggers?

• There is not really much, that is not possible when you are able to do some scripting and create your own TriggerHandler, otherwise everything listed above is possible and with some clever combination of triggers and appending :once to a trigger, you can already achieve a lot

How to create a custom TriggerHandler

• First you need to be able to create a script and add the LBmaster_Achievements as a required addons in the config.cpp
• You can create a new Trigger in the 3_Game, 4_World or 5_Mission module. Make sure it inherits the LBTriggerHandler class.
• Check out my examples LBTriggerHandlerPosition and LBTriggerHandlerPosition2D in the LBmaster_Achievements/scripts/3_Game/LBmaster_Achievements/Struct folder and also check out the LBTriggerHandler class also found in the folder