All Activity

Hello again, im sorry, what custom map it was?

Home: https://rustplugins.net/products/welcomepanellite/2/home_button.png Rules: https://rustplugins.net/products/welcomepanellite/2/rules_button.png Wipe Cycle: https://rustplugins.net/products/welcomepanellite/2/wipe_button.png Links: https://rustplugins.net/products/welcomepanellite/2/steam_button.png Kits: https://rustplugins.net/products/welcomepanellite/2/kits_button.png Shop: https://rustplugins.net/products/welcomepanellite/2/shop_button.png Vip Ranks: https://rustplugins.net/products/welcomepanellite/2/vip_button.png Rewards: https://rustplugins.net/products/welcomepanellite/2/reward_button.png Commands: https://rustplugins.net/products/welcomepanellite/2/rules_button.png Wipe Cycle: https://rustplugins.net/products/welcomepanellite/1/richtext.png Links: https://rustplugins.net/products/welcomepanellite/1/enableaddons.png Shop: https://rustplugins.net/products/welcomepanellite/1/multiplepages.png https://rustplugins.net/products/welcomepanellite/2/rustlogo.png All of these images that the plugin depends on to work properlly are now not available. The documentary, the web app to edit config files even the discord are down too so now because of WelcomePanel is broken, the ShopUI goes down with it.

thx

thank you

HOW THE GLOBAL PERMISSION SYSTEM WORKS Important: Branch permissions are a separate system. Use Permissions ? has no effect on branch permissions. Branch permissions are explained in the dedicated branch permissions tutorial. WHAT "USE PERMISSIONS ?" DOES The config option "Use Permissions ?" enables or disables TechTree's global permission checks. It affects: techtree.use techtree.unlock.free techtree.unlock.instant It does not affect branch permissions. WHEN "USE PERMISSIONS ?" IS FALSE Players can open the TechTree without techtree.use. techtree.unlock.free does not apply. techtree.unlock.instant does not apply. This is the simplest setup. Use it if every player should be able to use the TechTree normally. WHEN "USE PERMISSIONS ?" IS TRUE Players need techtree.use to open the TechTree. Players with techtree.unlock.free can unlock nodes for free. Players with techtree.unlock.instant skip the unlock timer. Use this setup if you want to restrict access to the TechTree or give special unlock benefits to specific groups. GLOBAL PERMISSIONS -- techtree.use Allows the player to open/use the TechTree when "Use Permissions ?" is enabled. -- techtree.unlock.free Allows the player to unlock nodes for free when "Use Permissions ?" is enabled. -- techtree.unlock.instant Allows the player to unlock nodes instantly when "Use Permissions ?" is enabled. RECOMMENDED CONFIGS Public TechTree, no special permission bonuses: "Use Permissions ?": false Public TechTree with VIP free/instant unlock bonuses: "Use Permissions ?": true Then grant techtree.use to everyone. Grant techtree.unlock.free or techtree.unlock.instant only to VIP groups. Restricted TechTree: "Use Permissions ?": true Grant techtree.use only to the groups allowed to open the TechTree. COMMON MISTAKES Mistake: Enabling "Use Permissions ?" but forgetting to grant techtree.use. Result: Players cannot open the TechTree. Fix: Grant techtree.use to the default group or to the groups allowed to use the TechTree. Mistake: Expecting techtree.unlock.free or techtree.unlock.instant to work while "Use Permissions ?" is false. Result: Those special permissions do not apply. Fix: Enable "Use Permissions ?" in the config. IMPORTANT NOTE ABOUT BRANCH PERMISSIONS Branch permissions are not controlled by "Use Permissions ?". Even if "Use Permissions ?" is false, branch permissions still work independently. Do not configure branch permissions here. Use the dedicated "How Branch Permissions Work" tutorial for branch restrictions.

Any ideas???

Set it to 0, players can use /ztop to execute it themselves to see the standings.

