-
Posts
1,860 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by IIIaKa
-
Changed Status from Pending to Work in Progress
-
In the database, select the table 'db_servers', then go to the structure of that table, and for the field 'ServerHeader', increase the length of varchar(2048 would work), or change the type to TEXT.
-
@JohnWick Hi, it is recommended to create separate threads for different issues to avoid confusion. From the error message, it is clear that the length of the ServerHeader field(link to the header image) exceeds the size of the ServerHeader field in the database. To resolve the issue, you need to either remove the length constraint(by default 64 characters) or increase it(2048 should be sufficient).
-
Changed Status from Pending to Work in Progress
-
@SlayersRust Try downloading the plugin again.
-
Changed Status from Pending to Work in Progress
-
If the issue persists, feel free to report it in this thread.
-
Changed Status from Pending to Not a Bug
-
You should use /twig warn
-
Hi, how exactly are you trying to disable the warning? Please provide the full command.
-
Hi, thanks for the suggestion! But I believe one time is not enough, as the player might miss this warning, not all players are attentive(especially PvE players). Adding a separate UI for this purpose is not practical. Not everyone finds this message annoying, and those who do, can turn it off with a command, but they will still 100% remember that twig decays and can't be repaired. This plugin is only relevant for PvE servers. And I’m sure that 99% of PvE servers have something like an info menu with server information and a list of commands, where you can also add information about TwigsDecay and how to disable the warnings.
-
Hello! Thank you for the suggestion. Unfortunately, adding this functionality to the current plugin isn't possible, as it is specifically designed for the forced decay of building blocks with twig upgrades. But I will definitely consider your suggestion for a separate plugin. I can't give a precise answer at the moment, as it will depend on the attempt to create it.
-
If the issue persists, feel free to report it in this thread.
-
Changed Status from Work in Progress to Not a Bug
-
- 67 comments
-
- 1
-
-
- #rust
- #industrial
- (and 25 more)
-
@Kobani Hello, you forgot to specify the chat command at the beginning. It should be /wipe bar 'wipe' is the main command, which can be changed in the config file (the first property).
-
Changed Status from Pending to Work in Progress
-
@anisb3l Most likely, when uninstalling the ZoneManagerAutoZone plugin, it does not remove the created zones. You need to unload (o.unload) the ZoneManager plugin. Then, either delete the file *SERVER*\oxide\data\ZoneManager\zone_data.json (which will remove all zones) or manually delete the lines related to monuments using any text editor. Then reload ZoneManager (o.load ZoneManager).