All Activity

No, but I don't think there's a need to fix this problem, so it's solved

same reports from the players here, some boxes turn up empty after yesterdays updates.

At the bottom layer, there are two password generation settings. Probabilistic occurrences do not generate passwords. You can conduct tests to obtain data. Usually 10 times, you may encounter this problem.

there is nothing in the config file to do with the output piles as well i have had multiple people tell me the same thing so i dont run this event anymore

Same issue here The raid protection is working, but the plugin no longer displays public messages. Messages still appear when you enter the admin command to check status. So it's like hitting an entity doesn't trigger the chat message anymore

https://codefling.com/files/support/26227-will-this-nre-also-be-fixed-in-the-next-update/ Thank you for the reply. Here it is! Thank you in advance.

Changed Status from Pending to Closed

Hey! You can just increase it: "Minimum time between events(in seconds)": 3600, "Maximum time between events(in seconds)": 7200,

Thanks, I'll test it. I didn't quite understand you about the bottom layer, could you please clarify?

hi , how can i reduce the auto time start amount on the plug in ?

I don't understand how categories work exactly. I put an M2 and ammo together in a single category, yet the M2 spawns without the ammo.

Is the limit 6? Because after 6 you can't see the button anymore.

So as you see in my config I have a 300 second cooldown. First use works fine as intended, then even if I wait 300 seconds or more then I die it gives me a 300 second cooldown in the death screen to use it again no matter if I haven't used the DeathModifier respawn button in a long time. Shouldn't the 300 second cooldown only be from your previous usage of the DeathModifier respawn option not every single time after you die? It basically makes me wait 300 seconds every time I die before I can click the respawn option after death. The cooldown should only be applied from the last usage of the DeathModifier respawn button option not be applied every single death to make players wait 300 seconds in the deathscreen to respawn. Hope this makes sense! DeathModifier.json

@Angry Dragon Gaming Hello, I apologize for the strange sequence of messages and the long wait, it may be related to the GasStationEvent, if the event is running, then betternpcs are removed from all gas stations, in the next update NpcSpawn and BetterNpc this will be fixed.

Because it kept generating passwords but failed, I deleted the connection. You can connect and test it to understand. Additionally, the bottom layer has two passwords that are connected, which may result in a probability of password generation failure. You can test 10 times and should encounter 1-2 failures.

Miss. sorry

@stev61 Hello, I apologize for the strange sequence of messages and the long wait, do you still have this problem? This means that somewhere there is an NPC who should be moving, but he is standing still, because he does not have a Nav Mesh, as a rule, this is due to the wrong Grid* type in the preset data files or incorrect spawn coordinates in them. most likely, you have had these messages for a long time, in order to save your time, I can advise you to wait for the update NpcSpawn and BetterNpc, the new version will have tools to find these problems.

Hey, its me again. Found another very annoying issue. "Auto Kits": [ "autokit_default" ], this currently just defines which kits are autokits - duh. all kits listed here, are given automatically during spawn regardless of kit permissions specifically. this however disables us to have different autokits per user/rank (permission). id instead suggest an approach as following: ----- oxide group example ----- default: kits.autokit,default (...) donator: kits.donatorautokit (...) ------- ------ config example -------- "Auto Kits": [ // "autokit_example_name" : "kits.<permission>", "autokit_default" : "kits.autokit.default", <----- Will be reffering to this as autokit 1 or 1 further on as its the 1st place in the array "autokit_jackhammer" : "kits.whateveridlikeofcourse", <--- Will be reffering to this as autokit 2 or 2 further on as its the 2nd place in the array. "autokit_donator" : "kits.donatorautokit" <----- Will be reffering to this as autokit 3 or 4 further on as its the 3rd place in the array ], now with this config, its clear what a user like me would be assuming to be doing. giving different autokits per permission. a user in the default group would spawn with A whereas a donator would spawn with D. however, in the current version of the plugin the donator would spawn with both, A and D as there is no configuration option to only give a player the highest array entry. additionally, users may want to merge different autokits. if we assume autokit 1 and autokit 3 are full spawn kits and autokit 2 is only a jackhammer for someone who wouldve bought/unlocked this perk somehow, youd end up giving a donator only the jackhammer instead of the full kit or vice versa, if the jackhammer would be further down in the array. hence id suggest a per-kit config value which lets configurators either have an autokit overwrite all prior autokits a user may have access to or to add onto the autokit(s) a user may have access to (the way it works right now at the moment). this is the quickest and cleanest solution i could think of though its 3AM and i surely am not anywhere as experienced as a coder as you are. if you find a better solution to this issue, you'll surely implement it wisely. Thank you for your attention - hope to have a working change for this soon! PS.: after reinstalling the plugin on another server (copied it from my test server to production) and copypasting the data + config instead of migrating from umod kits and redoing everything from scratch again (duh), the offsets in the text boxes i reported earlier on were gone hence id assume this was a sideeffect of migrating.

@bazou52 Hello, I apologize for the strange sequence of messages and the long wait, do you still have this problem?

@jayinwww Hello, I apologize for the strange sequence of messages and the long wait, do you still have this problem?