imthenewguy
-
Posts
3,697 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by imthenewguy
-
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 â¤ï¸- 144 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 Request in Support
Changed Status from Pending to Closed -
Custom Perm Skills error when assigning skill tree perms
imthenewguy replied to Zoreeno's Support Request 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 Request 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 🙂- 249 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 Request 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 Request in Support
Changed Status from Pending to Closed -
Changed Status from Pending to Closed
-
Have a solution being tested on a server. Should see this in the next release.
-
Changed Status from Pending to Closed Changed Fixed In to 1.4.1
-
Patched in 1.4.1
-
Known bug and has been patched in the next release.
-
Ive built something. Will test it and wack it up.
- 1,299 comments
-
- 3
-
-
-
- #leveling
- #progression
- (and 19 more)
-
If I made it, it would use items with interactive buttons such as presents. Ill have a tinker and let you know though.
-
Feels like it would be a separate plugin for something like that.