BlackLightning
-
Posts
205 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by BlackLightning
-
Let's say you set the config to 100k. For an item with 25 max stack size, one full stack can be transferred at once. For an item with 500k max stack size, a full stack will require 5 transfers, so it will take longer. -
Thanks for reporting this. There's an open support request about a similar issue, though I haven't been able to reproduce it yet. I am currently away and will be able to look further into this in about 8 hours. To minimize impact, you can try adjusting the underwater drag in the config to a lower value like 0.3.- 39 comments
-
- 2
-
-
- #helicopter
- #minicopter
- (and 7 more)
-
Thanks for reporting this. Unfortunately, I was not able to anticipate the Rust hot fix that caused this and I am not able to get home for probably 6-8 hours so you will have to wait. This means bags will revert to standard halloween loot bags, leading to the contents being lost when players attempts to open them. For now, warn your players to stash their bags somewhere safe and do not attempt to open them. -
I could potentially implement it, but it adds some complexity because a backpack can change hands, so the rules for a given backpack need to change as the backpack moves around. It creates some nuanced situations for users, like if the backpack is on the ground and has a lot of bags in it, one player (with permission) can pick it up, but another player (without permission) cannot, and the plugin needs to explain to the user what the issue is. There's a similar problem with limiting bags inside of other bags (because the parent bag can change hands), which is why there aren't permissions for those limits. It is probably easier to address for backpacks as they can only hold items while equipped or on the ground, so I can look more into it if it's important to you.
-
There is probably an issue with how you have configured it. First of all, ensure you are configuring the correct section. "Backpack bag limits" defines how many bags players can use inside of Backpacks (the container managed by the uMod plugin of the same name). That section doesn't determine how many bags can be used inside the player inventory. There is a separate section for that called "Player bag limits". If you do intend to set the limit for the Backpacks plugin integration, keep in mind that if the Backpack has multiple pages, bags on all of those pages count toward the limit, so the player may have forgotten about bags on other pages. Within a given permission profile, you can also configure bag limits by category, which may have a stricter limit for a specific type of bag. If so, the player may have reached the limit for a particular bag type. If you have multiple permission profiles defined for a given section of the config, ensure the player has permission to only one of those profiles, or re-order them for proper prioritization, as only one can apply to each player. For instance, a player can have a permission override for "Player bag limits" and a permission override for "Backpack bag limits", but if the player is granted 2 from "Player bag limits", the plugin has to choose which one should apply.
-
Most likely, you placed it in the wrong place, prabably in the content ruleset rather than the bag profile, as the reference option I mentioned will definitely be there (you will see it if you search for it). Try backing up your config and deleting it to regenerate a new one (ideally on your test server). Then you will see the correct place it needs to go, and you can then modify your original config accordingly. Ideally the plugin would automatically update your config file in order to avoid any confusion, but the current logic that determines whether the file needs to be updated has limitations so it did not detect this case.
-
This is supported by the latest version. Set "Enable food spoiling" to false in the bag profile configuration (must be set per bag profile). This option may not automatically appear in the config for existing plugin installations, but you can add it (next to where you see "Allow player item input").
-
What issue are you experiencing?
-
Support tickets do not get deleted. I don't even have the ability to delete them. There may have been a bug on the website, perhaps you typed up the ticket but did not submit it, or perhaps you submitted it on another file or as a general website support ticket. I can't investigate the issue without more information from you. I don't know what you mean when you say the bags turn into loot bags and I can't reproduce that issue. You may be experiencing a plugin conflict, which initially you will have to troubleshoot as your combination of plugins is unique to your server.
-
Under what circumstances are you seeing bags stack inside of each other? If you mean that you are dragging and dropping a bag onto another of the same type, you expect the bags to stack, but instead the bag goes inside the other, that can be helped by enabling stack improvements in the config. Additionally, make sure you don't have the destination bag currently open at the time, or else the moved bag will go inside anyway.
-
If you are experiencing an issue with the plugin, please use the support tab to create a support request. Please also provide as much information as possible so that I can understand the symptoms and try to reproduce the issue.
-
I was able to place a bag in a stash without issue. Do you have any plugins that restrict which items can be placed inside stashes?
-
I just tested and it seems to still be compatible. I can view another player's inventory, then open a bag in their inventory, and even return to the player's inventory from the bag using the back button.
-
@sykosmurf Yes, that looks correct.
-
Technically all bags are "off" by default, meaning they won't appear anywhere on your server unless you explicitly make them available somehow such as via loot tables, shops, kits, etc. The only built-in way that bags can be made available to players is via the "Loot spawns" feature which is disabled by default. If you have enabled loot spawns, simply reduce the spawn chance of bags that you don't want to 0 under "Bag spawn chance percent by prefab".
-
It's working for me.
-
That issue is resolved in v1.3.1, and I cannot reproduce it using latest Oxide (2.0.6119, Rust 2519.246.1). You may have other buoyancy-related plugins that cause the same issue. I heard one server owner had 3 plugins causing this issue, so the errors went away only after unloading all of them.
-
Hi, unlike the Backpacks plugin, which has a dedicated storage container for each player, and which saves backpack contents in a data file to remember them between plugin reloads, Bag of Holding bags are simply items with containers inside them, using the same vanilla capability as weapons that have attachments, water jugs that contain water, etc. As a result, there is no need for the plugin to store the contents in a data file since Rust knows how to save it. If you want to view the contents of the bags currently in a player's inventory, you can just use the Inventory Viewer plugin to remotely open their inventory, then click on the bags and open them. If that is not possible because the bag cannot be found, then there isn't much the plugin can do to help, as that would be the same as losing any item. For what it's worth, I haven't heard this brought up as an issue before.
-
Yes, I plan on maintaining it at least through end of 2025. As for integration with vanilla backpacks, so far it doesn't seem like much will be possible. To open a backpack, the player must click on the backpack while equipped, which shows a container on the left of the inventory. It doesn't appear to be possible for the server to detect that event as it is client sided, so I won't be able to draw any UI over there. At best, we can probably change the visual backpack feature currently in the plugin to show the new backpacks instead of the parachute.
-
I'm not planning anything in particular at this time, given that it's still a few weeks out and subject to change of course. I'll have to do some experimentation to determine what's actually possible to modify, but I'm open to feedback about what people would like to see.
-
I don't think it's possible for this plugin to cause NRE errors. At the end of the day, this plugin just changes the value of a numeric property on each industrial conveyor. NREs happen when an object is unexpectedly null, which this plugin shouldn't be able to cause.
-
I've never seen a plugin do that. The simplest way to do it would be to make a plugin which sets the IO spot's type to Generic. Since there is no wire tool or entities which use that, instead of seeing the white blocks for those connection slots, you will see nothing.
-
That is possible, but is out of scope for this plugin.
-
That issue hasn't been reported yet, but now that you mention it, I think that could be an issue when you have configured the wearable bag limits separately (latest feature released hours ago) since it splits container supervisors which gather mode uses to know which containers to monitor. I'll take a look and figure out a solution in the next few days.
-
Thanks for the report! I've released the v1.6.2 update to resolve this.
