-
Posts
2,532 -
Joined
-
Last visited
-
Days Won
10
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Reels
Everything posted by IIIaKa
-
@Razor Hello, I want to add compatibility with your plugin. However, I encountered the absence of an API and hooks. You only have two hooks: OnRandomRaidStart(string waveType, Vector3 pos) and RandomRaidEventEnd(Vector3 pos). Additionally, there is no information about NPCs, helis, or airdrops. I kindly ask you to add the following hooks for better convenience for plugins that will be compatible with your plugin: Interface.Oxide.CallHook("OnRandomRaidRaiderSpawned", location, theNewGuy, true);//line ~1406, true means npc is juggernaut Interface.Oxide.CallHook("OnRandomRaidRaiderSpawned", location, theNewGuy, false);//line ~1474 Interface.Oxide.CallHook("OnRandomRaidHeliSpawned", location, heli);//line ~4522 It would also be super convenient if you assigned skinID for your NPCs, helis, and airdrops, similar to how nivex does it in Raidable Bases using skinID = 14922524. theNewGuy.skinID = 123; heli.skinID = 123; Also, please add the hook OnRandomRaidOwnersUpdated, which will be called when the list of authorized users changes (OnCupboardAuthorize, OnCupboardDeauthorize, OnCupboardClearList), passing the parameter BuildingPrivlidge or HashSet<PlayerNameID>. Thank you in advance for your cooperation.
-
Hello, it would be great if the "Manage Purchases" section under "Plugins" only displayed the purchased plugins. And for the list of "Featured My File" had its own subsection.
-
Welcome to the ExtendedStats Plugin Discussion Section! Hello! This section is exclusively for discussing ExtendedStats plugin. Encountered Issues? If you're facing any difficulties with the plugin's functionality, feel free to create a topic in the Support section for assistance! Ideas and Suggestions? Have ideas to share or new features to suggest? Feel free to start a discussion by creating a topic in the Support section. Feel free to share your thoughts and experiences - together we can make our plugin even better!
- 6 comments
-
- #rust
- #reputation
- (and 26 more)
-
Hello. I noticed that not all Featured plugins are pinned. Currently, there's a limit of 15. I suggest that the remaining Featured plugins, which don't fit, be displayed every 5(for example) items. This way, the money spent on purchasing the Featured status will not be wasted for those whose plugins did not fit when content is loaded for potential buyers. Because I have to refresh the page 2-3 times to see my plugin. I don't think potential buyers will just refresh the main page 2-3 times. And if the number of featured plugins increases, then the chances of your plugin being seen will decrease, especially if you haven't updated your plugin in a while.
-
Yes, the problem arises because the HumanNPC plugin has the exact same name as the in-game class HumanNPC that my plugin references. So, when starting/restarting, the compiler mistakenly thinks my plugin refers not to the in-game class but to the plugin, leading to an error. That's why detailed information is crucial.
-
Which modification are you using? uMod or Carbon? Also, I need to know the list of installed plugins. Because this error indicates that HumanNPC does not contain skinID, although this is not the case. HumanNPC is a class from Rust itself, which, through multiple inheritances, inherits from BaseEntity and has the skinID property. You should check the integrity of this file: *SERVER*\RustDedicated_Data\Managed\Assembly-CSharp.dll
-
Unfortunately, I haven't received any responses from the developers of these plugins. This conflict (warning) arises from different views among plugin developers on what non-null value should be returned to prevent 'vanilla' behavior in this situation. In my opinion, the correct value to prevent 'vanilla' behavior is the boolean value false, not true. I will stand by my position, but in any case, this warning will be resolved in the next update.
-
Changed Status from Work in Progress to Closed Changed Fixed In to Next Version
-
Unfortunately, I haven't received any responses from the developers of these plugins. This conflict (warning) arises from different views among plugin developers on what non-null value should be returned to prevent 'vanilla' behavior in this situation. In my opinion, the correct value to prevent 'vanilla' behavior is the boolean value false, not true. I will stand by my position, but in any case, this warning will be resolved in the next update.
-
Changed Status from Work in Progress to Closed Changed Fixed In to Next Version
-
If the issue persists, feel free to report it in this thread.