aimacak
-
Posts
1,529 -
Joined
-
Last visited
-
Days Won
11
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by aimacak
-
It's a bit of a strange question, but is the weapon visible to all invisible NPCs? Have you checked if they are invisible to all players, or only to some? For example, if both screenshots with an invisible boss and screenshots with invisible NPCs were sent to you by the same player, it is possible that this player has problems with the client and he should try reinstalling the game, I heard about a situation where one player did not see Lightsight, and I was even shown a screenshot If they're invisible to everyone, and you're pretty sure of it, I guess it gets harder.. As the developer told me, making everything invisible is not so difficult, but making only the NPC texture invisible, but leaving the weapon visible is difficult)
-
Hello, remove this folders to oxide/data, not in Convoy folder
-
.thumb.png.b26373a73126c8e4a5a32ba1e2ae1d84.png)
Could you clarify what you mean? maybe a screenshot? -
I also have my own server and have been using NpcSpawn, BetterNpc and some events that use NpcSpawn for a long time, I have not seen such an error, so I assumed an error in recent changes. You can provide your configuration/data files, and I can help you with the search if you want.
-
has another developer fixed FerryTerminalEvent? It's great that it helped you, but this code was given to me by the author of FerryTerminalEvent, if it's not difficult for you, please check him too, if he fixes your problem with BotRespawn, then there will be an update on FerryTerminalEvent today, where this problem will be fixed for other users too. Thank you.
-
Hello, I sent a suggestion to the developer.- 194 comments
-
- 1
-
-
- #boat
- #facepunch
- (and 15 more)
-
Hello again, I can assume that you had the server convar enabled (server.pve true), and this is most likely fixed in version 1.1.2. I will also clarify if you have a PvE server, as a rule, this server convar is turned off (server.pve false), and regulates all possible rules and situations using plug-ins, for example TruePVE on Umod. -
Hello, do you still have problems with CH47? -
@PistOffBastd Hello again, unfortunately, this was originally specifically prohibited to prevent all possible situations that could lead to various bugs, etc -
Hello, I'm copying my message with solutions from a ticket with the same problem: It turns out that the reason has already been found by the developer with another user.. it's all about advanced map markers ( type 1), spam is affected by 2 parameters, the number of players on the server and the number of simultaneously running events with advanced map marker. There are only 2 solutions: 1) experiment with the number of simultaneously running events with this marker 2) use a simple marker (type 0) Check it for yourself and let me know, I think the spam will go away. "Marker configuration on the map": { "Use map marker? [true/false]": true, "Type (0 - simple, 1 - advanced)": 1, https://codefling.com/files/support/24387-main-thread-stalling-write-queue-at-capacity-waiting-for-write-thread/
-
It turns out that the reason has already been found by the developer with another user.. it's all about advanced map markers ( type 1), spam is affected by 2 parameters, the number of players on the server and the number of simultaneously running events with advanced map marker. There are only 2 solutions: 1) experiment with the number of simultaneously running events with this marker 2) use a simple marker (type 0) Check it for yourself and let me know, I think the spam will go away. "Marker configuration on the map": { "Use map marker? [true/false]": true, "Type (0 - simple, 1 - advanced)": 1,
-
Fixed in 1.1.2
-
.thumb.jpg.f61100ccc57656212ac059406e93854b.jpg)
Although this plugin was not very well received, I think that over time all the nuances will be corrected and by simplifying the creation of loot tables by developers and administrators, we will be able to receive new, more developed products more often, because developers will be able to direct the time saved in a more productive direction. I also find it difficult to accept something new in a coordinated manner, but I guess it's moving forward, not backward- 79 comments
-
- 6
-
-
-
- #loot
- #lootmanager
- (and 2 more)
-
Hello, this has been fixed in the NpcSpawn 2.8.4 plugin. I perfectly understand your reaction, but do not make such categorical conclusions, we are all human beings, thank you.
-
Hello, if the problem still persists, please create a topic in the Support section, provide the configuration of this plugin in it, preferably logs at the time when this happened (from the server logs file), and try to unload all plugins (in server console: o.unload all) and try to repeat this behavior. Can you also tell me what value you have set on the server convar 'server.pve', true or false?
-
Hello, check this with default cards, do not use cards from plug-ins such as Super Card in this test. Hello, check it out with all the disabled plugins that can affect turrets, such as TruePVE and other similar plugins. -
Hello, I added it for consideration.
-
Hello, I added it for consideration.
-
Hello, this will definitely be added to AnimalSpawn, I assume that there will be the same support here, too, since the event works in conjunction with AnimalSpawn. -
@Noel2997 Hello, yes, but you are specifying the name just for convenience, so that the item has improvements with Epic Loot, you need to specify for each improved item the SkinID of the same one that you use in Epic Loot. -
Hello, if the problem still exists, please create a ticket in the Support tab and provide your configuration of this plugin. -
Hello, I have submitted this for consideration. -
Hello, is the problem still there? -
Hello, is the problem still there?
-
Hello, please create a ticket in the Support tab and you can provide the configuration file in it. Regarding the errors with NavMesh, they only indicate that NPCs cannot move, and it can be any NPC on the map.