nivex
-
Posts
5,399 -
Joined
-
Last visited
-
Days Won
187
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
heya, this is a loot table, and it's all on one line. I would have to see your profile. a few reasons this won't work: 1. did not set the difficulty (first option) in your profile 2. you have profiles mismatched with the wrong difficulty 3. the reward amount is not set to the desired value "Rewards": { "Custom Currency": { "Enabled": false, "Item Shortname": "scrap", "Item Name": null, "Amount": 0, "Skin": 0 }, "Economics Money": 0.0, "ServerRewards Points": 3, "SkillTree XP": 0.0, "Do Not Reward Buyable Events": false },
-
hi thanks! yes, you can find Arena Walls in each profile and set Enabled for it to false you can use the Loot Amount Multiplier that is also in each profile it isn't possible for me to provide a one-size-fits-all with loot though. every server is different. so might be best to adjust them individually sooner than later
-
debug says they auto spawned. it hit the max for easy medium and hard. looks like your server got stuck saving. no, the plugin did not cause this. you most likely have a null entity in the save list and there's no telling how it got there. use the rbe debug command again. if it continues to say the server saving then it will not auto spawn and I can give more instructions. if there is no more server save messages then reload the plugin to see if that resolves it.
-
hi, use the rbe debug command in the server console to see why. type it again to toggle it off.
-
hi, I've been trying to fix this for months but I cannot fix it when I don't know what is causing it. you can find the bases using AdminRadar plugin, /radar buildings raid and you can remove them by going to the base and typing, /rbe kill_cleanup post your config
-
that makes no sense. kill commands are sent to each at the same time -
ok, I believe everything is in order for the next update to resolve all outstanding issues though it must be tested. I believe I've fixed the one issue with this update but I must verify that before releasing it. so I will let this run on a high pop server for a few days and if that issue is fixed then I will release it.
- 600 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@m3dus4 ok ill look into it
-
@m3dus4 o.reload AbandonedBases but really, it is the best option for that.
-
heya! you would need to change the Convert PVP to PVE to true and make sure any other Convert settings were false.=) it is under Buyable Events, Scheduled Events and Maintained Events in the config file.
-
@m3dus4 might be from another plugin then. such as PveMode.
-
@m3dus4 I still don't understand. why do you have them marked as PVP when there's no base? if the map markers are from raid bases plugin and aren't despawning then you have something preventing them from despawning if you're using linux then the libgdiplus is required. otherwise there is no issue where just the map marker doesn't despawn.
-
@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
- 600 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
heya, 0.0 to 1.0 is the range where 1.0 is 100% - all items have 1.0 probability by default so it is impossible to spawn them all based on probability. probability is determined once the items are pooled together and selection begins. if you want an item to always spawn then put it in the Base Loot tables and enable Always Spawn Base Loot Table in your profiles. you can disable by changing Move Resources Into Tool Cupboard or you can disable specific items from going into tool cupboard by modifying Resources Not Moved To Cupboards
-
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
-
hehe MalS is a good character. he just wants you to explain a bit more with some context so it has some substance to it is all I don't do private work I'm sorry but I have too much to do already
-
thanks, I'm glad you like it. that's exactly why I write plugins to begin with so people can enjoy them. being able to feed myself is of course nice as well =D
-
@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
-
hi, this is not a bug because putting duplicate items into multiple loot tables is not supported because stacksize exists for this very reason if you want an item to spawn multiple times then you would use the stacksize option eg: explosives min: 1000 max: 5000 stacksize: 1000 this would spawn explosives 5 times into boxes randomly. whether or not these items may stack onto each other is irrelevant as the stacksize option is exclusively used in determining how many times and item will spawn. not how it will stack inside of a container. that is controlled by your servers stacksize. i know, it's a bit confusing, but if i were to implement every use case for everyone then the plugin would need to call Jenny Craig no, those options are for Allow Duplicate Items and are not related to this because you should not putting the same into multiple loot tables anyway. eg: you have explosives in your base loot table, but you absolutely do not want more than the configured 5000 to spawn. these should always be in the base loot table though you have other items and you don't care if they are duplicated or not. these should always be in the difficulty loot table you would enable do not duplicate base loot table in order to prevent explosives from spawning more than 5000
-
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
-
hi, it will not exceed the servers stacksize limit after looking into it. I will have to make an exception to fix this that is how probability works - all items are 1.0 by default and so it is impossible to spawn all of them if the amount you have available exceeds the amount that you want to spawn. it can only pick so many. probability determines if the item is spawned AFTER it is picked from this entire collection of items. so there's 2 parts to it. you can't spawn an item without it first being pooled to see what is available. if this still doesn't make sense then I can give an analogy to clarify. ya, always spawn base loot table is how you would always spawn an item. this is why the base loot table has so few items, and the remainder is in the difficulty loot tables where it's randomly picked from.
-
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
