-
Posts
3,299 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Steenamaroo
-
MissingMethodException: .LootSpawn.SpawnIntoContainer
Steenamaroo replied to lystor's Support Request in Support
Hi, I don't think that one's a me problem. SpawnIntoContainer is a vanilla method. Any chance you've got mismatched oxide+server versions, or something like that? -
BotReSpawn remembers all your monument settings even if the monument doesn't exist, so that you don't have to set it all up again next time you run a map with that monument on it., It'll show those missing monuments in your bots.count output, but it'll just say 0/0 spawned like pookins output, [BotReSpawn] Ranch 0 - 0/0 [BotReSpawn] Train Tunnel 0 - 0/0 I should probably have some way of indicating 'not present' in the UI. Either way, it's extremely unlikely to be related to that because BotReSpawn goes through all the monuments which exist on the map and then runs spawners for those. @pookins- Your data looks super helpful. No custom monuments or event profiles enabled narrows things down. I'm going to put together a debug plugin (or BotReSpawn mod) that logs to file the profile and precise location and timestamp for every NPC that gets spawned, and also logs timestamps for when the error is thrown. Would either of you be willing to run that so I can capture some data? Thanks folks.
-
Ok, seems like it's definitely a BotReSpawn issue then. Thank you. There's a decent chance it's coming from one of the events, like airdrop or hackable crates or something. I'll keep observing and see what I can find.
-
Ooh, it's mega spamming. Ok. I know it's a bit of a pain but it'd probably be worth it. When the spam is going steady like that could you just unload BotReSpawn? It destroys all of its npcs so if the spamming stops immediately, it was a BotReSpawn npc. If it doesn't, it was something else.
-
I'm talking about the server log file that's enabled by adding RustDedicated.exe etc etc ...-logfile "somefile.txt" to your startup .bat file. The events preceding the errors may give some clues, though, so the whole file would be ideal.
-
Nah, that's covered. BotReSpawn only initialises profiles for monuments which exist on the current map. The same goes for custom profiles where the Parent_Monument doesn't exist...They are skipped over. Would you be able to send me a copy of your server log containing an episode where this happened? I might be able to get some clues from it.
-
Up and running with a 250 day time and 335 night time npc complement. Not seeing any issues so far but I'll keep an eye on it. If it's since the last Rust update rather than the last BotReSpawn update, there's every chance its vanilla npcs or animals. Was there anything in particular made you think it's BotReSpawn? I mean, it could be...just wondering.
-
Thank you. I'm firing up your map now to investigate.
-
Hi, Is this since the last Rust update or since the latest BotReSpawn update? Are you aware of any missing npcs, looking at bots.count? If you're on proc gen, would you be willing to send me your size+seed, and contents of BotReSpawn /oxide/data folder? Finally, do you have server log to file enabled? If so can you look in there to see if there's more detailed information? I think usually there is for that particular message.
-
My pleasure. Thank you!
-
Hi, Thanks for flagging this. I'll be releasing a patch update very shortly.
-
No problem.
-
The only thing I can really think of is that the APC is firing at vanilla npcs, not BotReSpawn, or that you have multiple BotReSpawn profiles in that area, so there are others you need to set AI_Weapons_Safe true for.
-
Is it a vanilla APC or spawned/controlled by some plugin?
-
Oh sorry, you're quite right. It's still wrong in the public version. Noted and fixed for future updates.
-
It's a true/false option in every profile. You'll see it under the 'Other' tab.
-
That file looks fine, as you thought. The error points to `Invalid character after parsing property name. Expected ':' but got: ,. Path 'clan', line 29, position 13.` That makes sense to me because line 29 it's right before 'losttitle' which, in older versions of PlayerRanks, had the variables backwards. "clan": "Clan", "tooktitle": "{0} has taken the title {1}.", "losttitle": "You have lost the title {0} to {1}.", 'losttitle', is the one that is wrong in most people's lang files, so perhaps someone tried to fix that at some point? Now that your file is working fine the fix for incorrect var placement would be to swap 0 + 1 in "losttitle" like this "clan": "Clan", "tooktitle": "{0} has taken the title {1}.", "losttitle": "You have lost the title {1} to {0}.", I have fixed this in PlayerRanks plugin but lang files don't automatically update changes for already existing entries, leaving users to fix it manually. Alternative, if your lang file is totally unmodified, you could just delete it then reload the plugin. PlayerRanks will create a brand new file with the correction already in it.
-
Do you still have it in your recycle bin or a backup? If so PM it to me. The error was definitely with reading the lang file so at some point it got modified or damaged.