Steenamaroo
-
Posts
3,473 -
Joined
-
Last visited
-
Days Won
203
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Steenamaroo
-
Bots do not shoot when in melee range
Steenamaroo replied to KingSizeKevin's Support Request in Support
Hi, Testing on my current version there's no issue, but I've made a huge number of changes since V1.0.6 which most likely fixed it. I'll DM you about testing/confirming, since you're already on a prerelease copy...An older one. -
Feel free to ping me in discord man. You're on a pre-release copy ^^.
-
@BetterDeadThanZedtested and tells me that checking the crate for parent (even with a delay) didn't work. The proper solutions are either A: For me to provide make a call so other plugins can opt out, which I've done or B: For other plugins to make a call or provide API so their spawned crates can be identified. I don't really care which option gets used but the first one is available and working already. If someone refuses to use it, I think it would make sense for them to provide a solid alternative.
-
Hi, PermissionsManager never offered this, but you can create new groups with oxide's command oxide.group add SomeNameHere
-
Hi, If they're not spawning at the points you designated then most likely there is no navmesh at those points. The only workarounds are either to put them somewhere else, or make them stationary. In the next update there's a button (and bindable command) to sample and tell you if there's navmesh at your location, to make it easier when creating spawnpoints, and when you use 'Show spawnpoints' button, any without navmesh are show red instead of green.
-
Hi, Maybe new sign types in game? This is the first I'm hearing of this error, but I'll take a look and get it figured out. Thanks,
-
That's a cool idea! Sure, I can't see it being a problem. The next update has quite a few ignore/defend/attack options so that addition would fit right in. -
Hi, The present data set wouldn't allow for that but I could add an additional category called PVPDeaths to facilitate it. I think a lot of people weren't bothered because quite often in PVP you die to fire, explosion, turrets, falling, bleeding, where technically the 'attacker' isn't another player, but if you think it'd be a valuable or popular option to have I can add it.- 424 comments
-
- 2
-
-
- #statistics
- #leaderboard
- (and 12 more)
-
Safe to ignore until next update @Deadpool Thanks for reporting.
-
Hi @Rubiks-Q-Bert Yes, the murderer 'huff' should be a true/false option per profile in the next update. Lots of great changes and updates on the way.
-
@Razor14150- Just let an npc shoot at me (naked) doing 4-5 damage each shot, then kitted out with heavy armour and it was 2-3 damage per shot. That might be as a result of the changes in prerelease, which you now have... Might be worth checking, if you're willing.
-
Is that definitely true, @Razor14150? If it is, I'm pretty sure I can sort it out. @Rezanow- I don't believe they do headshots.
-
I can add a parent check, sure. Not really worth getting worked up about.
-
Hi, I think that would be possible although it may result in other people not getting npcs in cirumstances where they want them to spawn. I do have a hook there - OnBotReSpawnCrateDropped. If the dev of your event plugin is willing, they could use that to prevent BotReSpawn deploying npcs to crates from that plugin.
-
They shouldn't if the PVE_Safe option is set to true.
-
Timers are in minutes so your 1800 setting would be keeping them alive for over a day. Set it to 30 and that should solve the problem.
-
There's already a command there although it's behind a player haspermission/isadmin check. I could make that work from console, for sure, if it's useful.
-
To be honest that's probably easier ^. I'll take a look at that fairly soon. Thanks!
-
Must have missed this, way back when. There's no option at present to have multiple complete databases, but you can take leaderboard snapshots, which save the #1 player for each category. This is really only useful via SQL or manual file reference, as it's not viewable in UI. In future maybe I could save historical copies, at wipe, and allow admin to view that via UI.
-
@[email protected] You can 100% ignore this until the next version. It's of no consequence at all, but thank you for reporting it.
-
Both are fixed at my end. The fix will be in the next public updates for BotReSpawn and RustRewards. The error's inconsequential, apart from taking up space in your console, so you can safely ignore until then.
-
@pookins- You're quite right. The locked crate duration is in minutes.
-
The reply you've quoted was to someone else, with a different issue. You're having trouble getting airdrop npcs to spawn? Open the UI and go to default profiles > airdrop, Then make sure that AutoSpawn is set to true and that day + night spawn amounts are greater than zero, then click to reload the profile. Once that's done npcs should spawn at your server-called airdrops, as long as the crate falls on suitable terrain. If, for example, the crate fell at sea or on an oilrig or something, the npcs wouldn't spawn, but anywhere on open terrain should be fine. Whether or not they spawn for player-called supply drops (using supply grenade) is governed by the global setting - Supply_Enabled.
-
Yup, same issue - same fix. Thanks @BetterDeadThanZed Glad this was something so simple, because i've looked at these a few times and not seen the problem. Good to get them all sorted.
-
Yup, that's exactly what it is. The error's coming from BotReSpawn's call to give a reward for killing an npc from a specific profile. It's trying to give the reward to an npc, and the error is coming from trying to look up that npc's notification preferences which, of course, it doesn't have. Easy fix - It'll be included in the next BotReSpawn update. Thanks for the additional info - That was really helpful!
