nivex
-
Posts
5,160 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
@BeePssY yes, you can use the spawns database plugin and just set that filename under whatever event type in the config, "Spawns Database File (Optional)": "none", so if the filename is maintainedspawnpoints.jsosn then you would replace none with maintainedspawnpoints. don't include the .json extension -
np @Emigo @Tiddy oh so I gotta do it. lol. ok ill try
-
@Tiddyit looks nice! can you have it scale down the size so it doesn't include lockouts with no time?
-
Changed Status from Pending to Closed
-
@Emigono, but that is fixed next update which will be out soon @Tiddytoo many complaints about users accidentally turning it off. just sick of dealing with that. the ui class needs a rewrite anyway. I would use a better UI yes. I suck at UI. =P
-
it should be fixed next update @chuck norris its most likely topology check blocking it. my bad =p if (!spq.spawns.IsCustomSpawn) { string topology; if (!SpawnsController.TopologyChecks(vector, spq.buildRadius, out topology)) { LastMessage = $"Spawn is on blocked topology ({topology})"; continue; } } this is the fix, the first line with its open and closed curly brackets go around the enclosed lines of code
-
you can look to see which tables didn't load with the plugin to know which are broken
-
actually it looks like 3 of them have the same json error
-
hey. its telling you that one of your loot tables has a json error
-
it is working. minus an issue where heads poke through blocks the npcs spawn fine. this issue is on your end.
-
read the update notes. its pre-release Changed Status from Pending to Closed
-
2.5.0 released you must wait until Rust releases the update! it will not compile until then if you have issues (including previously reported issues) then report them to me again
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
hopefully this is fixed in the next update 2.5.0
-
lol yea, it's a big plugin. corpses don't disappear. they turn into backpacks and get ejected 10 meters outside of the dome. the location is also drawn on the users screen. this only happens when they could not loot it otherwise. so when the raid becomes locked and they can no longer enter. it does not happen otherwise that would be caused by another plugin. Eject Corpses From Enemy Raids (Advanced Users Only) you can disable it by setting this to false
-
ok will get it prepped then
-
lol no problem bud. im still recovering from a STEMI so I understand yea i'm no good at naming the options. they're long winded for sure, but they're meant to be self-explanatory so you don't have to look at the documentation repeatedly
-
i'm saying I added this option in next update as a better solution. then you can set the despawn after looting to 5-15 minutes and not worry about it not being enough time, because it will reset if players are still active in the base. @Swedish Chef
-
=p fyi
-
2.0.1 released- 583 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@Delco6467good catch. fixed in next update if (!attacker.IsHuman() && EventTerritory(attacker.transform.position) || attacker.userID == victim.userID) to if (EventTerritory(attacker.transform.position) && (!attacker.IsHuman() || attacker.userID == victim.userID)) @saintmichel13LOL well sure I can add this but I don't think it'd work too well for compounds
-
@Tabmorineits in the profiles, not the config
-
@Hakkaiserver saves during `restart` command. what is a dirty restart
