-
Posts
2,100 -
Joined
-
Last visited
-
Days Won
17
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by ZEODE
-
Firstly, your initial post was just this: Which I think most people would agree is neither helpful or informative in any way. To just write a comment like that with no explanation or context was not helpful. What response would you expect after a comment like that? Secondly, hook time and "performance monitoring" is relative and dependant on many factors, not quite what you make it out to be. You say my plugins are and have But that plugin isn't saying the hook time is excessive, its just showing you the hook times in descending order. To simply assume then that my plugins have "huge issues with exessive time calling hooks" etc shows you don't really understand what is going on. Now to put it into context, there are many other plugins out there, particularly any with anything AI related or stat collecting that also have higher hook times. But just because hook times are longer for a plugin doesn't necessarily mean there is an issue, it just means they are doing more stuff. Unless you are seeing lots of "GARBAGE COLLECT" warnings in the console, which I know you aren't for my plugins, then it is not really indicative of a problem. To make a more informed assessment, I would need more information, which you didn't provide. For example, server hardware spec, how long was the server and/or those plugins running to accumulate that hook time. Around 40 seconds actually isn't that much, depending on circumstances. Now, back to my initial reply of people not reporting such hook times, they aren't. Many people use these without issues. We also use both these plugins on our servers, each server is restarted daily and after 24 hours of running on a fairly busy PVE server with many people who love taking helis, the hook times are rarely above 30 seconds over 24 hours for Heli Signals and Bradley Drops (this is on a highly modified, 170+ plugins PvE server. Much, much higher hook times are on Raidable Bases, SkillTree, and a host of other event plugins that we run. My initial reply may have been a bit abrupt and thoughtless, but then so was your initial comment, and it is sometimes frustrating to read comments like yours from people who don't have a clue of what's gone into the writing of the plugin, how it works, or how it performs and why. But I can assure you my plugins and my code in general is written to be as efficient as I can make it. But for some reason a couple of people get longer hook times than others using the same plugin, in the same way. Now this could be due to a number of reasons, one might be another plugin making calls to my plugin. For example AlphaLoot calling to my plugin to see if it can populate heli_crates, bradley_crates, etc. Or any other plugin checking to see if a supply drop belongs to their plugin or mine, etc etc. Excessive calls to my plugin will add hook time. I can see why a lack of understanding might lead you to draw conclusions that my plugins are "the culprit" when trying to troubleshoot performance, but without understanding all the various factors you should be cautious of pointing fingers, instead maybe approach it in a different way and we could have troubleshooted the issue to see if we could find any reasons why you are having these issues where others are not. However, as I mentioned before, those hook times aren't horrendous, but then, I don't know how long the plugins had been running to get those amounts. Lastly, a couple of updates ago I had already given the plugin a overhaul and code clean up, which I do frequently as my coding improves. The only other person who has reported an issue with hook times reports hook times to have halved (after troubleshooting together on Discord). But again, these hook times are not the norm, so could indicate another issue with your server or some sort of conflict. Edit: After reading your past comments on other devs plugins, I can see your attitude is no different to what it was here. Speaks volumes. -
Thanks for the detailed report. This is the wrong place for support issues, please open a support thread in the proper place and I will gladly help you. Then I can keep proper track of progress and keep the discussion pages clear of support, thanks.
- 424 comments
-
- 1
-
-
- #helicopter
- #helicopters
- (and 17 more)
-
The issue is not with my plugin. According to the rules of writing code on Oxide, the hook CanCombineDroppedItem should return either null or true, because this hook returns values object. Hooks which return bool values can return either null, true or false. So the author of the other plugin is incorrect in this case.- 301 comments
-
- 1
-
-
- #bradley
- #bradleyapc
- (and 14 more)
-
Both issues fixed. Update to latest version
-
Version 1.1.6
862 downloads
Horse lock is a simple plugin that locks horses to players for a certain amount of time as set in the configuration. Once a rider dismounts, they have a set time to mount again before the horse is unlocked to use by anyone. If an unauthorised player attempts to mount the horse before that time they will be denied. However, If a horse is kept within a players building privilege, that horse will remain protected from unauthorised use indefinitely (or until building privilege is gone). Other config options allow friends, team and clan members to ride players horses and the horse can be configured to rear up if an unauthorised player attempts to mount a protected horse (just for fun). This is a great plugin for PVE servers, but equally it can come in useful on PVP servers too. No permissions and very few config options to worry about, so it couldn't be easier to set up. Default Config: { "Options": { "Use Chat Prefix": true, "Chat Prefix": "[Horse Lock]: ", "Use Friends Plugin (Friends Can Mount)": false, "Use Clans Plugin (Clan Can Mount)": false, "Use Teams (Team Can Mount)": false, "Custom Chat Icon (Default = 0)": 0, "Time Horse Locked After Dismount (Seconds)": 900.0, "Minimum Time Between Dismount Unlock Warnings (Seconds)": 120.0, "Make Horse Rear When Unauthorised Player Attempts to Mount": true, "Horses Within Building Privilege Do Not Lose Health": false }, "Plugin Version": { "Major": 1, "Minor": 1, "Patch": 6 } }Free -
Please open a support thread
-
Thanks for the report, will definitely look into this. I will have to write a check that makes sure they can’t call at monuments.
- 301 comments
-
- 1
-
-
- #bradley
- #bradleyapc
- (and 14 more)
-
Many users of both plugins without any lag issues. Why automatically assume it’s these plugins causing the issue? If there is an issue you could open a support thread and we can investigate any potential for a conflict which might be causing your issue. I can assure you if these plugins were the cause of lag there would be many people reporting it, but it’s just you.
-
Hi, the heli has been acting weird and going under water since a couple of Rust updates ago. It has been doing it even on Vanilla official servers. This is not controlled by my plugin so I cannot do anything about it. There was also a bug which made it hover stationary just above the water, but that is supposed to be patched by Facepunch now. But to begin with you can set the height at which the helicopter will arrive at the target, but after that it uses default Rust behaviour. "Height of heli when it arrives at called location": 20.0,
-
Probability is per item, not combined. The way it works on my plugin is this: 1. An item is chosen from your list of loot items, depending on the rarity. (More rare = less chance). 2. The item then has a chance of being caught or not, determined by the drop chance. 3. If the item is selected to be caught, the bait level of on the rod or trap is then checked, if requirements are met the item is caught, if not, the item is not. 4. Lastly, if all stages are met and item is to be caught, it is either given or the blueprint is, depending on the BP chance. -
Oh, you don’t. I could maybe add it on a future update though.
-
Huh?
-
My instructions are correct for the command (I wrote the plugin, I know this ). It tells people the format to use in their command, i.e: hsgive "profile name" "Steam64ID" "amount" That is correct, but when using in a plugin then yes, you will need to follow the Shop plugins instructions for issuing commands, {steamid} is just a placeholder used by your shop plugin for the Steam64ID of the player using the shop and making a purchase. Anyhow, I still recommend you add the items to the shop instead of using the command.
-
Did you make it work in the end? I have been offline for a few days so haven't been able to reply. You aren't following the instructions on the Shop UI documentation to add the items correctly We use the Shop UI plugin, and I see you were confused on how to set it up in the config and data file for the Shop plugin. You said you wanted to use the command, but the config/data part you posted was for giving the item, not issuing the command. For selling items in a shop, I always recommend specifying the item, NOT using the console command. To set up items in Shop UI, you have to first specify the items in the items.json file in the data directory. It should look something like this for the default Heli profiles: "supply.signal{1}": { "DisplayName": "Heli Signal (Regular)", "Skin": 2920175997, "Image": "https://path-to-image/easyHeli.png", "DefaultAmount": 1, "BlockAmountChange": false, "BuyPrice": 2000, "SellPrice": 0, "Currency": "rp", "ShowDisplayName": true }, "supply.signal{2}": { "DisplayName": "Heli Signal (Medium)", "Skin": 2920176079, "Image": "https://path-to-image/medHeli.png", "DefaultAmount": 1, "BlockAmountChange": false, "BuyPrice": 3000, "SellPrice": 0, "Currency": "rp", "ShowDisplayName": true }, "supply.signal{3}": { "DisplayName": "Heli Signal (Hard)", "Skin": 2920176050, "Image": "https://path-to-image/hardHeli.png", "DefaultAmount": 1, "BlockAmountChange": false, "BuyPrice": 3500, "SellPrice": 0, "Currency": "rp", "ShowDisplayName": true }, "supply.signal{4}": { "DisplayName": "Heli Signal (Elite)", "Skin": 2920176024, "Image": "https://path-to-image/eliteHeli.png", "DefaultAmount": 1, "BlockAmountChange": false, "BuyPrice": 3500, "SellPrice": 0, "Currency": "rp", "ShowDisplayName": true }, Notice how each item has to have a unique name. So because you kept using the same item shortname ("supply.signal") it was breaking the shop plugin and only giving vanilla supply signals. You have to number them in curly brackets as above, like supply.signal{1}, supply.signal{2} etc. Then in the categories.json file you need to add the Heli Signals, here is an example of the heli signals items to be sold in their own category: "Heli_Signals": { "Image": "https://i.imgur.com/w2cI90o.png", "Permission": null, "Sale": 0, "Items": [ "supply.signal{1}", "supply.signal{2}", "supply.signal{3}", "supply.signal{4}" ] }, Again, I recommend using the above method, issuing the items, rather than using the console command.
-
Just set the distance spawned from player in the config to 0.0
-
I'll have a look at this later, it works fine for me and others, so I don't know why some have issues. -
Hey, reach out to me on Discord and we will work this out, I have a version you can test to make sure its fixed for you.
-
If you edit the existing language file to your chosen language it will work, its not possible that it wont
-
Yes the crfates that spawn are standard heli crates. Unless you specify a loot table in the config, then the default heli loot will spawn in the crates, or whatever you specify in any loot plugin you are using. If you want the vanilla heli event crates to be controlled by your loot plugin, you should be able to have custom loot using the loot table in my plugin, it should play nice with almost all loot plugins.
- 424 comments
-
- 1
-
-
- #helicopter
- #helicopters
- (and 17 more)
-
Just edit the file that's exists already with your language?
-
Well, I don’t know how that should work then. I never mess with languages. I think plugins which support that have it hard coded in the plugin. I am not providing that. Most other people just edit the existing language files to their own language. How do you make it work with other plugins? What plugins do you make it work with other languages?
-
I have added this option in the config on the next update which will drop tonight or tomorrow.
-
Done, on latest update. -
Thanks for the report, if you get a minute, please open a support thread with this issue so I can keep track of it and update you when it is fixed. Thanks.
