-
Posts
2,189 -
Joined
-
Last visited
-
Days Won
17
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by ZEODE
-
Changed Status from Pending to Fixed Changed Fixed In to Next Version
-
I found a bug which might cause this, it will be fixed in next update. If you want the fixed version before release to test hit me up on Discord.- 315 comments
-
- 1
-
-
- #bradley
- #bradleyapc
- (and 14 more)
-
Fixed in the next version, but it might not be out for a little while. If you are interested in having the updated version before I release the official update, hit me up on my Discord.
-
Changed Status from Work in Progress to Fixed
-
Any luck?
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Not a Bug
-
Changed Status from Pending to Work in Progress Changed Fixed In to Next Version
-
Hi, thanks for the report, you're AI report is not entirely accurate. For starters, my plugin is not responsible for spawning Bradley crates, it merely sets the number of crates to spawn when it dies. The native Rust code spawns the crates. You are correct, the crates are somehow falling below the map. This is happening depending on where the Bradley is spawned and the terrain around it. Native Rust Bradley only spawns in Launch Site, which is flat terrain. When the Bradley dies the crates spawn without issue on the flat ground. You are not alone in seeing this happen, although it always used to be rare. In a future update I will take over the spawning of crates so that this cannot happen. It wont be out for a little while, but will be ASAP>
-
I’m not familiar with Skills 2.0, but all you need is to be able to grant users the permission for each tier. if there is an issue with Skills doing this, you will have to take it up with the author of that plugin as I have no idea how it works.
-
Changed Status from Pending to Work in Progress Changed Fixed In to Next Version
-
Thanks for the report, I think I can see the issue and it can be easily fixed. I will work it into the next update.
-
Open a support thread in the correct support section and we can troubleshoot, start by uploading your config file in the new thread please. -
Have you created the profile for it in the config?
-
Hi, yes the first issue is already resolved and will be fixed in the next update. The warning message is harmless and can be ignored. The second issue "Failed to create agent because it is not close enough to the NavMesh" is not related to HeliSignals or the Patrol Helicopter at all, it is related to a walking NPC, most probably a scientist. This error is common where there are custom monuments with NavMesh errors or missing NavMesh. Especially is you use BotReSpawn where it can spawn and allow NPC to move where they wouldn't normally.
-
Changed Status from Pending to Closed
-
Changed Status from Pending to No Response
-
Changed Status from Pending to No Response
-
Changed Status from Pending to Work in Progress Changed Fixed In to Next Version
-
I could yeah, I will look at adding it as an option soon.
-
Apologies, I forgot to mention it in the changelog. have updated it now. It does compile and will probably be OK before force update, but I haven't tested, so my advice is to wait until after the update.
- 315 comments
-
- 1
-
-
- #bradley
- #bradleyapc
- (and 14 more)
-
What happens when you have that config value set to false?
-
That sounds like the way most would do it and how I would yes, using ExtraLoot is the best way to ensure they get those items. The chance system in the normal loot table handles the rest.
-
Changed Status from Pending to Fixed Changed Fixed In to Next Version
-
I think I see what is happening., for starters you have this set to false "Only Allow Event Owner/Team to Attack Deployed NPCs": false, So this should mean anyone can hurt/kill the NPC. But because my plugin assigned them an OwnerID, I assume one of your other plugins, such as LootDefender maybe, or another similar PvE plugin that prevents other players interacting/damaging owned entities, in this case the NPCs. I will release a fix to address this shortly. As an FYI, if you only want the owner and team to kill the NPC, you should change this to true, after the fix: "Only Allow Event Owner/Team to Attack Deployed NPCs": true,
