MooDDang
-
Posts
84 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by MooDDang
-
oh god... this plugin need to PopUp API?? shit i don't know that sry -
76561198119814349 ã„´ this man is cant open quarry and cant remove quarry
-
all works fine but Some people can't remove quarry. The cause is unknown. I also press the trash can and the quarry is not removed. But someone can erased. I am attaching the data file. please check. quarryData.json
-
Oh, there's an oxide update. This might solve it. And now, in a small furnace, you can't melt the crude oil. If there is a continuous problem after the oxide update, I will report it.
-
Why are there so many problems? This is an error in which the virtual query does not work even when work is pressed.
-
Users complain that "you are doing that too open" is continuously output. The above phrase is printed by pressing once without pressing it frequently. And there are problems like screenshots. The low grade ful does not come out even if the crude.oil is burned by fire in the refinery.
-
Hi, pressing the trash can doesn't delete the quarry. What should I do?
-
Allow Raid Bases On Building Topology (true) - Specifically added for custom map makers oh sorry i just saw this -
vex, by any chance, what is the topology for which Bases is not created? https://wiki.facepunch.com/rust/Topology Since it's a custom map, in this wipe I'm going to add a topology to the map. 😄
-
Thank you very much! XD
-
Nivex, I know you're busy with other things. But in the way you suggested, If you limit where the base becomes spawn, i have to do like this screenshot. This is very inefficient... You have to do the same thing every time you use the server's wipe. I would appreciate it if you could add something to prevent spawn. like a1 b2. I know you're busy, but I really need the above patch.
-
That's a great way I hadn't thought of! But it's a temporary measure. I wish the plugin could add coordinates such as z20 to prevent summoning. Looking forward to future updates. Thank you for answer.
-
How can I prevent bases from spawning in unwanted locations? if you can, I would like to allow the use of zonemanager or prevent summoning using coordinates such as z10, a11, etc.
-
thanks for the reply I checked, my server's nav_wait is already true -
Hello, I'm back. Still I want to talk about the problem of custom spawn points not working properly, which we talked about earlier. However, if you do "Reload profile", it spawns normally. So if it is difficult to make it always spawn normally, Please add a command like "botrespawn 'profile name' reload". I want to auto-enter this command every time the server is restarted.
-
Thank you very much. If we encounter any problems, I will report the bug in as much detail as possible. Thanks for the quick fix and interest as always XD
-
Thank you for quick response! I am not good at English, so I will write a little more about my current situation. There are several custom hunting grounds on my server. NPCs are summoned in quite a few places (about 400-500 npc) And about 200npc has spawn points specified. I was specified the exact same XYZ axis as like before was used at BotSpawn, But sometimes it spawns properly, sometimes it doesn't. like you said, It would be nice to add be able to check if the location is a valid location!
-
Hello. The amount of bots in the my config is 36, which is the same as the number of spawns. My server has 200 plugins, so it may be a conflict. But some spawn regions work fine, As shown in the screenshot above, there is a problem that the npc is not spawned properly. This is a problem that has been going on since last month, I was hoping an update would fix it, but the problem persists. Can you possibly fix this?
-
Works great with no problems!- 15 comments
-
- 1
-
-
- #querry
- #miningquerry
- (and 3 more)
-
This zip is my data file BotReSpawn.zip
-
Oh, I'm really sorry. You attached the botspawn, not the botrespawn. That config file outputs an error powerful enough to kick the user when summoning an npc at night, like the following quote:
-
It prints an error so i was set it to false. and i use it normally set this true . Thank you for your interest. I am attaching my config file. However, there doesn't seem to be a problem with the settings themselves. I think this has to do with the restrictions on morning and night summons. and just in case... my server uses CUSTOM MAP. will this be a problem? BotSpawn.zip
-
"Biomes": { "BiomeArid": { "type": 2, "Spawn": { "AutoSpawn": false, "BotNames": [ "코볼트 êµ°ì¸" ], "BotNamePrefix": "사막부대", "Keep_Default_Loadout": false, "Kit": [ "사막코볼트" ], "Day_Time_Spawn_Amount": 0, "Night_Time_Spawn_Amount": 60, "Announce_Spawn": false, "Announcement_Text": "", "BotHealth": 400, "Stationary": false, "UseCustomSpawns": false, "ChangeCustomSpawnOnDeath": false }, "Behaviour": { "Roam_Range": 200, "Aggro_Range": 20, "DeAggro_Range": 90, "Peace_Keeper": true, "Bot_Accuracy_Percent": 90, "Bot_Damage_Percent": 130, "Running_Speed_Booster": 0, "AlwaysUseLights": true }, "Death": { "Spawn_Hackable_Death_Crate_Percent": 0, "Death_Crate_CustomLoot_Profile": "", "Death_Crate_LockDuration": 10, "Corpse_Duration": 15, "Weapon_Drop_Percent": 0, "Min_Weapon_Drop_Condition_Percent": 50, "Max_Weapon_Drop_Condition_Percent": 100, "Wipe_Belt_Percent": 0, "Wipe_Clothing_Percent": 100, "Allow_Rust_Loot_Percent": 100, "Respawn_Timer": 5, "RustRewardsValue": 0.0 }, "Other": { "Chute": false, "Suicide_Timer": 5, "Die_Instantly_From_Headshot": false, "Instant_Death_From_Headshot_Allowed_Weapons": [], "Disable_Radio": true } }, Thanks for the reply, this is my setup for spawn npc at night.
-
Oh, I keep getting error reports. this is "Day_Time_Spawn_Amount": 0, "Night_Time_Spawn_Amount": 60, It happens in the config I set like this: It prints an error at night and sometimes kicks the user for this error. Also, at night, npc's do not use lights. alwaysuselights : Do not use lights even when in the true state. Is this a problem with my configuration? Or is it a bug?
