-
Posts
95 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by miniMe_rust
-
Raidable Bases (Tier 3 Package) - Plugin sold separately. Bundle available.
miniMe_rust commented on nivex's file in Bases
Hi @nivex any chance you update the included loot tables to address the changed Facepunch TOS? I followed your suggestion over on the Raidable Bases plugin page and got myself the loot table editor you suggested, also verified it's output with the online check tool for prohibited items (https://app.rustspain.com/facepunch/checkitems). The loot table editor did remove DLC items flawlessly and I got clean loot profiles. But there were warnings from the loot table editor after removing DLC items that bases likely won't have enough items to spawn. I think the problem is that with the removal of the DLC items in the "Difficulty_Loot" profiles the number of available items actually is reduced, and could lead to player complaints about bases having too little and "not good enough" loot. I never changed the original loot profiles you provided with this bases pack, because it was just right and worked great, and players loved the resulting raids. It would be awesome if you could find the time and update the profiles in a sensible way. That would also help customers who buy now and run into the TOS drama. Thanks again -
Hi @nivex, if I understand the rule changes clarifications about Facepunch's TOS and their FAQ right it is all about not being allowed to drop skinned items in a Raidable Base's loot which the participant in the raid does not own. At the same time Facepunch states they have no problem with NPCs using such skins, or decorative elements using such skins. While you're thinking about how to detect which skins a raid owner has in their library, I think the most important configuration change lies within `carbon/configs/RaidableBases.json` within this snippet: "Loot Items": { "Use Identical Skins For Stackable Items": true, "Use Identical Skins For Non-Stackable Items": false, "Use Random Skin": true, "Use Workshop Skins": true, "Use Imported Workshop Skins File": true, "Use Approved Workshop Skins Only": false }, In my eyes all of these lines (except the first line) must be changed from "true" to being "false" - and, if I'm not mistaken - skinned items in a raid's loot should be gone. What is your take on it? Are more configurations needed or suggested? I'm thinking of the option which removes locks from doors when the raid is done, that should be in the raid profiles. That would allow players to pick up skinned doors before the base despawns. That should probably not be possible -
Loot Protection not working for player-called airdrops
miniMe_rust replied to miniMe_rust's Support Request in Support
Hey there! Thanks for getting back to me. Currently I have 2 plugins installed which take care of looting: Horse Lock (not in scope of Simple PVE and should not interfere) Supply Lock (installed to handle player-called airdrops, because Simple PVE fails to handle them) Here is my entire list of plugins (see attached). To be clear, I never used any loot protection plugins until I detected that Simple PVE does not do what the player-called supply drop option says. As you can see in the text file I'm using Carbon (on a Linux server w/ Pterodactyl Panel) with a not-too-many plugins configuration. For the PvE implementation I rely on Simple PVE - in my eyes the best and easiest way to run such a server. If you could somehow get the option do what it says that would be the cherry on top of the pie. plugins.txt -
Loot Protection not working for player-called airdrops
miniMe_rust posted A Support Request in Support
Hey there, there is a problem with player-called supply drops. Even though the loot rules have been configured to only allow the owner to loot such an airdrop, it happens all the time that other players are stealing player-called supply drops. That causes a lot of frustration. Here is the relevant snippet of my `carbon/data/SimplePVE/RulesData.json` "Loot Rules": { "Use Loot Protection": true, "Admin Can Loot All": true, "Teams Can Access Loot": true, "Player can loot other player in PVP Zones": true, "Anyone can open Player called SupplyDrops": false }, -
SimpleStatus not detected on start in carbon
miniMe_rust replied to miniMe_rust's Support Request in Support
Hey there! I don't see this problem anymore. Chances are something in Carbon did cause the problem and was fixed (there have been a lot of fixes and changes in Carbon so hard to say). In addition I decided not to use the status display from Simple Status since player feedback was negative. Players find the additional status information distracting and annoying, therefore we disabled that part. For me the original problem is a non-issue and likely never was caused by Simple PVE -
Hey there! Sadly there has been no response at all. You know these players / teams who have a lot of Diesel accumulated and occupy Exca for a long time. Luckily the community on our server is very cooperative, but every now and then there is a selfish player / team. A minor issue to be fair. Overall players love this excellent plugin as it helps to organize the chaos and helps preventing conflicts and annoyances. There are so many configuration options which I still need to explore, but sadly it seems obvious cool-downs were only considered for individual players, not for teams. -
Yes, team members do have the same access as the player who got ownership. The behavior of monument ownership between team members can be configured - important if one team member loots A and another team member loots B. Can lead to ownership going back and forth quickly. Per default should behave like you say and expect
- 185 comments
-
- 1
-
-
- #jtedal
- #mad mappers
- (and 7 more)
-
I'm using Abandoned Bases with SimplePVE for a long time already, and although there are some quirks, overall it works fine. Quirks: Sometimes players can't inflict damage, and SimplePVE warns that damage was disabled. Next minute the base can be damaged and raided, also rewards are given to raiders as expected when the raid is completed. Another problem is that sometimes the dome and map marker just disappear without a message that the raid completed. In such cases there is no reward given. But as I said, these quirks happen once in a long time, and usually Abandoned Bases just work fine with SimplePVE.- 592 comments
-
- 2
-
-
- #rust
- #rust plugin
- (and 6 more)
-
ammo and fuel in weapons disappear with server restart
miniMe_rust posted A Support Request in Support
Hey there! I have checked out your plugin on my server with Carbon, but it seems that - in conjunction with server restarts as mentioned in other problem reports - there are more problems! Loaded weapons, flamethrowers and chainsaws lose their ammo or fuel. I've added 2 screenshots which depict a) how items were stored in the locker, and b) how the same items were found the day after server restart,. ammo appears to be reverted to how the weapon looks when spawned in fresh the same with the fuel in the flamethrower (was 100, after restart 50) the chainsaw lost all of it's fuel On the bright side weapon attachments (holo visor, extended magazine and weapon flashlight) were unaffected on all 3 guns which had that equipped. I can't see anything interesting / error messages / etc. in the game log. The plugin never complains about anything. There is only the loading message on server startup. If you want to reproduce, that is simple: Load a bunch of guns, a chainsaw or flamethrower and put into your locker. Restart the server. Access the locker. See that your items are no longer fully loaded / fueled.
-
Hi there, basements don't seem to support wallpapers. I'm using your excellent plugin on a PVE server with SimplePVE under Carbon, which generally works fine. But added wallpapers disappear in the course of very few hours. See screenshot - I had wallpapers on the walls, ceilings and floors. They started to disappear on the outer walls first, then floors and ceilings, and finally inner walls. Not sure how or why that happens, but can be reliably reproduced. Thanks in advance for checking.
-
Hi @TheGhostOfChaos I'm scratching my head trying to understand the use case for this plugin. Yes I understand that you can specify and add plugins to a list, which will cause them to be unloaded in a set interval. But I don't get why I would want that - could be my lack of imagination. I either want to have a plugin, then I install it and expect it to be there all the time. When I want to remove it I unload and remove it - no need to keep it unloaded when it is removed. What I understand from the plugin description appears to be a very niche use case, or I just don't get it. I think your plugin could be really useful if you have dynamic rules on your server, maybe want to control the weather or events through other plugins, or disable PVE at certain times. In such a case profiles might be handy, and the ability to schedule over longer time periods - like, for example, every Thursday I want this profile to trigger, which should disable the set of plugins in that profile. When the scheduled duration is passed (e.g. "now" it is Friday) the previously disabled plugins should be loaded again. In the case of a server restart in between start and stop of a profile the intended profile status should be restored. But maybe I'm making it too complicated. Can you give an example use case? -
Not going to argue with you guys @Aero70 @puddingking130 but let me thank you for your demonstration of ignorance. First things first. It is of course possible to control the turret through a computer station. The turret has to be in Attack Mode, and you need to have set an ID. And of course you can fire the equipped gun from the Computer Station. And you can kill players this way depending on what you configured in /sprules. So ... what are you yapping about? And why should the author fix something that isn't broken? You should use the /sprules command and make sure to set the "Disable Traps" option to "false" and "Traps can damage Player" to "true". You should also look at the "Friendly Fire" and "Player can hurt players" rule and set it as you like. -
Hey there, this might be a stupid question, but I'm really struggling with getting a bit of justice to my player base (and peace-of-mind to myself). I'd like to make it so that players can own a monument for e,g, 10 minutes (600 seconds) and then have a cooldown of equal length, so that other players have a chance to become owner. While this might work for a distinct player with the cooldown, that player's team mate has no problem to gain ownership straight away. This makes it unfair to everyone else on the server. How would I have to configure e.g. Launch Site, so that during a cooldown nobody from the player's team can become owner? Here is my current config - it doesn't prevent team members to become owner: --- snippet from "Launch Site.json" in [carbon/data/MM_Data/MonumentOwner/Monuments] --- "Monument settings": { "Timers": { "Cooldown timer after becoming monument owner during which the player cannot claim the title again in seconds": 1200.0, "Timed duration which the player will retaion ownership of the monument in seconds": 1200, "The amount of time which the owner can leave the monument area and retain their title in seconds": 120 }, "Settings for obtaining monument owner status": { "The number of points that the player must receive to become the owner of the monument": 60, "Points for time": { "On/Off": true, "Number of points per 1 sec": 1 }, --- snippet from "MonumentOwner.json" in [carbon/configs/] --- "Should the plugin ignore the admin inside the zone": false, "Should the plugin ignore a player with a Noclip inside the zone": true, "Should the plugin ignore the player with Vanish inside the zone": true, "Should the zone forget the player if he went beyond it": false, "Should the zone forget the owner if he went beyond it": false, "Prohibit the team from disbanding or changing its composition if there is a monument owner in it": false, "Prevent a player from entering an monument area if they are the owner of another monument": false, "Prevent a player from entering an monument area if he has a cooldown": false, "Prevent a player from dealing damage to a target if he is outside the zone and the target is inside the zone": false, "Prevent an NPC or Bradley from dealing damage to a target if it is outside the zone and the attacker is inside the zone": false, "Should the player be allowed to become the owner of another monument if he scored the required number of points? (In this case, the owner's status on the previous monument will be lost for him or his teammate)": false, "Can the player loot his backpack if he is in the locked monument zone": true, "The time during which the player can leave the secondary zone without consequences.": 15,
-
Whether or not proper function of an auto turret is a flaw heavily depends on your use case. I think that's quite a stretch. Generally speaking you should be able to control an auto turrent from a computer table. The turret must be in attack mode, and there must be an ID set. It is not possible to control the turret if it is in peacekeeper mode.
-
The item blacklist will automatically add
miniMe_rust replied to Takeshi's Support Request in Support
Hey there, the automatic addition of items can very easily be stopped. For that open the .cs file in a text editor and remove lines 40 and 41. Before change: [JsonProperty("Blacklist of items")] public List<string> BlackListItem = new List<string>() { "scrap", "rifle.ak" }; After change: [JsonProperty("Blacklist of items")] public List<string> BlackListItem = new List<string>() {}; Save the file & reload the plugin. There will be no more additions of those items to the item blacklist. -
Hi, your plugin is a hit with our players, but they've quickly discovered an issue related to the bank cell feature. They've found that they can store very big stack sizes for common items like metal fragments which they got from raiding Raidable Bases. Currently, if a player tries to store three stacks of 1000 metal fragments each, the plugin prevents it. This is because I limited the stack size to 1000 to counter large quantities being stored in a single slot. However, the plugin fails to consider the number of available slots. If a limit of 1000 of an item is set and there are three empty slots in the bank cell, the plugin should allow storing the item in those slots up to their maximum capacity and consider that limit for each individual slot this item uses.
-
This depends on what you use as map voter. For one you would have to make sure that the seed you've voted on is going into the configuration file of this plugin. Secondly your voter would have to issue a command to the server console, so that the wiper plugin knows to do it's foo. Having said that, something tells me the answer to your question is "no". -
This plugin manages your wipe. Any voting for maps is outside of this plugin.
-
Guys, if you want to add the new "Jungle Ziggurat" monument you can easily do that yourself! Simply copy one of the existing .json files in your "oxide/data/MM_Data/MonumentOwner/Monuments/" directory and rename it to "Jungle Ziggurat.json". For me the Abandoned Supermarket file worked nicely, the zone size fits the Ziggurat perfectly. Copy, adjust name of copied file, done! Thanks again to jtedal for a great plugin!
-
Fridges are no longer loot-protected
-
Hey there, the snippet you posted looks fine. However, you cut off the "Forced" section of that config file. It would have been better to provide the entire config file. Chances are your json is invalid, e.g. a misplaced or missing comma, bracket, or maybe incorrect indentation or even problematic character encoding. You might want to grab another (working) config file from another plugin in a text editor which is capable to show the used encoding, then verify what you have at hand with the wiper configuration. The "Weekly" section of that config however looks fine to me, even though I wouldn't know why you want to keep e.g. players vanished from wipe to wipe (the files you blacklisted from being deleted). But it is your server, and you probably have good reason to do so.
-
Hi there, why don't you simply unload the Abandoned Bases plugin when PvP begins, and load it back in when PvP is over? Can be achieved easily in the config. Valid point for the enhancements to the rule editor.
-
No, nothing is changed. This Server Wipe plugin simply overrides whatever map you have configured in your server config - reliably. If you don't add map seeds to the plugin config it will make and use a random seed. If you add a list of map seeds or URLs the plugin will choose either of the maps from your list and set it in it's own config file. The set map in the plugin config is used to override whatever map you have configured in the server config. That's all.
-
Works, but there are issues e.g. sometimes there is a delay before players can deal damage. But overall working fine with SimplePVE. Carbon here.
- 592 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
Thanks for the hint. I just reconfigured Death Notes to use the same text for turrets and gun traps. Will see how that works, should anyway solve my problem.
