Twigs Decay 0.1.5

link to real pve plugin dosn´t work 

22 minutes ago, Kobani said:

link to real pve plugin dosn´t work 

Hi. Real PvE still pending approval.

I purchased the plugin but I have a major problem. Every time someone builds even while using /bgrade 1-4 wood/stone/armored they still receive the message with every single placed building block. You can see how this could be very annoying very quickly for anyone building for an extended period of time.

Is there a way to have a cooldown for this message and also block it from appearing when using /bgrade 1-4 ? 

At the moment this plugin is unusable until these things are implemented. 

A config option for On/Off for players would be handy as well like /twig off or /twig on. To turn on/off the notifications.

1 hour ago, SlayersRust said:

I purchased the plugin but I have a major problem. Every time someone builds even while using /bgrade 1-4 wood/stone/armored they still receive the message with every single placed building block. You can see how this could be very annoying very quickly for anyone building for an extended period of time.

Is there a way to have a cooldown for this message and also block it from appearing when using /bgrade 1-4 ? 

At the moment this plugin is unusable until these things are implemented. 

A config option for On/Off for players would be handy as well like /twig off or /twig on. To turn on/off the notifications.

Hello, you can set "Is it worth displaying a warning?": false,

16 hours ago, IIIaKa said:

Hello, you can set "Is it worth displaying a warning?": false,

I would like to display the warning but maybe just 1 time or once an hour or something a bit longer apart.

This is probably a silly question but one that I don't know the answer to.

We use decay.upkeep false for decay to be disabled. If I were to add this plugin, am I right in thinking that it would not work because decay.upkeep "false" is set or will it ignore that and decay twig?

5 minutes ago, Russ said:

This is probably a silly question but one that I don't know the answer to.

We use decay.upkeep false for decay to be disabled. If I were to add this plugin, am I right in thinking that it would not work because decay.upkeep "false" is set or will it ignore that and decay twig?

Hello! This plugin does not depend on any Convars.
If the plugin is installed, it will enable automatic decay for buildings of the Twigs grade. You can also set the decay time and damage.

Thanks for the quick reply.

I've set twig to decay for 3 days time, I'm guessing this won't work due to our daily restarts resetting the timer?

Also the update you released overwrites all config settings previously set when updating.

35 minutes ago, Russ said:

Thanks for the quick reply.

I've set twig to decay for 3 days time, I'm guessing this won't work due to our daily restarts resetting the timer?

Also the update you released overwrites all config settings previously set when updating.

1. You are welcome!
2. You need to set the timer so that it can activate. You can adjust the damage value as you like within the range of 0 to 10, inclusive.
   It doesn’t have to be an integer; you can specify non-integer values, such as 0.123456789.
   However, if you want to set a prolonged decay, the parameter responsible for disabling repair should be enabled.
3. This is done to avoid compilation errors. It is simply recommended to make a backup of your config file before updating.

I have a question about a plugin similar to this, but to make twig or wood have more upkeep/decay at a faster rate than normal.

I have only found that you can adjust upkeep based on the number of building blocks - not by grade type.
This plugin is the closest thing I have found for twig and could probably easily add wood and a higher upkeep.

I would be very interested if you could tweak this plugin to include wood and upkeep costs.

thanks!

On 3/28/2024 at 4:25 PM, SlayersRust said:

I purchased the plugin but I have a major problem. Every time someone builds even while using /bgrade 1-4 wood/stone/armored they still receive the message with every single placed building block. You can see how this could be very annoying very quickly for anyone building for an extended period of time.

Is there a way to have a cooldown for this message and also block it from appearing when using /bgrade 1-4 ? 

At the moment this plugin is unusable until these things are implemented. 

A config option for On/Off for players would be handy as well like /twig off or /twig on. To turn on/off the notifications.

I agree with that. @IIIaKa

First of all, hello 
1. it would be fantastic if you could give players the option to disable or enable this message themselves, for example with a command like /twig warning
It's quite annoying because players get annoyed when the message appears all the time. Because when it's on, it's annoying all the time, and when it's off, new players don't know about it and complain that their building is falling apart. Some players are bothered by it whether it's on or off, so it would be good if players could decide for themselves. At the moment the plugin only makes annoyed players. That's why a command is essential.

2. there is also a small plugin conflict. When players build with BuildTools from Mevent directly in a better material than Twig, the message still appears. Would it be possible for you to prevent this?

10 hours ago, Kobani said:

I agree with that. @IIIaKa

First of all, hello 
1. it would be fantastic if you could give players the option to disable or enable this message themselves, for example with a command like /twig warning
It's quite annoying because players get annoyed when the message appears all the time. Because when it's on, it's annoying all the time, and when it's off, new players don't know about it and complain that their building is falling apart. Some players are bothered by it whether it's on or off, so it would be good if players could decide for themselves. At the moment the plugin only makes annoyed players. That's why a command is essential.

