-
Posts
178 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by BlackLightning
-
Changed Status from Pending to Closed
-
Showing inner tubes only some of the time is currently better for client performance but worse for server performance, but only marginally worse because hiding and showing is fast. I should add a disclaimer that this is subject to change. I could make the logic "lazy" by only creating the inner tubes on the server side the first time the heli touches water. That is a good idea. If I do that, dynamic inner tubes would be better for server performance in many cases (though not all, as it depends on a few things). My advice is to keep them dynamic, purely for player experience, since people probably don't want to see inner tubes on their helis all the time, though I could be wrong about that.
-
Setting them to dynamic actually requires that the plugin do some work to toggle them on and off when entering/leaving water. Here is a more detailed explanation of the performance consequences. When the decorative inner tubes are enabled, regardless of whether they are dynamic, they are always spawned and networked to clients. That means there's a greater networking cost when a heli is started or stopped since that is when helis enter/exit global broadcast mode. For example, if someone starts a heli engine across the map, if it was outside network distance, it gets networked to me at that time, requiring that the inner tubes also be networked (i.e., network packets are sent to my client for each inner tube entity). There is a small cost to networking entities to clients (on create, update, and destroy) but Rust normally sends an enormous quantity of network messages per second on populated servers, so I estimate the true impact of the inner tubes to be negligible. When then inner tubes are set to dynamic, even though they are still networked to clients, they are invisible because of a flag. When the plugin wants to show or hide the inner tubes, it simply sends a flag update to clients, which is a relatively small network message, much smaller than a full entity message. The plugin was designed this way in order to minimize the time spent hiding and showing the inner tubes. Overall, the decoration aspect of this plugin, or even the plugin as a whole isn't a performance bottleneck that I'm aware of. Do you have any data or anecdotes suggesting this plugin is causing significant performance loss?
-
If you want to maximize perfomance, disable the floating tires by setting Enabled to false under the Decoration part of the config.
-
- 11 comments
-
Changed Status from Pending to Closed
-
While the player is viewing the vending machine in-person, the skin will be shown if the item is in stock, so players will just need to be careful about buying bags via drone marketplaces since the skin won't be shown in that UI.
-
The small halloween loot bag is a different item. I will test later to see if this can be done. If it can't, I will look into the feasibility of using the small halloween loot bag for the plugin as an option.
-
I don't recall if I've tested this, but it should be possible if the vending machine interface allows selling the large halloween loot bag. To my recollection, not all items are sellable, but most are. If the player wants to sell multiple bag variants, they'll need separate vending machines to get the skin to display correctly.
-
- 36 comments
-
- #helicopter
- #minicopter
-
(and 7 more)
Tagged with:
-
- 36 comments
-
- #helicopter
- #minicopter
-
(and 7 more)
Tagged with:
-
- 36 comments
-
- #helicopter
- #minicopter
-
(and 7 more)
Tagged with:
-
Heli's floating on ground when landed
BlackLightning replied to Butters's Support Request in Support
Changed Status from Pending to Closed -
Heli's floating on ground when landed
BlackLightning replied to Butters's Support Request in Support
Ok, thanks for confirming. -
Heli's floating on ground when landed
BlackLightning replied to Butters's Support Request in Support
I couldn't reproduce this issue with only this plugin loaded. Are you sure this is caused by Buoyant Helicopters? -
Not really. That feature was considered during initial development of this plugin, because the Backpacks plugin on uMod has a similar feature, but ultimately it was deemed too complex and not a good fit for this type of plugin. The biggest capability difference between this plugin and Backpacks is that players must "earn" the capacity by acquiring the bags. If a player loses their bags for any reason, not only are the contents of those bags lost, but the capacity is also lost. If you want to allow players to keep the bags and their contents on death, that would be in scope for the Restore Upon Death plugin to solve. At this time, that plugin doesn't discriminate about which items are retained, but it could be updated to allow the server owner to configure which types of items are kept vs lost, in order to keep Bag of Holding bags (and their contents) on death. Another way to achieve this would be to use the Backpacks plugin with keep-on-death enabled, and only allow backpacks to hold Bag of Holding bags. As a result, players could place Bag of Holding bags inside their Backpack to protect them (and their contents) from dropping on death. If you want to allow players to keep only the bags themselves on death (not the contents of the bags), there is no solution at this time. One reason we didn't try to solve that problem is that it's not clear where the bag contents would go. Depending on how many items were inside the bags, the player's corpse may not have sufficient inventory space to hold all the items. We considered the possibility of creating a "corpse" bag, which is basically read-only bag that would replace the original bag on the player corpse, allowing the player to retrieve the bag contents, but the player would not be permitted to move the corpse bag or add items to it to prevent abuse or bag duplication. We could possibly revisit that idea in the future.
-
Changed Status from Pending to Closed
-
Resolved on Discord. The requester wanted to know how to enable loot spawns in the config. They were new to Rust plugins and didn't know about config files.
-
When you say you cannot put anything in them, do you mean that they have the checkered appearance? If so, that means wherever you placed them (in your inventory, in a container, etc.) has a limit of 0 for that bag category. Bag limits can be changed in the config. By default, players can place items in up to 3 bags in their inventory at once, but cannot place items inside bags that are inside of storage containers.
-
My discord username is blacklightning33.
-
If you want bags to automatically appear in loot containers, you can enable it in the config. It's not enabled by default. The instructions are in the documentation. If you are using another loot plugin, you may need to enable the option that adds the bags with a delay.
-
- 11 comments
-
- 1
-
-
Changed Status from Pending to Closed Changed Fixed In to 1.2.2
-
I tested but was unable to reproduce this issue. This issue was introduced last month with the water update but was subsequently fixed. Can you confirm you are using v1.2.3? According to the download history, you last downloaded this plugin on 4/29, so you cannot possibly be on v1.2.3. Simply update to v1.2.3 and the issue will be resolved.