-
Posts
2,199 -
Joined
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Jbird
-
Any details about what was happening at the time this appeared?
-
This came up in the Discussion tab. If I understand what you want as far as it being linked, here is what we offered. The more details and explanation you give the better so I know what you mean by linked with. You can attempt this change in the CS file. Let me know if it works. weapon.primaryMagazine.capacity = (int)(weapon.primaryMagazine.definition.builtInSize * config.Scale); Change to weapon.primaryMagazine.capacity += (int)(weapon.primaryMagazine.definition.builtInSize * (config.Scale - 1));
-
Have you done much to customize the configuration? Would you try a fresh install for me? Make copies of the config file if you have customized it. But just to test. Reinstall the data files as well, not the images files but the other main data files for the plugin. Are you using oxide or carbon?
-
Okay please let me know if it happens again and any details you notice especially if there is an issue. I think it was a one time issue that you will not see again or at least not often.
-
How often are you seeing the first error? Seems to be related to the Bomber NPC. At a glance it looks like your settings for this NPC are default. When you shared the other error as well, was this something you were seeing along with the 1st error? It is for another plugin, perhaps the issue is related to both plugins, although I am at the moment unsure how. HitIcon is related to player damage output, unless it was something that only happened once or only happens rarely.
-
Do you know what damage is taking place when this error occurs? Where it is coming from and what is taking damage?
-
Fair enough @DocNorris. It was always my impression that anything that works on oxide would work on carbon but I've seen many instances where this has not been the case. Will get with KpucTaJl and see how easy and quickly we can resolve it. Thank you.
-
I am so sorry, I swore I replied to this. Still an issue for your servers I presume? When I tested last on one of my servers and on the test server I had no issue. I will run it again as soon as I get a chance just to confirm again but when I tested this back when I last replied I had no issues in either place. Do you have any plugins related to keycards or that provide the keycards being used?
-
Looking into this, will get back to you later today.
-
Did he give any actual information to support that claim? I'll run it past KpucTaJl today.
-
Make sure you are using the most recent version of RustEdit by checking their Discord. It's often in a beta version any more. Running the updater will only catch full release versions and we get stuck in beta a lot the past few years and have to do those updates manually. Most likely you're using the most recent stable version and need to grab the latest beta. Otherwise take a look at the Rust Edit dll. When you get to the page it explains how to install which is needed before launching the map, and how to check the version on your server. If you launch the map without RustEdit you'll need to wipe everything and relaunch the map.
-
Doors do not open after killing all npcs like set in settings
Jbird replied to SlayersRust's Support Request in Support
However many spawn points are listed for that NPC. So if there are 4 locations set for that NPC, then the max would be 4. -
NRE are generally a configuration issue. Did you make any changes to the config file(s) for the plugin? Seems to me that it might be regarding the loot for the NPCs, perhaps a change was made there that's causing an issue when an NPC dies? How often are you getting the error and what happens when it appears? This is referencing HitIcon which is a free uMod plugin.
-
Good, glad to hear that was confirmed, thank you for letting me know. Yes it is impossible to create a loot table that works for all servers. This is highly configurable in the config files for each base. You can simply multiply, or completely customize the loot tables here.
-
Why dont the npc's move and attack
Jbird replied to Forbidden Lands Rust's Support Request in Support
Generally this type of thing is either a performance issue, interaction with another plugin, or something within configuration. But it can be different case by case. For anyone still having issues if you haven't found a resolution I do recommend jumping into the Discord and creating a ticket. I do most of the monitoring on the sites but KpucTaJl the developer is active in the Discord and will help with tickets when I am working, sleeping, or otherwise busy. I just started a new job and have been doing a lot of traveling lately and Discord is a bit easier for me to monitor when I'm mobile. -
Why dont the npc's move and attack
Jbird replied to Forbidden Lands Rust's Support Request in Support
Thank you for sharing the resolution for your case. Unfortunately I don't think this will be the fix for everyone, because even though some of the behavior is similar it is likely different causes with similar results. -
Any details you can share such as anything going on at the time in console would help me to tell you what to do. How did you go about adding the custom monument and spawn points and such? I would definitely consider starting that process over and making changes one at a time, trying to repeat anything you had done before but one step at a time to narrow down the cause. Generally what you are doing should not be a problem so I would need more details before I could give a good plan of action.
- 1 reply
-
- 1
-
-
Have you tried Death or their general chat even to see if anyone else has had a similar issue and knows the fix? I have a feeling it's something going on in carbon. What issues are you having with the plugin itself, like performance or any details you can think of. While you try to get an answer from them I'll bounce the details around with KpucTaJl to see what we can sort out on our end as well.
-
Thank you for the feedback! There must be something in common that throws that in console Anything that you guys can find that consistently throws the error might be helpful. But I do recommend some testing as well like unloading plugins and trying just what is essential to see if it still comes up.
-
Doors do not open after killing all npcs like set in settings
Jbird replied to SlayersRust's Support Request in Support
Security officers being sent to the GC point would be because you have too many set to spawn and there are not enough spawn points for them. So you may be killing all of the NPCs at the monument but players cannot get to the NPCs below the map. This is not a bug but a configuration issue. -
Added another reference to the note, it's still there. Most recent work on this plugin was to improve performance. Quite a few things in the works all at once but the note is still there and I added another reference with those notes for KpucTaJl.
-
Yes it will be random as long as there are multiple locations available, and you have those options in the configuration still. If you have not removed any locations, and you have more than one of the monuments on the map you are running, just give us those details so we can look into it.
-
Why dont the npc's move and attack
Jbird replied to Forbidden Lands Rust's Support Request in Support
I appreciate the willingness to troubleshoot and the work testing it. My only concern about all those changes, mostly just as far as switching from oxide to carbon, is there are a few things to ensure you do when making the switch to avoid issues, same with switching back. Still we are more than happy to dig into it with you. Easiest sometimes in Discord if you're cool with that? Hop in the Mad Mapper Discord, create a ticket, and tag KpucTaJl and myself in a ticket if you would. Sounds like you have checked all kinds of shit so we might start with some of the basics and just go through it all until we can find a culprit and resolution. -
It works with all of the events, but what are you having issues with? Need details on both, like what is not working and we can start to dig into it.