Gd.Kenni
-
Posts
45 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Gd.Kenni
-
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
-
Changed Status from Pending to Closed
-
It's find ?
-
Hello, yes, it's the version of Carbon Aliases that isn't up to date. I specified this in the patch note, but I forgot to add it to the main page. While waiting for the official version to be released, I've compiled the public version (up to date) for you. Oxide.Ext.CarbonAliases.zip
-
Changed Status from Pending to Not a Bug
-
Indeed, if this is your first installation, it can't be due to the plugin, as the data is created directly from the plugin. A very strange error if it breaks the configuration of another plugin.
-
Is this the first time you've run the plugin ? Was the configuration already created ?
-
Have you managed to create a configuration for yourself ? -
The node name is its ID. You don't have to call it A1, you can use anything like the item name as the ID. This is your own logic. If you want to start a tree, you don't specify a parent, otherwise you specify a parent (ID).
-
Changed Status from Pending to Not a Bug
