nivex
-
Posts
5,322 -
Joined
-
Last visited
-
Days Won
185
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
TruePVE was updated to address an issue regarding this Raidable Bases will have more strict control over despawns in next update 2.7.7 which will hopefully be released this week
-
Question: Loot Tables and Duplicate Entries - Low Loot, Normal Loot, High Loot bases.
nivex replied to Jackelmyer's Support Request in Support
Changed Status from Pending to Closed -
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
let me know if this happens once the new version is released, 2.7.7 hopefully in a day or two
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Turrets and npcs shooting/targetting through walls and floors
nivex replied to tacman1981's Support Request in Support
Changed Status from Pending to Closed -
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
fixed in next update!
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
make sure you are using the config you attached here, and that you are using version 2.1.0
-
nope. perms are for converting, not for despawning
-
you should update truepve raidable bases isn't related event will end, then the base will despawn when that time expires ive tried this numerous times with automated and manually converted bases (/sab and /sar)
-
I just tried this with your config with Seconds Until Despawn After Looting at 5 and it despawns 5 seconds after TC is killed
-
attach your config
-
@AaronL there are bugs in the plugin that cause this, but fixing TruePVE had fixed one of them you said your server is PVP so it's still another plugin or a bug causing the issue I implemented some changes that should help in the next update if it's a bug -
@AaronL did you witness the issue occurring in real-time when the problem initially happened, or did you discover the issue later at a different time? what you are describing is a despawn issue which is very different from a spawn issue some failed which is probably another plugin, but I can look anyway
-
@AaronL that's not an error. what you described is called an issue errors are in the server console and logs.