2. there is also a small plugin conflict. When players build with BuildTools from Mevent directly in a better material than Twig, the message still appears. Would it be possible for you to prevent this?

Hello! Added the ability to individually enable or disable warnings. Also fixed warnings when auto-upgrade is enabled.

On 8/6/2024 at 1:01 PM, Rust Admin said:

I have a question about a plugin similar to this, but to make twig or wood have more upkeep/decay at a faster rate than normal.

I have only found that you can adjust upkeep based on the number of building blocks - not by grade type.
This plugin is the closest thing I have found for twig and could probably easily add wood and a higher upkeep.

I would be very interested if you could tweak this plugin to include wood and upkeep costs.

thanks!

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.

Would be nice if we could have the big red message only display once then never again when building twig. That way when a player starts building and is new to the server they get a warning for say 10 seconds in GUI then never again need to see it.

Is this possible? Thank you. Ive seen other plugins do one time warnings per play session like DeathEffects Plugin. @imthenewguydoes this when players first kill something being logged on are sent a warning. Maybe you can do the same where it sends one warning per play session? Maybe ImTheNewGuy can explain how to do it  Hes a great dev thank you for considering my request

I have the method check a list of player ids. If the list does not contain the player ID, it adds their ID and send them the message.

6 minutes ago, imthenewguy said:

I have the method check a list of player ids. If the list does not contain the player ID, it adds their ID and send them the message.

Thanks so much for your input! This would be great for twigs decay as its only really necessary to send the msg one time as a gui per logon for say 10 seconds

I find the implementation as it is now better I have included the command to deactivate in the message.
Because experience has shown that if a message only appears once, it is simply overlooked. 
Most players don't even read the welcome panel or the rules. 
But this message, as it is now, seems to be the first that everyone really reads. So far no one has complained that their Twig is falling apart. 
Good work @IIIaKa

5 hours ago, SlayersRust said:

Would be nice if we could have the big red message only display once then never again when building twig. That way when a player starts building and is new to the server they get a warning for say 10 seconds in GUI then never again need to see it.

Is this possible? Thank you. Ive seen other plugins do one time warnings per play session like DeathEffects Plugin. @imthenewguydoes this when players first kill something being logged on are sent a warning. Maybe you can do the same where it sends one warning per play session? Maybe ImTheNewGuy can explain how to do it  Hes a great dev thank you for considering my request

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.

@IIIaKa
Hello, first of all, thank you very much for your efforts and the first-class support. 

I have one last small request. It would be good if the message:
‘Repairing blocks with the Twigs type is prohibited’
is not deactivated. (Or that you can decide for yourself in the config which messages remain active).
Reason:
1. it's not annoying, because nobody is constantly hitt a wall unless they're sick. 
2. it has the advantage that if you try to repair a Twig brick, you will be reminded that Twig always decays.

If you don't want to change this, I would be grateful if you could send me a solution via PN that I might be able to change.
Thank you very much for your effort.

@IIIaKa
Could you increase the display time of the gametip or add it to the config so we can set the time ourselves? Please! So that you can finish reading hints with longer messages.

10 hours ago, Kobani said:

@IIIaKa
Could you increase the display time of the gametip or add it to the config so we can set the time ourselves? Please! So that you can finish reading hints with longer messages.

Hello. Unfortunately, this is not possible, as the in-game command showtoast is used for display. The time is fixed and cannot be changed.

11 hours ago, Kobani said:

@IIIaKa
Could you increase the display time of the gametip or add it to the config so we can set the time ourselves? Please! So that you can finish reading hints with longer messages.

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.

8 hours ago, IIIaKa said:

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.

To the previous post:
I know that instead of using
gametip.showtoast,
man,
gametip.showgametip and
gametip.hidegametip
can be used. 
I have seen this elsewhere. There, the gametips remain visible for much longer. 
But it's not absolutely necessary. The plugin is still great.

Anyway, thanks for the changes and for always endeavouring to do your customers justice. I will be sending you a donation soon. I think good support should be rewarded. Thank you very much for your help.

1 hour ago, Kobani said:

To the previous post:
I know that instead of using
gametip.showtoast,
man,
gametip.showgametip and
gametip.hidegametip
can be used. 
I have seen this elsewhere. There, the gametips remain visible for much longer. 
But it's not absolutely necessary. The plugin is still great.

Anyway, thanks for the changes and for always endeavouring to do your customers justice. I will be sending you a donation soon. I think good support should be rewarded. Thank you very much for your help.

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.

1 hour ago, IIIaKa said:

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.

That sounds logical, I hadn't even thought about it. Then everything is perfect Thank you very much