-
Posts
46 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by TheRustingDead
-
@The_Kiiiing Thank you for your prompt, thoughtful and detailed response, I appreciate the transparency regarding the challenges of maintaining the original plugin. I understand that maintaining a plugin that has evolved over time can be incredibly difficult, and I respect your decision to rewrite it from scratch for long-term sustainability. I love this plugin and it has become very important to my server, and many others based on it's popularity. If at any point it continues to become too burdensome to maintain, I wonder if you would consider making it open source on a platform like Github. This could help mitigate some of the challenges you face and allow the community to actively improve upon various aspects of the plugin. To address your points: **Item Search Functionality**: It’s good to hear that this feature is on your roadmap. Having this back will definitely help streamline loot table management. **Removal of Configurations**: While I understand the need to improve maintainability, these configurations were key for server owners like myself. Removing them limits the control we had, which was one of the plugin’s strengths. **Stack Size Import**: If this is functioning as intended, I’ll need to recheck my setup. However, several users, myself included, seem to have encountered issues with the stack size import during the transition. **Manually Enabling Loot Tables**: While I understand it's a one-time action, it did add an unexpected layer of manual work, particularly during an already busy wipe schedule. But I agree that it’s not a huge deal in the grand scheme. **Announcement of V2**: I may have missed the early announcements and beta phase, but I think clearer in-plugin messaging might have mitigated some of the surprise for users like myself who weren’t following the forums closely. **UI and Paid Plugins**: I understand that the Loot API is open source, but I initially interpreted its integration incorrectly. Clarifying its open nature helps, and I appreciate the added flexibility for developers to use it. **Transition Issues**: I realize it’s challenging to anticipate every use case, and I appreciate the effort to smooth things over. However, the rollback to V1 isn’t a long-term solution if support will eventually be discontinued, which is concerning for those of us who have become accustomed to it and rely on stable, functioning systems. **Protobuf vs. JSON**: While Protobuf may offer technical benefits, I don't think most server owners would notice the slight disk space savings. The disk space JSON used was negligible, and unless Protobuf brings clear performance improvements, the flexibility and ease of use of JSON outweighed the supposed benefits for many users, including myself - even if we weren't supposed to be editing it that way. I had no issues in the past making changes this way. I understand that not all users are diligent enough to make changes without corrupting the plugin, again this is not a big deal, just my personal opinion. **Feedback**: I’m glad to hear that you're considering constructive feedback like mine and that many users have had a positive experience with the update. I hope that this approach continues as further adjustments are made. **Documentation**: I’ll take another look at the updated documentation, but clearer guidance from the start might have saved users a lot of confusion. Regarding refunds, I'm simply stating that the product was functioning as advertised and has since stopped functioning in the same way. Per Codefling's refund policy you actually are the only one that could approve a refund, which is why I asked you initially - https://codefling.com/refunds/ However, since you are addressing most of my concerns, I won’t be pursuing a refund. Once again, I appreciate your openness and responsiveness. While I may not agree with every design choice, I respect the challenges you’ve faced and hope that future versions of the plugin continue to evolve with feedback from the community in mind. Best Regards, TheRustingDeadAdmin
- 1,005 comments
-
- 1
-
-
- #loot
- #customloot
- (and 13 more)
-
It's unfortunate to hear that support for V1 will be discontinued. While I appreciate the effort to modernize with V2, I feel the "upgrade" has resulted in the loss of too many crucial features, which makes it difficult for me and likely many other server owners to continue using this plugin. Here are my main concerns: The removal of search functionality for loot tables. The loss of valuable configuration options, such as furnace speed, airdrop settings, and shredder/kiln tweaks. Stack size configurations not properly porting from V1. The need to manually enable loot tables after migration, which adds unnecessary complexity. The sudden, unannounced changes have drastically increased the time required for routine wipes. While the new UI looks visually appealing, it doesn't seem to offer significant organizational improvements and instead highlights additional paid plugins. Many users, including myself, have experienced issues with loot dispensing properly among other problems after migrating to V2. Switching from JSON to protobuf complicates things for the average user, as JSON was far easier to edit and back up. There seems to be little regard for user feedback in this transition. The decision to discontinue V1, despite the feedback, raises concerns about the future direction of the plugin. Additionally, the current documentation is out of date, and no new documentation has been provided for users to understand what commands are now available or when they should be used. This further complicates the transition to V2 and leaves users without proper guidance. Overall, these changes have made me consider more stable alternatives. The removal of key features, increased wipe time, and lack of up-to-date documentation have become too much of a burden. I don't recall seeing any demand for a UI overhaul or the removal of these features, which makes me wonder if there are more unannounced changes on the horizon. Unfortunately, I no longer have the time or patience to relearn the system and reconfigure 100+ loot tables with this wipe and potentially others in the future. If any of my concerns are misplaced I would be glad to know. I have been using this plugin for years and would like to continue doing so, but only if these issues are going to be addressed. I know that critical feedback is tough to hear, and you have obviously worked very hard on these changes. I don't mean to discount your efforts, I am simply providing an honest feedback based on my experiences with the new version. I appreciate the inclusion of V1 so that way users like me have some time to make the transition to V2 or other plugins and continue to have our loot tables functioning as before while they do so. Lastly, are refunds going to be available for users who are dissatisfied with the changes, or should we instead prepare to issue chargebacks? @The_Kiiiing
- 1,005 comments
-
- 2
-
-
- #loot
- #customloot
- (and 13 more)
-
How long can you make these lines? "AIPromptParameters": { "System role": "", "User Server Details": "", Our server has 150+ plugins and a lot of info specific to our server. Does increasing the info in these lines affect the plugin negatively? Or does it increase the token count per response? Just trying to wrap my head around this plugin, love it so far though! Also any chance we could get openwebui integration? I run a locally hosted LLM and would love to avoid the openai costs by using my local instance. Edit: Does anyone know how to get RustCord to not display the RustGPT in the "sync" channel? Currently when a question is answered by RUSTGPT it is sent to the sync channel and then sent back again to the server resulting in a global/doubled response. For now I have the RustGPT response getting sent to a separate channel, but I would like it to appear in discord only as well as privately communicated to the player that asked it,
-
Had to switch back to V1 because V2 was having issues properly filling loot containers. I made sure to enable the profiles in V2, but the loot boxes were not properly dispensing the loot. It looked like it was attempting to use my custom profiles, but it was only dispensing the first item. Once I switched back to V1 and clicked the "refresh loot" option up top it fixed everything. @The_Kiiiing Does this function [refresh loot] exist in V2? Should we expect that you will not provide V1 indefinitely and that eventually we will all need to switch to V2?
- 1,005 comments
-
- 1
-
-
- #loot
- #customloot
- (and 13 more)
-
@Robis nothing has changed it just looks like that, also you should be doing backups before each wipe fyi First off, I think the new UI looks great! I just inspected my loot tables and they actually have not changed, but it is showing "vanilla" for each loot type. You might want to fix this as I am sure it is giving many people running this plugin a mini-heart attack like it did to me. 2 Questions: Is the new "High Quality Revolver" available yet? I don't see it in the weapons list. Is the search function gone for items? I also can't seem to find it.
- 1,005 comments
-
- 1
-
-
- #loot
- #customloot
- (and 13 more)
-
- 69 comments
-
- #rust
- #rust plugin
- (and 9 more)
-
How does this interact with the server.cfg cvar server.max_sleeping_bags "x" ? A few times my players have had issues with this plugin. Upon getting raid and the bag being destroyed their limit was not reset, not by the timer nor by their old bags being destroyed. Here is my .json config: { "Settings Plugin": { "Debug": false, "Chat Steam64ID": 0, "Chat Prefix": "[<color=yellow>Better Beds</color>] " }, "Settings Global": { "Bag cooldown": 15.0, "Bed cooldown": 15.0, "Only 1x rename per placement": false, "NO bed/sleepingbag cooldown": false }, "Settings Bags": { "Refund Sleepingbags": true, "Max placements Default": 1, "Max placements Vip": 3 }, "Settings Beds": { "Refund Beds": true, "Max placements Default": 1, "Max placements Vip": 3 } } I enjoy this plugin, but it needs to include the other potential "spawn" locations like camper beds via vehicles. It needs to be able to override/play nice with the server-side cvar. My intended use case (as seen above) is to grant VIP players more spawns than non-VIP. With the way it works now every player is governed by the global cvar, the only difference is VIP players can put more bags/beds down, but other players can still use those additional spawns in the form of campers beds. I would prefer if these VIP players are able to place/allocate more spawns as intended. If I raise the global cvar to lets say "5" as is the default for hardcore mode (which our server uses) then all players are able to have 5 spawns. I only want VIP players to have access to the increased spawns/"placements". Another major issue is that this plugin does not do anything about the server-side UI message about placements, although it does have a chat command that is executed, the difference in the two messages causes confusion. I read above that you are rewriting the plugin - I will be sure to come check it out after the next update. Good luck and thank you for the hard work ðŸ˜
- 39 comments
-
- 1
-
-
- #rust
- #sleepingbag
-
(and 3 more)
Tagged with:
-
- 1,005 comments
-
- #loot
- #customloot
- (and 13 more)
-
- 1,287 comments
-
- #leveling
- #progression
- (and 19 more)
-
- 104 comments
-
- 1
-
-
- #customizablequests
- #dezlife
-
(and 5 more)
Tagged with:
-
Plugin appears to be causing errors & crashes
TheRustingDead replied to papi's Support Request in Support
just started seeing this error myself, running quite a few plugins so hard to take time to diagnose for it. -
Any way we could get more cvars for the z13 virus? My players are showing boredom with the current way it works. Would there be a way to make it an option so that once players are infected, they are progressively affected with damage? Another idea is making it so the virus has a maximum duration and once it is reached players are either cured or die from the virus and join the horde. Thanks for the hard work as always ðŸ˜
-
- 36 comments
-
- #raulssorban
- #raul sorban
-
(and 7 more)
Tagged with:
-
- 1,005 comments
-
- #loot
- #customloot
- (and 13 more)
-
"It's important to remember that this plugin is provided for free" yes, but is also a required plugin for other paid plugins, I think this invalidates a bit of your argument. You should understand that the consumers here simply expect the plugins to work. If you need to purchase another plugin for any plugin to fully function - in my mind that plugin then becomes, a paid plugin Anything else is extra - including "generous updates"
-
Issue adding items to tables, adding to "Extra items" instead
TheRustingDead posted A Support Request in Support
Getting this output in console - https://paste.ee/p/vb2w5 Was trying to add items to loottables as normal, but I had added an item to "extra items" earlier. After that anytime I try adding an item it will add it to "extra items" instead. I noticed that console output directly afterwards. I reloaded plugin and issue ceased. Thank you for your hard work, this plugin is amazing and so are you 🙂