ninco90
-
Posts
561 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by ninco90
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Players who are dead or stopped playing a long time ago are not recognized by the game itself. Also if you use a plugin that automatically shares cupboard permissions like DynamicCupShare this could also happen. It's not a plugin bug as such, just the name information "disappears" from the player list.
-
I think I've patched it, contact me privately and I'll send you the edited plugin so you can try it and confirm if your problem has been solved.
-
If you want to allow players to place any type of workbench, you should ideally set this to true: "Allow Place All Workbench": false, Also make sure you don't lock it as an item in any tier. Otherwise it won't let you put it on the player's belt.
-
How do you have the configuration for the workbench placement?
-
Changed Status from Pending to Closed
-
You can also block his crafting. But it cannot be removed from the game's crafting menu, since that is client-side. -
Checking your configuration file, you have set: "ID Item Default": 1, However, there is no item with "ID": 1, configured. You will have to modify the ID of an existing item or simply change "Default Item ID": To an existing ID. Example: "Default Item ID": 95, Maybe this is your problem, since the plugin tries to open the item by default but it does not exist.
-
Does the same thing happen when you try to open it with the chat command? /craft What do you have set in the config: ID Item Default ? Does the id established there really exist?
-
They have released an update to the server and oxide, can you confirm if once updated it continues to happen?
-
Hello! Not as such, it is preferable that you disable the container skin completely. We had to do it on my server for the same reason. This skin has so many details that it lowers the client's performance in large builds.
-
Don't you have any other plugins that could affect builds? Add me on discord and we'll see it with more details if you want. The reports I received about it were due to Building Skin, but with the patch I made it seemed to be solved. Maybe some kind of conflict will arise with another plugin.
-
Changed Status from Pending to Closed
-
New Update: I have had to disable the button that appears from being picked up. Because if you don't pick up the button with the hammer, it won't let you pick up the workbench.
-
Hello! When images appear like this it is because Image Library was unable to download the images correctly. I would recommend resetting the image library cache by running its cleanup command and then reloading the plugins that use Image Library to download images again, including BetterTC. This should solve it. -
Changed Status from Pending to Not a Bug
-
Changed Status from Pending to No Response
-
I seem to remember that if you put it to work and then continue increasing the base, the new constructions are not added to the queue of entities to improve. So yes, you will have to stop and restart the process. At the optimization level, it is preferable to do a stop/run manually before adding new entities to the base.
-
If you are also using BuildingSkins from umod, try this modification I made, it should solve it. You tell me! BuildingSkins.cs
