Leaderboard

Update is coming out in a few days which will address all the changes

4hrs of fiddling with this plugin to sort loot profiles for easy convoy. got nowhere, loot wont populate. Just going round and round with this structure, alphaloot is not recognising the prefabs and is populating its own configurations. At this point im just going to remove all plugins that require using this plugin. Its not helpful for me at all, i dont have time to go back and forth between screens on a gui. Its a no from me!

yes we are working on an update now to make it compliant and adding in some more custom skins.

100% agree. This should be optional and shouldn't be a dependency. I hope the Mad Mappers team see that it wasn't a good change and revert back.

Hey everyone just a quick update. Ive been packing some new features into this update that I think you are all going to really enjoy, I personally am not a fan of the sudden removal of game accepted skins so there will be options I'm adding to skinner that will hopefully help smooth things over for your player base. I don't want to go into too much detail into the extra features side, however currently in the update I have new options for removing all FP accepted skins/dlcs, automatic filtering for imported skins and commands to remove imported skins as well. If anyone has questions feel free to dm me or discuss in my discord. https://discord.gg/cobaltstudios

@Whispers88 could you please add a option to "remove" / "hide" or deactivate **all** official skins from the plugin? this would help a lot to avoid using skins that get accepted after we added it to the data. in best case, you could also allow players that own a specific official skin to make them being usable in the skin menu.

Or he is just trying to get it all fixed up? 2 updates in last 12 hrs or so is hardly doing nothing. KpucTaJI has been here for years and has always stood behind his plug ins. When needed updated in a timely fashion. Seems like he wanted to do a major update and it didnt go perfect. Mind you it would have been FREE for current customers. Maybe instead of name calling and being all derogatory one should just give him the benefit of the doubt.

Can change this var dItem = __instance.SpawnLootListItem(player) as DroppedItem; To this for now to get it to compile var dItem = __instance.SpawnItem(player) as DroppedItem;

hey, will there be some migration assist option from BetterLoot? Currently most of my plugins use that, but I'd be interested in switching to this. Thanks!

I can look in to it, for sure. The hard work's already done with the existing drone targeting. Thanks for the suggestion.

Doing some prelim testing atm and fixing up a couple of new bugs, but the update should come out monday. To give a few days for feed back and such.

love the plugin, brings life to server for sure, only issue is the fire rate. They seem to fire one bullet every 2-5 seconds. Very slow, even when given an ak or mp5- just pop.........pop.....................pop. Cant wait for bases!

It's planned, in new addon these bots will be able to build bases and store loot in them

This plugin contains separate Carbon and Oxide flavors inside, and I think only the Carbon one was fixed. Here's an untested attempt to port the Carbon fixes to Oxide: https://gist.github.com/HunterZ/c8c848d159fadad6e020bf139b6bac08 An official update from Edwin is now available, please use that instead!

There are multiple tools available (RB loot table editor, and various websites) to help you with removing paid content. In the next update, I will have two additional ways to handle this for Raidable Bases: An option, which is enabled by default, and will remove paid content without modifying any files. A command, generated at random, that will permanently remove all paid content from your copypaste and loot table files. The command name is randomly generated and stored in the configuration file. Only those with access to your configuration files will be able to see the command name. This can be used as a server command, or by those with auth level 2. It will never be permission based. Example output with tier 1, tier 2 and tier 3 packags installed.

@Amadeus.pve Hi, do not worry, turrets will be addressed in the next plugin update. All paid content will be blocked from spawning by the new option until Facepunch is able to clearly outline specific exceptions. I've asked them to comment further on this, but haven't gotten a response other than to wait for the dev blog.

Heya, I hope this message finds everyone well. Please help spread the word should someone ask about this. Please ensure that any paid content, DLC items or workshop skins, are removed from your files to avoid breaching the recent Facepunch TOS changes. I’m working on a solution, but I can’t promise it will be flawless right away—expect a revision or two to resolve any edge cases. Realistically, the first iteration may just offer a blanket blacklist for all DLC and workshop skins—we’ll see what happens. Unlike solutions already implemented by other plugins, RaidableBases has multiple other issues to account for: Players looting and moving items, where some player might try to loot content that they do not own. This can happen under several different conditions, and would require another hook that which impacts performance. Skinning items for public events, where the owner is not set beforehand. This seems easy enough to solve, except the fact of the first issue. Skinning items for purchased events, where the owner is determined beforehand, but it's unclear if it would be in violation should other players join after the fact, when they do not own the same content. Items contained in your CopyPaste files (oxide/data/copypaste or carbon/data/copypaste), which could violate TOS when players do not own that content. Direct item spawns from other plugins, and more. Ultimately, it’s each server owner’s responsibility to keep their own files in order. I know it can be a time-consuming job, but that’s simply part of running servers. Facepunch is right to tighten the rules, even if enforcement won’t be simple. The sooner we clean things up, the fewer headaches we create for them—so they can focus on making new content and fixing existing content, instead of policing avoidable TOS violations.

After some more testing I was actually able to reproduce the problem and there will be a fix for it in the next few days. In the mean time to prevent this from happening just disable your custom configurations for oil rig and deep sea npcs.

Most likely, yes. I'll have to take a look at it, though.

I am going to look into it and make an update. Thank You.

