imthenewguy

I found the issue. It is to do with "Maximum amount of pending xp a player can accumulate [0 = no limit]" being set to 0. There was an oversight and it restricts it to 0. I would set this to a large number for now, but its fixed in the next release.

It queues the xp up for offline players and gives it to them when they get online.

Changed Status from Pending to Closed Changed Fixed In to Next Version

I'll add a config option to the next release to disable it globally

That is a tricky one to work out as its a direct hook call exception (not a method). Does it happen after a server restart?

Changed Status from Pending to Closed

Its not possible to sell custom items via Rusts native vending system unfortunately. I am working on a custom solution at the moment.

Show me your config

Changed Status from Pending to Closed

You can add them to the relevant black lists "List of items to blacklist from the Component Luck buff" "List of items to blacklist from the Electronics Luck buff" Just add the item shortname in.

Set "Refund skill points on server wipe" to false

Changed Status from Pending to Closed Changed Fixed In to 1.0.2

It can be as high as you like.

Set the perkWeight attribute to a higher value. The higher the perkWeight, the more chance that those particular buffs are selected.

What needs patching besides the pooling?

Didnt see this one. The issue was patched on the 2nd of July though.

Can you record footage of you generating an item with the plugin and equipping it? Generate it with ipgive <name> pants Then put them on and open the menu. It works for everyone else, so it's either you have done something wrong or there is a plugin on your server that is conflicting with ItemPerks.

Have you given the permissions? itemperks.use

What are you wearing?

Changed Status from Pending to Closed Changed Fixed In to 1.1.18

If the plugin doesn't handle it in an additive manner, it won't be compatible with any other yield increasing plugins if its loaded before your loot manager plugin. There are 2 ways a plugin can handle it: a) The plugin SETS the multiplied value. For example if you would normally gather 25 wood, and the plugin is going to change it to 3x, it would set it to 75 wood. This is bad because any plugin that modified it's value is rendered completely useless, as its override entirely when the new plugin SETS the value. Example: SkillTree sees the default 25, works out the player has a 100% boost, and applies an additional 25 wood onto the stack, bringing us to a total of 50 wood. The loot manager then takes priority and SETS the item.amount to 75, nullifying what SkillTree did. b) The plugin ADDS the additional multiplied value. Rather than setting the item.amount to the new value, it simply calculates the difference between where it needs to be (75 - 25) and adds the difference (50). This means that any other plugin that may have handled the item.amount field before this plugin gets to it will still add their values on top of it. Example: SkillTree sees the default 25, works out the player has a 100% boost, and applies an additional 25 wood onto the stack, bringing us to a total of 50 wood. The loot manager then takes priority and ADDS 50 to the item.amount (75-25), bringing us to a total of 100 wood. This means that both plugins were able to add their values. Option b should be the way that any plugin handles the value, unless it fires off before the oxide hook (using Harmony).