aimacak
-
Posts
1,148 -
Joined
-
Last visited
-
Days Won
8
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by aimacak
-
This is already a standard question about backups, so I wrote it automatically, besides, I do not know for what reason you did a clean install. Since, judging by the server logs, UpdaterBetterNpc is installed on your server, I can assume that you have a broken BetterNpc configuration, and possibly NpcSpawn. I would advise you to delete the configurations: NpcSpawn.json, NpcSpawn_old.json, BetterNpc.json and BetterNpc_old.json, delete data files: oxide/data/BetterNpc/, oxide/data/NpcSpawn/Preset/. After that, transfer the data files from the last version of NpcSpawn and BetterNpc archives, then upload NpcSpawn.cs, then upload BetterNpc, you don't need any Updaters for a clean install. -
Well.. This won't help you right now, although at first it may seem like everything is fine. Did you backup your files before starting the major update? configs NpcSpawn and BetterNpc, data files: oxide/data/BetterNpc
-
@lokisoteg Hmm, I'm sorry, it looks like these are the correct logs.
-
these are the logs of the oxide, not the server, look for the server logs, you can make sure that you have found the right file by searching for your error - IOException
-
send the full error information from the server logs file, and I'm also interested in the messages when NpcSpawn is reloaded (o.reload NpcSpawn)
-
Hello, I wrote to you, send a backup if you have configs NpcSpawn and BetterNpc, data files: oxide/data/BetterNpc
-
its broken, delete it and o.reload BetterNpc { "Start time of day": null, "Start time of night": null, "Use the plugin's PVE mode? (only if you use the PveMode plugin)": false, "Distance from the center of the safe zone to the nearest NPC spawn point [m]": 0.0, "List of NPC types that should not be deleted (can use class name, NPC name, SkinID, or ShortPrefabName)": null, "Run the debug.puzzlereset command when the plugin loads or reloads to refresh puzzles, IO, and NPCs at Facepunch monuments [true/false]": false, "Refresh NPCs and crates at monuments when the plugin loads or reloads? [true/false]": false, "Enable simplified loading logs in the server console? (intended for advanced users who want fewer loading messages) [true/false]": false, "Configuration version": { "Major": 2, "Minor": 1, "Patch": 5 } }
-
Send config please ( oxide/config/BetterNpc.json )
-
Are you sure you're using NPCs from BetterNpc on your Oil Rigs? I know that flying heavy NPCs appearing on CH47s with small Oil Rigs has been a common occurrence for a long time now, and it's not related to plugins.
-
Write o.reload NpcSpawn and show messages from console
-
If you have already tried to do clear install, here is a list of everything you need to do before trying again. If you have a backup and want to keep your old settings, create a ticket in the support section and attach all files related to NpcSpawn and BetterNpc, config and data. For a clean installation, delete the following files in the oxide/plugins folder: BetterNpc.cs, NpcSpawn.cs, UpdaterNpcSpawn.cs, UpdaterBetterNpc.cs, in the oxide/data folder: BetterNpc and BetterNpc_old, and in the config folder: NpcSpawn.json, NpcSpawn_old.json, BetterNpc.json and BetterNpc_old.json. Next, move the data folder from the archive with the NpcSpawn plugin, downloaded from codefling, to the oxide/ folder, confirm the replacement of files, then move the data folder from the archive with the BetterNpc plugin, downloaded from codefling, to the oxide/ folder, then move NpcSpawn.cs from the archive with NpcSpawn to the oxide/plugins folder. After successful loading, move BetterNpc.cs from the archive to the oxide/plugins folder, everything should work. If you move *.cs plugins to the oxide/plugins folder and they don't load automatically, you'll need to manually load the *.cs file after moving it using the o.load {PluginName} command.
-
Well, I can't say that right away. My experience with custom maps isn't great. I tried it a couple of times and was disappointed, perhaps for my own reasons. That's why I only talked about that error and the reason it appeared. Perhaps there are some other nuances... If you could give me a clear example of a map with these errors, especially if RustEdit was blamed for something, I'd be interested in tinkering with it
-
is this the right behavior? or do you mean that BetterNpc has retired?
-
Yes, but even on a Custom Map, the final reason is incorrect coordinates or the navmesh type at the NPC) You can use the game console to spawn NPCs anywhere on the map, for example, on the road, ( spawn scientistnpc_oilrig / spawn scientistnpc_patrol) and they will stand still and spam you in the console, my console hides these messages and I see them only in the log file itself
-
Can you add me to discord or create a ticket in mad mappers? @shrpndfcsd It would be much easier and faster for both of us, I don't insist.. UpdaterNpcSpawn and UpdaterBetterNpc are only needed to update to new versions of plugins, and if installed correctly, they delete themselves after performing all the actions for which they were created)
-
Hello, I've read your previous ticket a bit ( https://codefling.com/files/support/14120-console-spam/ ) and I can tell you for sure that the reason for the spam has been with you all this time, at least the current one. This may seem strange to you, but it is true, this spam causes a lot of simultaneously running events multiplied by the number of players on the server with advanced map marker, change the markers in all events to simple and make sure of this. About it from before ticket, if you interesting: Failed to create agent because it is not close enough to the NavMesh When an NPC wants to move, it uses NavMesh coordinates. If it can't find them, it tries endlessly, but fails, which is what causes the errors you mentioned. Typically, this is due to incorrect NPC coordinates or an incorrect NavMesh type, which can be specified in the preset file oxide/data/NpcSpawn/Preset/, previously, it was also specified for each preset, but they were located in oxide/data/BetterNpc/
-
You did a great job) Here are the new files for custom maps
-
Hello, this is most likely from the update plugin (UpdaterNpcSpawn.cs or UpdaterBetterNpc.cs), which for some reason is located in oxide/plugins/ if you have a backup of your files: configuration (oxide/config/): NpcSpawn.json, BetterNpc.json and data files (oxide/data/) BetterNpc, you can start updating again, or send me your backup, I'll try to do it for you. Also, you can add me to the discord for the real-time dialogue @shrpndfcsd
-
Hello, this is an error from the update plugin if you have a backup of your files: configuration (oxide/config/): NpcSpawn.json, BetterNpc.json and data files (oxide/data/) BetterNpc, you can delete UpdaterNpcSpawn.cs, UpdaterBetterNpc.cs, NpcSpawn.cs and BetterNpc.cs from the folder oxide/plugins on your server, download the files that I listed above and start updating again according to the instructions from the archive with the BetterNpc plugin Also, you can add me to the discord for the real-time dialogue @shrpndfcsd
-
hello, your logs indicate that BetterNpc loaded correctly, which means NpcSpawn is working for you, I also see a lot of errors from the Admin v1.8.0 plugin, if your NPCs are not working correctly, I would try to unloaded it for testing. Do Events work for you? You can send me thease files? oxide/config/NpcSpawn.json oxide/config/BetterNpc.json folder oxide/data/BetterNpc folder oxide/data/NpcSpawn/Preset Also, you can add me to the discord for the real-time dialogue @shrpndfcsd
-
do corpses disappear in any particular event or monument or on the entire server? -
Hello, try to check it with the latest version of NpcSpawn. -
This is the only timer associated with removing NPC corpses, and it removes a corpse after 0.2 seconds only if that NPC has the Remove Corpse On Death option enabled. The update note you pointed to says that this parameter (Remove Corpse On Death) has changed its default value for the new presets (it was true, it became false) that you create in NpcSpawn (/preset) and for all NPCs that are used in events that have not yet been updated. in compatibility mode, because The configuration of these events for these NPCs does not have all the parameters that are in /preset, and therefore they accept the default values of these parameters from the NpcSpawn plugin. timer.In(0.2f, () => { if (corpse.IsExists()) corpse.Kill(); });
-
Yes, you're right, unloading or reloading the NpcSpawn plugin naturally affects this, but you wrote after the update, in the current situation, I understood this as a transition from older versions of plugins to a major update. You can read the information for each update, and if you are not concerned about what was fixed in the last update, update when it is convenient for you, there is nothing wrong with that, you should not immediately ruin the entire server operation when the plugin is released, unless there are good reasons for it. I will discuss with the developer the point you mentioned, whether there is a way to make Bosses have a timer to appear if they have retired due to NpcSpawn's unload / reload, but in any case it will be like a future plugin improvement, this will not happen in the shortest possible time, so you can stick to my first advice.- 458 comments
-
- 1
-
-
- #abilities
- #boss
- (and 16 more)
-
Are all the other NPCs working correctly for you? Events? Does BetterNpc fill the monuments? If so, then no, maybe you changed something in the Bosses settings, or you just didn't wait for them to spawn?
