-
Posts
1,900 -
Joined
-
Last visited
-
Days Won
8
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by IIIaKa
-
@OhanaGamrGrl I didn’t quite understand what you’re referring to. What can’t be looted? And where?
-
@OhanaGamrGrl I didn’t quite understand. Are you saying that friends can damage each other? Is this only in monuments, PvP monuments or also outside of monuments? Also, it's possible that friendly fire is enabled in your team(/realpve team ff).
-
Center - Vector3 coordinates of the monument's center. CenterOffset - the offset from the Center. Sometimes the Center can be shifted from the actual center of the monument. Size - Defines the size of the cuboid formed by the offsets in each direction (x, y, z) from the center. For example, if you specify 50 for the height, it means 50 units up from the center and 50 units down, resulting in a total height of 100 units. The same applies to the other coordinates. Rotation - Rotation of the monument relative to the world. It's better not to touch the Center and Rotation parameters for vanilla monuments, as they are usually correctly calculated during the first initialization after a wipe. Using the example of boundaries for ferry_terminal_1 Default(for my map): "ferry_terminal_1": { "Center": { "x": 1181.49207, "y": 1.25, "z": -1610.2207 }, "CenterOffset": { "x": 4.0, "y": 12.0, "z": 18.0 }, "Size": { "x": 215.0, "y": 45.0, "z": 205.0 }, "Rotation": { "x": 0.0, "y": 184.830338, "z": 0.0 } } Modified: "ferry_terminal_1": { "Center": { "x": 1181.49207, "y": 1.25, "z": -1610.2207 }, "CenterOffset": { "x": 4.0, "y": 12.0, "z": 18.0 }, "Size": { "x": 250.0, <= Change in length "y": 60.0, <= Change in height "z": 250.0 <= Change in width }, "Rotation": { "x": 0.0, "y": 184.830338, "z": 0.0 } } In your case, it's enough to increase the values for x and z.
-
@OhanaGamrGrl Hello. Regarding monument boundaries, you can adjust the boundaries in the monument settings(*SERVER*\oxide\data\MonumentsWatcher\MonumentsBounds.json) within the MonumentsWatcher plugin. To see the boundary, you can use the command /monument show gas_station_1_4 or simply use it without specifying the monument name(you must be inside it) with /monument show
-
Changed Status from Pending to Work in Progress
-
Yes, I'm aware of them, but their drawback is that you'll need to monitor them additionally, as they don't delete themselves. For each such call, you'll need to check and create timers, which isn't very efficient in this case. -
Check screenshots 2 and 3. I've updated the default messages. You can delete the plugin, remove the old language files(preferably keep a copy, just in case), and install the new version. Then, based on my example, you can adjust it however you like.
-
Hello. Unfortunately, this is not possible, as the in-game command showtoast is used for display. The time is fixed and cannot be changed.
-
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.
-
Hello! Added the ability to individually enable or disable warnings. Also fixed warnings when auto-upgrade is enabled.
-
If the issue persists, feel free to report it in this thread.
-
Changed Status from Work in Progress to Not a Bug
-
Hello, we'll see, I can't promise anything for now. The primary item for the composter is dung.- 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