HOW TO USE REWARDS Rewards are actions executed when a player unlocks a node. You can add multiple rewards to the same node. REWARD TYPES TechTree supports three reward types: ChatCommand ConsoleCommand Economics CONSOLECOMMAND VS CHATCOMMAND ConsoleCommand: Runs a server command from the server console. Use ConsoleCommand for admin/server commands such as granting permissions, giving items, running plugin commands, or executing Rust server commands. Example: ChatCommand: Runs a command from the player's client. Use ChatCommand only when you need the player to execute a client/chat-style command. Example: IMPORTANT Most reward actions should use ConsoleCommand. If a command needs admin/server authority, use ConsoleCommand. If a command is supposed to be executed by the player, use ChatCommand. PLAYER ID PLACEHOLDER Use playerID when the command needs the unlocking player's Steam ID. TechTree replaces playerID automatically. Example: If the player ID is 76561198000000000, TechTree will run: ECONOMICS REWARD Economics deposits money into the player's Economics balance. Example value: This requires the Economics plugin to be installed and available. RECOMMENDED WORKFLOW Open the TechTree. Switch to Edit Mode. Select the node. Click Modify. Open the Economy/Rewards tab. Add a reward. Select the reward type. Enter the command or value. Confirm. Save the editor session. GOOD EXAMPLES Grant a permission: Give an item: Deposit Economics money: Send a player/client command: COMMON MISTAKE Mistake: Using ChatCommand for a server/admin command. Result: The command may fail because it is executed as the player instead of the server. Fix: Use ConsoleCommand for server-side actions.

HOW BRANCH PERMISSIONS WORK Branch permissions allow you to lock a node, or an entire branch, behind a custom permission. IMPORTANT Branch permissions are not automatically created by TechTree. You type the permission name in the node editor, then you must grant that permission with your permission manager. Do not confuse branch permissions with the global TechTree permissions. Global permissions such as techtree.use, techtree.unlock.free, and techtree.unlock.instant depend on the `Use Permissions ?` config option. HOW IT WORKS If you set a permission on a node, players need that permission to unlock that node. Child nodes can inherit the nearest permission from their parent branch. This means you can lock a full branch by placing the permission on the first/root node of that branch. EXAMPLE You create a custom branch for VIP weapons. On the first node of the branch, set: Players without vip.weapons will see the branch as locked. Players with vip.weapons can progress through that branch normally. RECOMMENDED WORKFLOW Open the TechTree. Switch to Edit Mode. Select the node that should start the restricted branch. Click Modify. In the Permission field, enter your custom permission. Confirm. Save the editor session. Grant the permission to the correct players or groups. PERMISSION PLACEMENT Permission on a root node: Locks the whole branch. Permission on a child node: Locks that node and the child branch after it. No permission: The node is public, unless it inherits a permission from a parent branch. GOOD EXAMPLES COMMON MISTAKE Mistake: Typing a permission in the node editor but never granting it to players. Result: The branch stays locked for everyone. Fix: Grant the permission to a player or group with your permissions plugin.

Thanks, I've already resolved it.

That’s not in config you can comment it out if you really need to right now

Thankyou . i also notice another issue where if i upgrade from say stone with a skin appiled the symmetrical walls turn into twig

Do I have to install it directly into the server folder for it to show up in English?

and the sound?

I installed it from Carbon within the game.

