Gd.Kenni
-
Posts
55 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Gd.Kenni
-
Changed Status from Pending to Closed Changed Fixed In to 2.1.5
-
Permissions will only work if you have enabled the option in the configuration file { "Settings": { "Wipe Player Data at Wipe": true, "Time For Unlock Node": 1.0, "Selected Theme": "Default", "Use Permissions ?": false, "Use Economics ?": false, "Replace tree vanilla ? Open with [R] if false": true } } I just tested it on a fresh install, and the plugin loads correctly in Oxide. The data and config files are created correctly. You must be having an issue on your end. CarbonAliases must be placed in the RustDedicated_Data\Managed folder since it is an extension If the plugin has errors, you'll see logs. Also, keep in mind that Oxide has released a new compiler, and not all logs are necessarily displayed in the console.
-
What do you mean ?
-
Sets the value to false, so the bool detects the wipe, it doesn't care if it's a map wipe or a global wipe, if there's a wipe, it clears the bp or not And you delete the data players manually -
About permissions, I thought about adding a condition for the primary node: if a permission is specified for it, only those who have that permission will be able to unlock that branch. This will avoid having to specify the same permission for each node. I'm not sure how to implement a battle pass system. Are you thinking of a subcategory system? Being able to create subcategories for each workbench? Because if you disable the auto-replacement of the vanilla tech tree in the configuration, players have access to the Facepunch tree, and mine is still accessible so they can build a custom one -
Hi, compatibility with CraftMenu is in terms of user interface. Both of our plugins use the same system to display our user interfaces, and previously, they couldn't work together. In terms of interaction, CMenu does not have any API, so I cannot interact with it, but it can interact with mine if it wants to display BP's only if they are unlocked, for example. No, currently it is not possible to privatize nodes for certain permissions only. I hadn't thought of that, I'll implement it. I am open to any suggestions or improvements
-
Ah, indeed, I hadn't noticed that the latest version of CraftMenu no longer uses the container. I'll see if I can adapt to that
-
Normally, there is no blocking since CraftMenu uses a container to open its UI. My UI opens directly from the workbench. The two UIs cannot conflict with each other
-
If I understand your request correctly, yes, I added the “techtree.unlock.path” permission, which allows you to directly unlock the entire branch up to the node you want to unlock, but only if you have the resources
-
The plugin is not designed to recreate the Rust techtree; you can assign chat commands, console commands and economic rewards, but this requires the reward to be unlocked on the plugin's techtree. If you want a special feature, I can try to integrate it but I need to know exactly what behavior to ask for. Does this answer your question?
