-
Posts
2,500 -
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
-
Changed Status from Work in Progress to Closed Changed Fixed In to 0.1.5 -
Hi, please re-download the plugin. Everything should work now.
-
Changed Status from Pending to Work in Progress
-
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! -
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.
-
If the issue persists, feel free to report it in this thread.
-
I've resolved the issue, so it won't occur in the next update. However, if you'd like to fix this problem immediately, feel free to message me privately, and I'll send you the corrected file.
-
Changed Status from Work in Progress to Closed Changed Fixed In to Next Version
-
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.
-
I have a slight suspicion that you have the HumanNPC plugin by Razor installed, and the compiler thinks my plugin is referencing his HumanNPC class instead of the HumanNPC class from the game itself.
-
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
-
Changed Status from Pending to Work in Progress
-
@original4d And I strongly urge you to create a support ticket with more detailed information about the issue, rather than posting in the discussion section, as troubleshooting in that section will only lead to confusion.
-
@original4d To solve any problem, it is essential to understand what is causing it. Without providing the necessary information, such as installed plugins, error logs(especially), configurations, etc., this is not possible.
-
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.
-
Changed Status from Work in Progress to Closed Changed Fixed In to 0.1.4
-
If the issue persists, feel free to report it in this thread.
-
Changed Status from Work in Progress to Not a Bug
-
Hello, you're talking about BalanceStatus, but this is BalanceBar. I named it that because BalanceStatus was already taken. -
*del