-
Posts
5,916 -
Joined
-
Last visited
-
Days Won
199
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
@Delltus the name field - what the item name will be when you view it in your inventory probability - 0.0 to 1.0 stacksize - when set above -1 it ignores server stack size so you can configure it separately from the rest of the server nice tool, but did you know about the rb.populate command? then you can just edit all items instead of adding individually feature responses: 1. so you want Move Cookables Into Ovens moved into the profiles? 2. so randomly wood, and sometimes randomly stone? for the same base? 3. i will pass on alphaloot compability 4. i like this. noted for later 5. you can have as many profiles as you want but they must be 0-4 in difficulty. this is nice when you want to mix / match your PVE and PVP bases @Razor14150you can add many weapons to that list already example...: "Random Weapons To Equip When Unequipped": [ "rifle.ak", "rifle.bolt", "smg.thompson" ] @God@Delltus fixed in next update should be done with testing very soon as it seems no more issues atm
-
@thepiercedweirdohey, that looks like raideasy10 - just recopy it slightly higher off of the ground, or edit the profile and increase the height to 2.0. it's fixed in next package update if I can ever get to it... to note Maximum Elevation Level can most definitely cause some bases to appear like they've been pasted wrong when in fact they haven't. the default value is 2.5 meters so that is how far the base can be off certain points of the terrain, and likewise how far in it can be too. try adjusting it to 2.0 meters but this can and most definitely will cause issues on maps with bad terrain as it will reduce the potential amount of spawn points on the grid. my suggestion? if you don't want to edit the height to accommodate this setting then just ignore it. the loot shouldn't spawn underground anyway. i don't believe there will ever be a proper fix for this unless maps become flatter
-
@Rubiks-Q-Bertthere is no known fix for this atm so if its a real problem just disable the npcs until i figure it out. this update requires me to learn an entirely different AI and I don't know what I'm doing. it's like trying to find a needle in a haystack. i tell the npc to stay put and it runs off anyway like an untrained dog
-
AI is pretty spot on for the most part in 2.3.0. You may see bots AI act confused or run off endlessly in a straight line... I can't fix this. It can happen while you are vanished, but as for happening with players? Rust will have to fix it I did not rewrite the AI like most plugins. I simply did what I could to improve it. I may in the future, but for now I am very satisfied with how the AI behaves
-
heya bud. this exists already the plugin will not spawn any bases when a restart is pending. so if you start your restarts with restart 3600 then no new bases will spawn within that hour, and it will give all current players one hour to finish existing raids. just adjust the time to your needs. I'd say around 3600 to 7200 should be long enough to finish any raid. as for notification messages they're hit or miss. some players wouldn't see them if it were directly in the middle of the screen
-
The roam range parameter is Aggression Range in the config. this range and deaggresion range increases dramatically when attacked. this allows them to exit the dome and chase the players. no problem. because it is controlled by code that I was missing. it's fixed in the next update (2.2.8) when it's released (soon) I will continue to support both versions. Though I ran into issues after submitting premium 2.2.7 and wanted to focus on fixing it before implementing those changes in the free version.
-
I am making progress but I am still having issues with NPCS not spawning on the navmesh. so at this point I will release an update without npcs enabled, and another update once they are working properly. i'd appreciate anyone who answers this question for those who do not read this message or the update notes