nivex
-
Posts
4,789 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
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 -
Suggestion: Option to show (copy/paste) base name in-game
nivex replied to doublee313's Support Request in Support
Changed Status from Pending to Closed Changed Fixed In to 2.4.7 -
Implemented this in the next update Added `Show Opened Message For PVE Bases` (true) Added `Show Opened Message For PVP Bases` (true) Removed `Show Opened Message`
-
@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 -
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
I have fixed this bug in the next update
-
Changed Status from Pending to Closed
-
this does indeed appear to happen when teleporting using the NTeleportation plugin. please continue the discussion in the active uMod thread. closing this
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
I've added this change in the next update
-
added in next update. it will be enabled by default to block campers from entering the dome Eject Mounts = Campers (true) private object OnPlayerRespawn(BasePlayer player, SleepingBag sleepingBag2) { if (EventTerritory(sleepingBag2.transform.position) && sleepingBag2.HasParent() && sleepingBag2.GetParentEntity().ShortPrefabName.Contains("module_camper")) return ServerMgr.FindSpawnPoint(player); return null; } another option is the above where I just prevent the exploit by not allowing them to respawn on the bed inside of a camper when the camper is inside of a raidable bases event. but this requires a hook and I'm against adding hooks unless they're really useful. but nothing is stopping you from adding it yourself by copy pasting this into the RaidableBases.cs if you prefer this solution instead.
-
i also might be able to just check for this when they join a clan or team actually! that sounds ideal imo it would prevent them from joining any teams if caught exploiting, and remove them from any clan immediately after joining one. i'd prefer to prevent them from joining a clan but there's no hook in the Clans plugin to support this
-
...removed...
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
I've fixed this issue in the next update
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
lastly i have reimplemented the methods used to find a position for bases which was the last issue causing performance issues. though it has always been an issue since day but does not affect most people. either way if this was an issue for you then it won't be anymore
-
Changed Status from Pending to Closed
