Jump to content

imthenewguy

Curator
  • Posts

    4,621
  • Joined

  • Last visited

  • Days Won

    57

Everything posted by imthenewguy

  1. I won't be adding flat yield multipliers that arent skill related to the plugin as there are plenty out there that can add that functionality. Skill nodes aren't perm based. There isn't a way to prevent players from accessing the node if it is enabled on the tree, and they have access to the tree.
  2. Try using the internal give command for SkillTree: stgiveitem {id} <shortname> <quantity> <skinID> <displayName> Example: stgiveitem {id} chicken.cooked 1 2860127847 Homemade Moonshine
  3. The only thing you could do is assign a permission on unlock by adding it to the skill in the config. There are some examples in discussions of how to accomplish this, or you can use the /addtestpermsnode command while in game to have an example perm added to the cooking tree. If the command isnt related to permissions, you will need someone to build you a plugin to achieve this. You can remove perks or simply disable them by setting "enabled" to false, or you can change them to be a different perk all together, OR use permissions.
  4. imthenewguy

    Cooking

    Added to the next release.
  5. Unfortunately this isn't a plugin I would add a leveling system to and the way the weighted drop chances work would prove difficult to manipulate
  6. It tells you in the chat box when you unlock it, or toggle it off/on via the Ultimate Settings in your Skill Tree menu. You use the chat command.
  7. Not really. The only adjustment is for scavenger drops, where you can set the min and max values.
  8. This should explain how the logic works. Although I realize a mistake I made is that the modifier is set to 1.0 by default, so I need to adjust it so it takes into consideration lower modifiers than 1. So your 0.001 modifier won't work at the moment. Will patch this next release. double GetXPModifier(string id, PlayerInfo pi, out bool modified) { modified = false; double result = 1; // Checks each permission that you have created in the config for xp override. foreach (var perm in config.xp_settings.xp_perm_modifier) { // If the permissions value is greater than the value stored in result, result is set to the new value. if (permission.UserHasPermission(id, "skilltree." + perm.Key) && perm.Value > result) result = perm.Value; } if (config.rested_xp_settings.rested_xp_enabled && pi.xp_bonus_pool > 0) { // If rested XP is enabled, then we add the rested xp value on top of our result. result += config.rested_xp_settings.rested_xp_rate; modified = true; } if (TOD_Sky.Instance.IsNight && config.xp_settings.night_settings.night_xp_gain_modifier != 1) { // If night time xp gains are enabled, we add (or remove) that value onto our result as well. result += config.xp_settings.night_settings.night_xp_gain_modifier - 1; modified = true; } return result; }
  9. Unfortunately not as the plugin stands. I may look at an option for it down the line, but in the mean time you could easily replace the buffs with PVE related ones. "Thick Skin": { "enabled": true, "max_level": 5, "tier": 3, "value_per_buff": 0.10, "buff_info": { "Key": 25, "Value": 1 }, "icon_url": "https://imgur.com/wG7cG8X.png", "permissions": null }, "Assassin": { "enabled": true, "max_level": 5, "tier": 3, "value_per_buff": 0.05, "buff_info": { "Key": 59, "Value": 1 }, "icon_url": "https://imgur.com/xMp1fhd.png", "permissions": null }, "Guarded": { "enabled": true, "max_level": 5, "tier": 3, "value_per_buff": 0.05, "buff_info": { "Key": 61, "Value": 1 }, "icon_url": "https://imgur.com/cVhnv41.png", "permissions": null },
  10. Here is an example of how it works: "permissions": { "description": "Cooking food with the Cooking plugin will be instant and you may get admin.", "perms": { "1": { "perms_list": { "cooking.instant": "Instant Cook", "cooking.use": "Cooking access" } }, "2": { "perms_list": { "cooking.instant": "Instant Cook", "cooking.use": "Cooking access", "cooking.admin": "Cooking admin" } } } } You can add permissions to node unlocks, so that when the player unlocks the node, they will get access to a permission. If you have multiple levels that you would like to grant perms, make sure you add the perms to both levels that you would like the player to keep, as it unassigns perms from previous levels.
  11. imthenewguy

    Admin Toggle

    Hey mate a customer of mine mentioned a conflict between your plugin and EpicLoot. Apparently when switching inventories, the items from EpicLoot are being returned as vanilla items, and they lose their name. If you are destroying the items and serializing them, it should be a simple matter of storing the item.name, and then restoring it when creating the items again. If you need any help feel free to download EventHelper for some inspiration or send me a pm
  12. I added permission requirements for it. Forgot to update the main page but they were in the patch notes. Have updated the permission section with the relevant perm
  13. imthenewguy

    Cooking

    I have a feeling youn are updating from a version older than 1.4.0. 1.4.0 required a config deletion. Delete your config, reload the plugin and it should work fine.
  14. If I made it, it would use items with interactive buttons such as presents. Ill have a tinker and let you know though.
  15. imthenewguy

    Admin Toggle

    If you were wanting to fulfill Zeds request, you can use the existing API from SkillTree to prevent xp gain. object STCanGainXP(BasePlayer player, BaseEntity source) Return a non-null value to prevent xp gain.
  16. The latest version no longer uses the loot table that you add via RustEdit. The crates etc are all spawned/populated by the plugin now and include 2 loot profiles in the config.
2.3m

Downloads

Total number of downloads.

10.6k

Customers

Total customers served.

152.7k

Files Sold

Total number of files sold.

3.3m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.