imthenewguy
-
Posts
4,936 -
Joined
-
Last visited
-
Days Won
65
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by imthenewguy
-
Not really. The only adjustment is for scavenger drops, where you can set the min and max values. -
To gather them?
-
Failed to call hook 'OnEntityTakeDamage'
imthenewguy replied to ChristopherS's Support Report in Support
Is this appearing often? -
Not sure if any of that is possible with the current build. Didn't have preventing admin powers in mind when I built any of the plugins. It could be worked around, but it wouldn't be something that would suit the plugin or its dependencies, so it would be a custom job.
-
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; }
- 1,617 comments
-
- 1
-
-
- #leveling
- #progression
- (and 19 more)
-
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 },
- 1,617 comments
-
- 1
-
-
- #leveling
- #progression
- (and 19 more)
-
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.
-
Glad to hear it!
-
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- 150 comments
-
- 1
-
-
- #admin
- #admintool
- (and 31 more)
-
Changed Status from Pending to Closed
-
Custom Perm Skills error when assigning skill tree perms
imthenewguy replied to Zoreeno's Support Report in Support
Changed Status from Pending to Closed -
Custom Perm Skills error when assigning skill tree perms
imthenewguy replied to Zoreeno's Support Report in Support
Yeah I had a look at the code. It is not going to work for a number of reasons based on how player data is handled and perms are assigned/unassigned for that particular permission set (skilltree.<tree perm>) -
Custom Perm Skills error when assigning skill tree perms
imthenewguy replied to Zoreeno's Support Report in Support
Hmm that is odd. Paste me the section of the config responsible for it. -
You have put set bonuses for "2" items before "1". Change this around and it should work fine. The plugin assess the config 1 bonus at a time to see if the amount of pieces worn are equal to or greater than the set bonus entry and if so, moves on to the next. If you are wearing 2 pieces, this is how the logic would work with your current setup. Confirmed 2 pieces equipped. Check config for a match and enter into a foreach loop, where the key is the set pieces required. We start by assessing "2" and confirm that our current set amount is greater or equal to "2" pieces. We set our highest value as "2".. We move onto the next entry, which is "1", and we are greater than or equal to that as well, so we set our highest value as "1". We check the entry after that, but the entry is larger than "2" so we ignore it and confirm that "1" is our highest set number. I will add some logic to change it so it doesn't register a smaller number, but in the mean time change the entries to be ascending order and it will fix the issue.
-
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- 289 comments
-
- 1
-
-
- #enhanced
- #custom loot
- (and 7 more)
-
Pm'd the solution. -
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.
-
Custom Skills (perms) not cleared on stresetskills command
imthenewguy replied to Zoreeno's Support Report in Support
Changed Status from Pending to Closed -
Changed Status from Pending to No Response
-
Changed Status from Pending to Closed Changed Fixed In to 1.0.12
-
Changed Status from Pending to No Response
-
Changed Status from Pending to Closed
-
Changed Status from Pending to No Response
-
Love the plugin, but reworking the config is awful
imthenewguy replied to Rust Admin's Support Report in Support
Changed Status from Pending to Closed -
Changed Status from Pending to Closed