nivex
-
Posts
5,154 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
base marked as complete even though looker are not destroyed
nivex replied to MOnk3yM4st3r's Support Request in Support
Changed Status from Pending to Closed -
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
tyty looks to be sorted. can you confirm @doublee313
-
@BetterDeadThanZedthe plugin is bugged, though. your solution works because the plugin is telling TruePVE to use your ruleset when it is supposed to be telling TruePVE to outright allow it
-
unfortunately protection radius is the only modifier for this and it would prevent the plugin from spawning bases if its too large. it should be large when spawn points are manually added on islands for example, or when dedicating regions of a map specifically for raid bases with no build zones in zone manager and that would require you add said zones to the config too glad to hear the performance issue is fixed! if it is still fixed please let me know and i will submit the update
-
@ZEODEif you don't mind... change to: the lag might have to do with how many locations are on the grid, which would cause the search method to take longer to execute and potentially rubberbanding
-
did you try this after a server restart btw?
-
Yes, that's essentially what I said
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
@ZEODE can you replace this in the code (RaidableBases.cs): public Coroutine StartCoroutineEx(IEnumerator enumerator, string methodName) { Action<Exception> action = new Action<Exception>(ex => { if (ex == null) { return; } Interface.Oxide.LogInfo("[{0}] {1} : {2}", "Raidable Bases", methodName, ex); }); return ServerMgr.Instance.StartCoroutine(Choke(enumerator, action)); } with this: public Coroutine StartCoroutineEx(IEnumerator enumerator, string methodName) { return ServerMgr.Instance.StartCoroutine(enumerator); } and tell me if it fixes the issue? you literally just search for StartCoroutineEx, select all of the relevant code shown in the first snippet, and replace it with the code shown in the second snippet
-
it is in the next update
-
@Wolfsorry I missed your comment. did you figure it out? -
Ill add option to not bypass twig then
- 583 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
heya @thepiercedweirdo it is intentional that twig is ignored and controlled by decay instead the min requirements are at your discretion. i believe a min of 1 would prevent that issue, but create others where abandoned bases pop up that have no profit at all (such as a few cloth or a pickaxe, etc)
-
run out off the wall? @Ateszahun -
2.1.6 has no issue with rubberbanding. the issue started in 2.1.7
-
hi, try this option Use Stack Size Limit For Spawning Items
-
@Swedish Chefvery well, I will note this for you and implement it after I fix the current issues
-
it's not possible for the commands to not be recognized unless there's an error
-
no problem, but as I stated it isn't possible to use zones because I do not use zone manager. the support i added will use profiles you configure from botspawn and spawn those at the abandoned bases so for example, you add a few profiles to the abandoned configuration and it will then choose one of them randomly and spawn all of the bots from that randomly chosen profile. you can also specify just 1 profile if you like.
-
@ZEODEperfect thank you guys so much for being so detailed. this will help me narrow down the issue
-
@olajmuveksoon. I must fix the issue with server performance degradation before I release the update
-
@KingSizeKevin yes, there are 3 permissions in the configuration file and the default group must be assigned one of them. you can then assign your VIP players a longer permission, etc in order for this to work automatically then you would need to enable it to do so in the configuration file: "Run Once On Server Startup": false, "Run Every X Seconds": 0.0, I suggest running it on server startup on to conserve server resources. if you insist on running in on a timer then it should be no less than 3600 seconds. you can manually start this yourself using the command sab
-
hey sorry about this guys. I broke it somehow in the update. will get it fixed asap