Jump to content

nivex

Creator
  • Posts

    5,154
  • Joined

  • Last visited

Everything posted by nivex

  1. nivex

    hbhf sensor

    Changed Status from Pending to Closed Changed Fixed In to Next Version
  2. nivex

    hbhf sensor

    I've added this change in the next update
  3. nivex

    Campers Exploit

    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.
  4. nivex

    Clans/Teams Lockout Issue

    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
  5. nivex

    Clans/Teams Lockout Issue

    ...removed...
  6. nivex

    Despawn Issues Still

    Changed Status from Pending to Closed Changed Fixed In to Next Version
  7. nivex

    Despawn Issues Still

    I've fixed this issue in the next update
  8. nivex

    Crazy amount of lag

    Changed Status from Pending to Closed Changed Fixed In to Next Version
  9. nivex

    Crazy amount of lag

    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
  10. nivex

    Entity 1000000

    Changed Status from Pending to Closed
  11. nivex

    Crazy amount of lag

    also have raid bases set to kill these entities immediately if any spawn in the next update (2.4.8) too
  12. nivex

    Crazy amount of lag

    attached it below np CopyPaste.cs
  13. nivex

    Raidable Bases

    @chuck norrisyes
  14. nivex

    Raidable Bases

    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!
  15. nivex

    CUSTOM SPAWNS

    Changed Status from Pending to Closed
  16. nivex

    CUSTOM SPAWNS

    well damn that is news to me. nice find. glad its sorted
  17. nivex

    Crazy amount of lag

    this issue was fixed already. the issue you're experiencing is with the saddletest and fuel_storage being leaked by CopyPaste. downloading tier 3 update and replacing the copypaste files will fix it. this can easily take up an excessive amount of memory. I can share CopyPaste fix as well if you like
  18. nivex

    Loot & Corpse Timers

    Ill look into it regardless
  19. nivex

    Entity 1000000

    heya, this was fixed last December. you can download the tier 3 update and replace the copypaste files with the fixed ones. this happens because CopyPaste copies Unity scripts (saddletest and fuel_storage) when it should skip them. I have contacted the CopyPaste author to fix this but was ignored.
  20. nivex

    CUSTOM SPAWNS

    you would rename it to the name of the file generated by Spawns Database without the file extension. so if the filename was spawns1.json then you'd replace none with spawns1
  21. nivex

    Raidable Bases

    which bug since March? @MercedesCLA45AMG
  22. nivex

    Raidable Bases

    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
  23. nivex

    Raidable Bases

    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
  24. nivex

    Loot & Corpse Timers

    hm ill look into this but I see no reason it would happen unless a plugin is interfering and I don't believe Backpacks plugin could. corpses that turn into backpacks when ejected are not related even though they share the same name however the two options for corpse and backpack are related in some cases but that's not an issue just a distinction
  25. nivex

    Help

    heya. the command is /sar
1.8m

Downloads

Total number of downloads.

8.4k

Customers

Total customers served.

127.3k

Files Sold

Total number of files sold.

2.6m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.