nivex
-
Posts
5,814 -
Joined
-
Last visited
-
Days Won
199
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
@m3dus4 no, there is no command. I will make it so typing sab will abort the scan, if one has been started, in next update. what do you mean scans your raidable bases? why is that an issue? @Shneid this is an option, Sphere Amount in the config- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
ya, you would use abandoned bases -
bases don't float unless they weren't copied properly. this is the case for some third party packs, but not my packs. modifying height settings incorrectly in the profiles can cause this too
-
@aimacak yes, if you enable Use Stack Size Limit For Spawning Items (this is for the servers stacksize, not the loot table stacksize) @santigusa heya, sorry for the trouble. i've had it happen a few times to me but i don't know how it happened yet. i've been trying to fix it for months but can never reproduce it. I think I will write my own paste method so I don't have to use the copypaste plugin. this will at least solve bases not despawn on a server restart. however, if you are using linux then the solution is simple. your host needs to install libgdiplus and that exact issue will be fixed you can use /radar buildings raid to find all of the bases and then use /rbe kill_cleanup next to each of them to remove them
-
I think something was lost in translation to your language, aimacak. It will work both ways in next update
-
yea, it's technically doing what it's supposed to. if it's limited to 1k then it should not spawn the configured 10k. though I can understand your use case and don't have any problems making it work both ways depending on the value of the stacksize limit option. current use: if you wanted 10 stacks of 1k then you would set the stacksize to 1k in the loot table. this will count as 10 items towards Amount Of Items To Spawn because it is literally 10 items. so you would also increase the amount of items to spawn by 10. I'll make the amount change dynamically to account for the stacks. while I disagree with this, I can understand that it would need to be changed manually otherwise and that adds unnecessary steps to an already complicated plugin your use case: a single stack of 10k that when looted will obey the servers stacksize of 1k and split accordingly. though players will exploit this by dragging an item onto the stack of 10k in order to bypass the servers limit of 1k. the hook required to fix this vanilla bug is too heavy and won't be implemented.
-
it appears that if the servers stacksize limit is less than the stacksize for an item in the loot table then it will not exceed the servers stacksize limit. I will have to make an exception for this @Alpha28
-
that is how it should work. as i said, it is going to use the servers stacksize limit unless you specify the stacksize for that item. @Alpha28
-
It is intended that Use Stack Size Limit For Spawning Items uses your servers stacksize limit. Plugins that do not modify the actual definitions stacksize for the servers limit are not supported. State the stacksize plugin you use and I can look at it. Otherwise if you want to use the plugins custom stacksize then you must set a custom stacksize for each item that you want to use it with. @Alpha28
-
@Robert Stevensit's part of the AdminRadar plugin on uMod
-
@clippedyes sorry I am trying to fix this. you can unload the plugin before a restart then it would help. you can remove the bases by going to each and using /rbe kill_cleanup and you can find the bases using /radar buildings raid
-
@Kobani Requires A Power Source should be set to false in order to have power without a power source.
-
@m3dus4 this plugin can't prevent players from opening doors. that would be another plugin. do you use any plugins that handle auto auth? do you get a message? remove ownership does not give ownership. it removes it. using /sar claim will give it. the only issue with removal is auth turrets are deauthed which is addressed in the next update. this option does not prevent them from using their base otherwise. this simply sets the owner to 0 in order to bypass PreventLooting plugin though this option isn't required. you can disable it and players can still destroy any boxes in order to loot them. most boxes would be locked so they'd have to destroy them anyway. players with the abandonedbases.convert.claim permission can use the /sar claim command to take over a base.
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
yes you need to update copypaste as aimacak said
-
@m3dus4 heya, set Lock Players To Raid Base After Entering Zone false set Prevent Players From Hogging Raids to false otherwise you need to be more specific if this doesn't work.
-
@aimacak No. I have stated this numerous times. I will help you with your special issue when I can so be patient @MNfreakTim thanks, added a check in next update.
-
@RustyW that would be very very bad for any servers that accidentally enabled that option. not only that, imagine being an active player and your base despawns because the TC owner was inactive. I'd be very mad. it would cause more problems than it would solve.
- 634 comments
-
- 2
-
-
- #rust
- #rust plugin
- (and 6 more)
-
yes anyone with twig issue needs to update copypaste to 4.1.36+ ty nashslash
-
i'll check it out later @Dr.D.Bugbut it worked just fine in my testing. nothing spawned outside of it when only allowed inside, and vis versa @sinansisno, wooden stone metal hqm are in the profiles under Change Building Material Tier To. adobe will not be supported until copypaste plugin supports it. @Killerooxrust must fix this. they're aware and will fix it when they can.
-
yes, the base timer resets if you do not use the plugin for at least 24 hours, and it resets when the server wipes. it does not reset at any other time unless the player is active or has someone active
-
@Kapco411 I just spawned 200 bases for you using Maintained Events to test this, and I looked at each and there were no issues regarding this there were no changes regarding this in the last update either. I have received several reports of the difficulty, and only the difficulty, resetting in each of the profiles to 0 which is Easy. nothing was changed regarding that, and it cannot reset on its own. I suspect a json conversion issue in Oxide but I've not been able to reproduce it myself. if you want to zip these files and DM them to me in a private message then I can look into it further for you. oxide/data/copypaste/ but do not include any paid content from other vendors oxide/data/RaidableBases/ oxide/config/RaidableBases.json it is most likely that you have a few bases in the wrong profiles. this is a common issue with some third party base packages.
-
i was not able to strike the base with Allow Players To Use MLRS set to false as seen by the "You are not allowed to target this location!" messages next i moved the strike zone outside of the boundary, and the impact area was not close enough to damage the base either which you can see by the dust cloud in the center of the image so it may be SkillTree or something else, but we've tested it before and it worked just fine with that too verify that Allow Players To Use MLRS is actually set false in those profiles, and that the difficulty is set properly (very first setting of each profile) too
-
@Stark ill check it out
-
@406_Gromit haha that sounds awesome. how is it on performance though?
-
@Stark you create your groups in the Better Chat plugin you assign my groups to said Better Chat groups my groups are raideasy, raidmedium, raidhard, raidexpert, raidnightmare you then assign your title in the Better Chat group setting once you've done this save it, then add yourself to a group to test. o.usergroup add nivex raideasy type in chat. if you did it correctly then you will see the title. from this point the plugin will do this automatically based on your Ranked Ladder settings in the raid bases config file