Where'd jbird go? he was better help..

having to use loot manager now is lame

Comment out these lines to make it work temporarily. However, the oven multiplier will not work. 8555 and 8556 Instance.NextTick(() => { // Oven go brrrrrrrrrrr //oven.CancelInvoke(oven.Cook); //oven.InvokeRepeating(oven.Cook, tickTime, tickTime); });

Hi, 3.1.2 has been released This requires the Rust update to compile, enjoy

Sorry guys, I made changes to the plugin that were based on staging with the expectation that those changes would be pushed to main like always (a simple method name change). Alas they did not. It has been fixed.

This should 100% be optional. For now, im going back to old version of event without lootmanager.

While I appreciate your efforts and what you have done, I don't like the feeling of being forced into additional plugins without any discussion. While I have not tried Loot Manager yet, IF I am HAVE TO go down this road, editing configs is a lot better than UI's.. as least you are assured your settings are saved correctly.

II find it was easier to manage the loot from config than with this tool

Very nice idea, we'll probably implement it

Hey - I am the one that opened the original ticket about the red text issue. It is solved, following 0xF's guidance. I really don't understand the emotions here. This is a free plugin, a very good one, that helps the community altogether. 0xF has been nothing but nice to all of us in explaining the issue, and I can personally vouch that he does help a lot in a kind manner. Let's please tone down the emotions, there's no need to bash on a dev that's actually very decent and supports the community.

@imthenewguy here is an example of the wonderful things being done with your plugin hJune said it was a religious experience LOL. My brother and I made this on the Art of Rust server using the deployable nature plugin to create the mine.

For this reason, we have made a custom chair that can be given to players without restrictions.

Thank you @nivex for all your hard work, especially to address concerns about changed ToS. Personally I will do both, enable the new option to suppress paid and DLC items, and additionally use cleaned loot tables (your original from the Tier 3 bases pack, cleaned using a loot table editor) because APIs can fail and I don't want to blindly trust an option. Nonetheless I find your level of support and commitment outstanding and inspiring. Thank you so much. If you ever decide to sell support packages (= donation) to generate some extra income for your hard work, I'm pretty sure not only me will be happy to buy one once in a while. Such packages could be several sizes, depending on how much a user wants to support or can afford - not sure if codefling allows such "empty" packages. It has been about 2 years since I purchased your plugin and bases pack, and it feels a bit strange to have you working on and improving your fantastic plugin, and getting nothing in return. Keep up the great work!

Post #3901 3.0.6 has been released. This requires the Rust update to compile. Also, please read the update notes!

yes!

I made some improvements, now you can validate by fields.

This is a very useful tool for checking your configs & data files for now banned skins & items https://app.rustspain.com/facepunch/checkitems Link courtesy of @ninco90

Thanks for letting me know. If it's something a lot of people need, I can certainly prioritize it.

Kind of like the 5 star reviews. They're not even reviews, they're brown nosing the dev whilst calling us idiots. Whack

Got in touch with Edwin and he says he doesn't have time to maintain this, so he gave me co-maintainer. I've released 1.2.0 to try to address some issues. Please open or add to support tickets if you encounter any issues with this version.

This was just a quick fix to make the plugin compile again. There will be a proper fix in the next few days

Yes, I am and I also seriously against unnecessary forced changes that favours a small group without discussion or question. It is a little presumptious to assume everything is "working as before", for everyone, it may be for you and that is great, it is not for me. Ok, if you want to know how it affects my workflow, well; - Extracting singular parts of loot configurations from one plugin config file and exporting each as a singular data file is messy, it creates a lot of files, it makes manual .json editing a total mess. - The file extractions make a lot of presumptions, - suddenly the data files are named names I don't recognise. - The naming system uses some names I used in my config, sure but that is not intuitive as the name of a data file. Are you aware how disruptive that is? Imagine I opened your 1 year of notes, tore out all the titles, mixed them up, then re-wrote all of your notes in a way more familiar to me, then stuck every one of them from your note book to your wall with selotape. Now its easier for me to see them... but what about your notes Do you see my point? - There is absolutley no folder organisation between the loot tables - they are all in one folder (lets say shipwreck, Caravan, Convoy, Armored Train for reference) - suddenly I have a huge pile config files with no organisation. - This is not helpful, it has a huge negative impact on time, organisation, naming structures, editing of configurations. - There is no consolidation of files or ease of access here. - I could go on I'm quite sure I'm not alone here with these issues. I hope this can be read constructively and not with annoyance or aggression, I am sharing my thoughts, I only see many problems with this, in its current state and how it affects my use of Adem's plugins which are heavily customised. There should be an option to "opt out" or not use this plugin, at least until it can be fully finalised.

Hi, I'll try to check and update it tomorrow.

All in on an option for them to target TCs.

I add in config params next week

you mean some thing like that?

Don't worry about doing any more testing. I looked into this with a few other users and got to the bottom of it a few days ago. That'll also be addressed in the next update. If it's an issue, until then, you can run 1.3.9 without issues. Thanks for the info!

Yeah that's the plan

Same here. Since wipe the SkillTree (for mining/woodcutting) or Cooking (for harvesting from plantation) aren't taken in account and Quests pick vanilla rates. There are no errors to be seen.