-
Posts
3,700 -
Joined
-
Last visited
-
Days Won
210
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Steenamaroo
-
@Kaj Van der Hallen - Hi again. I just checked and they're getting vanilla Rust loot just fine over here. I had a profile on Default NPC and it gave me some pistol bullets and stuff, then I changed to Beehive and it gave me honey so all looks good. Maybe you've got some other loot plugin wiping the loot for these npcs? If you're struggling to track it down it might be worth unloading any plugins that manage loot (whether they're meant to affect npcs or not), then testing again.
-
@Kaj Van der Hallen - Thanks for letting me know. I'll check very shortly and see what's going on. @MelodyZE - Hi, I'm not seeing an issue here. Have you used `bot.count` command in console to 100% confirm? It gives you the total number of spawned npcs. `bots.count`, with the 's', gives you a per-profile breakdown. Also type nav_wait into console and see what the result is. It should be true. If it's false it means navmesh gets created after the server boots up, which means there's no navmesh for npcs at startup and you'd need to reload the plugin X minutes later. @TwoShoes - You've got APC_Safe set to false for some profile that's near a Bradley. Doesn't necessarily have to be a Bradley even or Launch site profile. It could be airdrop or a biome or...any profile that's close enough to an APC.
-
Can you be more specific with plugins names and the exact nature of the problem? If there's something 'better' I can do to address it, I will. BotReSpawn doesn't really do anything until OnServerInitialized which, during server boot, is a long long time after all plugins are loaded, so load order shouldn't really matter? If you want to DM or get me on discord instead, go for it.
-
I agree with rejecting AI submissions. Codefling has always placed importance on our creators truly owning, and fully understanding, their work. This stance initially emerged due to how easy it is to take snippets of other people's work without permission but it should apply just the same, in my opinion, to 'AI' generated work. Understanding exactly how a work was created and how it works is essential when it comes to maintaining that work and troubleshooting potential issues with it. We've had exceptions in the past where we allowed submission of 'bought and paid for' works on the condition that any required maintenance would be handled by the original developer, essentially allowing 'the creator' to be a support middle-man. I think I'm correct in saying it doesn't work and we don't allow it anymore. Where paid assets are concerned it's a competitive environment. There are many ways to maintain an edge and be successful, such as how you handle support requests, how well tested your code is, how quickly you respond to wipe issues, your personality, etc, but whether you wrote and/or understand the code should not be in that list. That should be mandatory. If someone wants to use AI as a learning or development tool I'm all for it. Whatever works for you... but if any reviewer has any doubt at all that a submitting creator could recreate any given work 100% from scratch with no assistance, that work should be declined.
-
Is your issue that it wont hurt the npcs, or that it's targeting them? For the former, BotReSpawn doesn't control that. You've probably got some rules or settings in a PVE / PVP plugin which need tweaked. The latter - Feb 25th V1.3.6 (latest) update notes `Added per-profile Ai_Weapon_Safe. Replaces APC_Safe/Turret_Safe.` You'd need to set that to true. Note, there are identified collision issues with Ai_Weapon_Safe when set true so the next update will be removing it and adding PVE_Safe and Weapon_Trap_Safe but both will be per profile. It's a long story...
-
Hi @Tanki Something strange going on there. The trace refers to RustServerMetrics - A harmony patch called 'Delayed'. Sounds like maybe some other plugin or dll is managing timing of what RustRewards is doing? I mean, of course it's possible there's just a RustRewards bug to fix but I haven't seen that on any of the servers I have access to.