IIIaKa

Changed Status from Work in Progress to Not a Bug

@dustyhansen Replaced the file. In the future, you can add it yourself. There’s only one line. You need to add it after "public class Vanish : CovalencePlugin {". private bool IsInvisible2(BasePlayer player) => _hiddenPlayers.Contains(player.userID);

If the issue persists, feel free to report it in this thread.

Changed Status from Work in Progress to Closed Changed Fixed In to Next Version

If the issue persists, feel free to report it in this thread.

Changed Status from Work in Progress to Closed Changed Fixed In to Next Version

In the next update, I restored vanilla behavior for mailboxes.

Yes, it is version 1.8.9.

If the issue persists, feel free to report it in this thread.

Changed Status from Work in Progress to Not a Bug

Hello, replaced it.

Changed Status from Pending to Work in Progress

I just noticed that there's no option to simply top up the balance. Could this option be added? And after that, restrict direct purchases if a plugin costs less than ~$5?

Is it possible to set a commission limit of no more than approximately 30% of the price? This would be helpful for plugins that are low-priced. Or for renewal, for example, if a plugin costs hypothetically $10+, and the license renewal(symbolic support) will cost $1-2 each year. For example, if a plugin costs $1, the current commission would be 12% ($0.12) + $0.49 = $0.61, this is more than half of the price. If you add a check to ensure that the commission does not exceed approximately 30% of the plugin's price, then the commission for a plugin priced at $1 would be no more than $0.30, and this would not affect the commission for more expensive plugins. With the current settings(and 30%), the limit will activate up to a price of ~$2.72. Something like this: const double MaxCommission = 0.3d; double price = 1d; double commission = Math.Min((price * 0.12d) + 0.49d, price * MaxCommission);//In this case, it will be $0.30 instead of $0.61

If the issue persists, feel free to report it in this thread.

Changed Fixed In from 0.1.11 to Next Version

@Aelanna I have added the ability to set a default value for friendly fire in the config file in the next version. "PvP - Is friendly fire enabled by default when creating a team?"

If the issue persists, feel free to report it in this thread.

Changed Status from Work in Progress to Closed Changed Fixed In to Next Version

@Aelanna Hi. Do you just want the mailboxes to behave like in vanilla?

Changed Status from Pending to Work in Progress

If the issue persists, feel free to report it in this thread.

Changed Status from Work in Progress to Closed Changed Fixed In to Next Version

In the next update, a parameter has been added to the config: "Is it worth preventing resource gathering in someone else's building privilege area?", which controls the resource gathering in someone else's building privilege. By default, the restriction is turned off.

It would also be great to have the ability to pin messages in the discussion section on the plugin page.