nivex
-
Posts
5,812 -
Joined
-
Last visited
-
Days Won
199
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
had this saved in my notes to come back later and now i'm really confused. this plugin doesn't protect players while they're online. TruePVE or NextGenPVE plugins handle that. this plugin simply tells those plugins to allow the damage when the base becomes an abandoned base so what you're asking for is this plugin to allow damage when they're online? i'm not sure I want to add that as it's not really what this plugin is about, and it would require a lot of conditionals as well which would be better suited in its own plugin. I think I misunderstood your original request- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
multiple loot tables exist to minimize the chance of raids becoming too predictable and boring. players will quit playing when this happens so it's important for player retention. 1 loot table limits you too much because you will not have any items that spawn each time. if all items spawn each time then it brings me back to my first point where it makes the loot too predictable and boring loot should have a large variety (150+ items) of items to pick from with some guaranteed drops as well. by using difficulty loot and base loot tables with Always Spawn Base Loot Table enabled then you can achieve the following: 1. your primary loot table is the difficulty loot table so this lets the plugin choose from a large selection of items randomly. this will ensure that loot is different each time 2. base loot will guarantee that items like scrap, explosive ammo, c4 and rockets spawn every time. now for number 2 you do not want too much of these guaranteed items to spawn otherwise you are enabling instant gratification and that will hurt player retention it's up to you to determine how much loot spawns, and to ignore the entitled players that say it isn't enough. you should have a good understanding of how much is too much, and if you don't understand this then you can do so by raiding the bases yourself and determining how profitable it should be. profits should be acquired gradually over multiple raids for best results for player retention. like you said, sometimes you get more loot than other times... that's perfect. -
@Hawkhillsounds like a good plan but i do suggest removing any useless items from the higher difficulties. mainly beginner items such as burlap etc also you will always have that 1 player that complains the loot isn't good so unless everyone is complaining then just ignore them. they just want instant gratification and thats not the way to go using this plugin however make sure there's specific loot that always spawns. the Base Loot tables should be used for this, with the Always Spawn Base Loot Table enabled in each profile. the loot in this file should have a range of min and max amounts so that a random amount of each item will spawn. so for example rockets with min 1 and max 3 for easy bases and whatever else. obviously the amounts will differ server to server as each has a different gather rate and mods that offer varying gather rates so there's no universal numbers to use if it becomes popular and people are constantly raiding the bases then you've done it right. if they're not then you should revisit it i suggest to spawn 3-5 bases at all times as well to retain more players and not focus efforts solely on purchasing bases. a mixture of both is ideal on almost every server because raiding is one of the most important objectives in the game and this provides an abundance of that so its very appealing to players and they wont disappoint i strongly advise against anyone using loot in their copypaste files. it should be spawned from the loot tables. this allows the loot to be in different boxes each time. static loot in the same boxes every time is predictable and boring no matter the intention behind it. some randomness goes a long way to retaining players and retaining players is my main selling point these are just common mistakes i've observed users doing so i try to provide valid points so that others understand the negatives of them and don't repeat them
-
@Hawkhillah right sorry for the confusion, setting Stone Walls to false does indeed spawn Wood Walls for anyone else looking for the answer. I don't plan to add a third option for this as it's intended to work this way, but I will update the documentation
-
@Hawkhillthanks. no plans to include bases in the plugin. that would require all of the config, profiles and loot tables to go with it and I already have tiered packages that provide all of that you can change the walls in the profiles to wood, stone or ice, oxide/data/RaidableBases/Profiles/ ice walls were bad on server performance so I suggest not using them if they stll are (client bug, not plugin bug)
-
@Herrcooles I didn't ignore anything. You were given the answer by Swedish Chef and I thanked him for it by giving him a thumbs up... thanks again Swedish Chef
-
@GamingHQany bases prior to the fix will remain on the server until you delete them or wipe the map. you can cleanup any of those bases using /rbe_cleanup while standing at the base
-
hi, set this false Drop Tool Cupboard Loot After Raid Is Completed, otherwise it is not this plugin dropping the loot thank you @Neighighfor the assist
-
added in next update Added `Custom Cost To Manually Convert (0 = disabled)` (0 scrap) Added `Custom Cost To Cancel Conversion (0 = disabled)` (0 scrap) added in next update Added `Seconds Until Event Can Be Canceled` (0)
- 634 comments
-
- 2
-
-
- #rust
- #rust plugin
- (and 6 more)
-
hi. buyraid is not broken in 2.4.9 either disable Obey Max Difficulty Limits or set the limit above -1 to enable the purchase of the difficulty
-
2.4.9 released to fix scheduled events not spawning there are some reimplemented features as well. nothing really needs edited in the profiles unless you want to change the amount of npcs that spawn. i don't recommend adding more npcs as that will only serve to degrade server performance accuracy settings should be ideal for all servers
-
@Delltus @Baron Von Finchus Accuracy per weapon implemented in next update "Weapon Accuracy (0 - 100)": { "AK47": 15.0, "Bolt Rifle": 15.0, "Compound Bow": 15.0, "Crossbow": 15.0, "Double Barrel Shotgun": 15.0, "Eoka": 15.0, "L96": 15.0, "LR300": 15.0, "M249": 15.0, "M39": 15.0, "M92": 15.0, "MP5": 15.0, "Nailgun": 15.0, "Pump Shotgun": 15.0, "Python": 15.0, "Revolver": 15.0, "Semi Auto Pistol": 15.0, "Semi Auto Rifle": 15.0, "Spas12": 15.0, "Speargun": 15.0, "SMG": 15.0, "Snowball Gun": 15.0, "Thompson": 15.0, "Waterpipe Shotgun": 15.0 },
-
ok, this isn't a bug. -1 means that difficulty is disabled set Hard to any value above -1 to fix
-
the value is -1 so Hard is disabled. set above -1 I need the full error. its in the server log -logfile log.txt or such of the server startup script
-
If you own multiple tier packages... they are now unique and you can update Tier 1 or Tier 2 package to 1.0.6 Tier 3 package is unchanged Download the respective tier(s) and copy the new base files from the data/copypaste/ folder in the zip archive into your oxide/data/copypaste/ folder For TIER 1 use the console commands: rb.config add "Easy Bases" raideasy11 raideasy12 rb.config add "Medium Bases" raidmed11 raidmed12 rb.config add "Hard Bases" raidhard11 raidhard12 rb.config add "Expert Bases" raidexpert11 raidexpert12 rb.config add "Nightmare Bases" raidnightmare11 raidnightmare12 For TIER 2 use the console commands: rb.config add "Easy Bases" raideasy13 raideasy14 raideasy15 raideasy16 raideasy17 rb.config add "Medium Bases" raidmed13 raidmed14 raidmed15 raidmed16 raidmed17 rb.config add "Hard Bases" raidhard13 raidhard14 raidhard15 raidhard16 raidhard17 rb.config add "Expert Bases" raidexpert13 raidexpert14 raidexpert15 raidexpert16 raidexpert17 rb.config add "Nightmare Bases" raidnightmare13 raidnightmare14 raidnightmare15 raidnightmare16 raidnightmare17 -
If you own multiple tier packages... they are now unique and you can update Tier 1 or Tier 2 package to 1.0.6 Tier 3 package is unchanged Download the respective tier(s) and copy the new base files from the data/copypaste/ folder in the zip archive into your oxide/data/copypaste/ folder For TIER 1 use the console commands: rb.config add "Easy Bases" raideasy11 raideasy12 rb.config add "Medium Bases" raidmed11 raidmed12 rb.config add "Hard Bases" raidhard11 raidhard12 rb.config add "Expert Bases" raidexpert11 raidexpert12 rb.config add "Nightmare Bases" raidnightmare11 raidnightmare12 For TIER 2 use the console commands: rb.config add "Easy Bases" raideasy13 raideasy14 raideasy15 raideasy16 raideasy17 rb.config add "Medium Bases" raidmed13 raidmed14 raidmed15 raidmed16 raidmed17 rb.config add "Hard Bases" raidhard13 raidhard14 raidhard15 raidhard16 raidhard17 rb.config add "Expert Bases" raidexpert13 raidexpert14 raidexpert15 raidexpert16 raidexpert17 rb.config add "Nightmare Bases" raidnightmare13 raidnightmare14 raidnightmare15 raidnightmare16 raidnightmare17 -
If you own multiple tier packages... they are now unique and you can update Tier 1 or Tier 2 package to 1.0.6 Tier 3 package is unchanged Download the respective tier(s) and copy the new base files from the data/copypaste/ folder in the zip archive into your oxide/data/copypaste/ folder For TIER 1 use the console commands: rb.config add "Easy Bases" raideasy11 raideasy12 rb.config add "Medium Bases" raidmed11 raidmed12 rb.config add "Hard Bases" raidhard11 raidhard12 rb.config add "Expert Bases" raidexpert11 raidexpert12 rb.config add "Nightmare Bases" raidnightmare11 raidnightmare12 For TIER 2 use the console commands: rb.config add "Easy Bases" raideasy13 raideasy14 raideasy15 raideasy16 raideasy17 rb.config add "Medium Bases" raidmed13 raidmed14 raidmed15 raidmed16 raidmed17 rb.config add "Hard Bases" raidhard13 raidhard14 raidhard15 raidhard16 raidhard17 rb.config add "Expert Bases" raidexpert13 raidexpert14 raidexpert15 raidexpert16 raidexpert17 rb.config add "Nightmare Bases" raidnightmare13 raidnightmare14 raidnightmare15 raidnightmare16 raidnightmare17 -
@Rustgaming2021this would need to be added, and would only work properly if the events ran every hour
-
@chuck norrisyes
-
despawn issue during server restarts is fixed in the next update! woo! private void OnServerShutdown() { IsUnloading = true; SaveData(); RaidableBase.Unload(Raids.ToList(), true); Scheduled.StopCoroutine(); Maintained.StopCoroutine(); SpawnManager.StopCoroutine(); GridController.StopCoroutine(); DestroyAll(); } SaveData(); was missing from this method. RIP. so sorry that I overlooked this!
-
which bug since March? @MercedesCLA45AMG
-
just found the bug that's causing some servers to not spawn any bases. this is a unity bug and has been reported to Facepunch. i've also implemented a workaround for it in the next update. private static bool IsSafeZone(Vector3 a) { for (int i = 0; i < TriggerSafeZone.allSafeZones.Count; i++) { var triggerSafeZone = TriggerSafeZone.allSafeZones[i]; try { if (InRange2D(triggerSafeZone.transform.position, a, triggerSafeZone.triggerCollider.GetRadius(triggerSafeZone.transform.localScale) + config.Settings.Management.MonumentDistance)) { return true; } } catch { return true; } } return false; } here is the workaround if any want to use it. just replace the existing code block for the IsSafeZone method with this code. or if that sounds too difficult for you then rename the existing IsSafeZone method to anything else such as IsSafeZoneBROKEN, and put this workaround code above that
-
thanks guys I will try to fix these issues. sorry some are frustrated but bugs are just a part of all software. it sucks but all I can do is try my best. I wish I could do more but my health isn't so good atm
-
@thepiercedweirdoheya sorry about this issue. I have not been able to reproduce it but I will figure it out. good suggestion but I already do this by recording all entity unique identifiers to find and kill them after a restart. I will try to reproduce during a restart. good info ty and let me know of any other details regardless of how important you think they are.
-
I can try @MooDDang