IMPORTANT RULE "Exclude from vanilla sync" must be used together with "Disable Future Vanilla Imports". If "Disable Future Vanilla Imports" is not enabled, the vanilla synchronization system can still import vanilla nodes again later. So the safe workflow is: Disable Future Vanilla Imports -> Exclude the node -> Remove the node -> Save WHY THIS IS IMPORTANT TechTree creates its default trees from Rust's vanilla workbench tech trees. This allows the plugin to detect vanilla nodes and recover or synchronize them when needed. Because of this, deleting a vanilla node is not always enough. If the tree is still allowed to import future vanilla nodes, removed vanilla content can be synchronized again. To make a custom tree stable, you must first disable future vanilla imports for that workbench tree. DELETE VS EXCLUDE Delete: Removes the node from the visible tree layout. Exclude: Marks the vanilla node as intentionally removed from vanilla synchronization. Disable Future Vanilla Imports: Freezes the current workbench tree so future vanilla imports do not modify it automatically. For a permanent vanilla node removal, use all three: Disable Future Vanilla Imports Exclude from vanilla sync Remove the node STEP-BY-STEP: REMOVE ONE VANILLA NODE PERMANENTLY Open the TechTree at the correct workbench. Switch to Edit Mode. Open the Excluded Nodes menu. Enable "Disable Future Vanilla Imports". This step is required if you want excluded/removed vanilla nodes to stay removed. Close the Excluded Nodes menu. Select the vanilla node you want to remove. Vanilla nodes are the nodes created from Facepunch's default tech tree. Click Modify. Enable "Exclude from vanilla sync". This marks the vanilla node as intentionally removed. Confirm the node edit modal. Select the same node again. Click Remove. This removes the node from the visible tree. Press Save in the top bar. This is required. The editor works in a draft session, so your changes are only written to the data files when you press Save. COMMON MISTAKE Mistake: Only removing the vanilla node. Result: The node can come back later through vanilla synchronization. Correct fix: Recover or restore the node, enable Disable Future Vanilla Imports, enable Exclude from vanilla sync on the node, remove it again, then Save. EXCLUDE ALL Use Exclude All when you want to remove many vanilla nodes or rebuild a workbench tree from scratch. Recommended workflow: Open Edit Mode. Open Excluded Nodes. Enable Disable Future Vanilla Imports. Click Exclude All. Remove the vanilla nodes you do not want. Add or move your custom nodes. Press Save. This is the safest workflow for a fully custom tree. DISABLE FUTURE VANILLA IMPORTS Use this option when you want the current workbench tree to stop receiving automatic vanilla additions. Enable it for: Fully custom trees. Progression trees where vanilla nodes were intentionally removed. Seasonal or staged progression. Servers that do not want Facepunch tech tree updates to change their custom layout. If this option is disabled, TechTree may still synchronize vanilla nodes again later. AUTO VANILLA SYNCHRONIZATION Auto vanilla synchronization is useful when you want to keep a tree close to vanilla. It is not the safest mode for a custom tree where vanilla nodes were intentionally removed. If you want to permanently remove vanilla nodes, use Disable Future Vanilla Imports. RECOVER VANILLA NODES Use Recover Vanilla Nodes when you want to bring back missing vanilla nodes. If a node is excluded, restore it from the Excluded Nodes menu first. Then use Recover Vanilla Nodes. Then Save. BEST PRACTICE SCENARIOS Scenario 1: Remove one vanilla node permanently Enable Disable Future Vanilla Imports. Modify the vanilla node. Enable Exclude from vanilla sync. Confirm. Remove the node. Save. Scenario 2: Remove several vanilla nodes Enable Disable Future Vanilla Imports. For each vanilla node, enable Exclude from vanilla sync. Remove the nodes. Save. Scenario 3: Build a fully custom tree Enable Disable Future Vanilla Imports. Click Exclude All. Remove the vanilla nodes. Build the custom tree. Save. Scenario 4: Keep the tree updated with Facepunch additions If you want to keep future vanilla imports enabled, avoid removing vanilla nodes permanently. Future synchronization is designed to keep the vanilla tree updated, while Disable Future Vanilla Imports is designed to freeze a custom tree.

Changed Status from Pending to Work in Progress Changed Fixed In to Next Version

just like for all console commands where a parameter is a string and has a space in it, you need to put quotes around it so it registers as 1 parameter. if theres no space in the string, you dont need the quotes. the following will work givedrugseed 76561198968114028 "Weed Seeds" 10 givedrug 76561198968114028 "Weed Leaf" 10

I have tried all the variations. givedrugseed 76561198968114028 Weed Seeds 10 givedrug 76561198968114028 Weed Leaf 10

can you paste the exact command you are using thats not working?