Minecraft Name: subxplorer Suggestion: Current Trade Chat rules state Messages in this channel must: Be no longer than 2 unique messages at a time. Must be no more often than once per 3 minutes. My suggestions are to: 1. Extend the minimum time trade ads can be repeated from 3 minutes to at least 5 minutes. 2. Add an additional rule that extends the "unique ad" and "frequency of the ad" rules to multiple players advertising the exact same (shop, casino, event, item etc.) at the same time. Reason: 1. With macros many players are running 2 unique adds constantly every 3 minutes causing trade chat to become very full. Due to this many players are leaving trade chat do to the "spam". Thus trade chat is not benefiting the economy or players the way it should. 2. Recently I have noticed that a certain player run casino will have 4-5 players advertising it all at the same time. Four players each advertising the same casino every three minutes in my opinion is spam and is unfair to other players on the server who want to utilize trade chat for their advertisements. The current rules of "uniqueness" and "frequency" should extend to multiple players advertising the exact same (shop, casino, event, item etc.) Other Information: Everything is stated above. Link to this plugin/Is this a custom addition?: Not Applicable
If you read my explanation you would understand that I am saying we can both advertise say an EFF7 for sale as long as it is not the same EFF7. In other words I cannot have three other players helping me advertise my EFF7 all at the same time as that would be abuse of the trade channel.
If you want to really block trade spam, it's very simple - Install the ClientPermissions plugin and block the ECHO command. This will get rid of the automated messages that require no effort at all and post even when users are AFK. If you want to advertise, you should be putting effort into your advertisements. As simple as that. Over-advertising often has tendencies to harm the business/user who does it themselves, so I'd say they're already getting punished by it. Anyway, that's only a minor part of the problem - The problem is constant trade spam caused by the MacroMod. I don't believe these are the right solutions to stop trade spam - I believe the problem lies with the MacroMod and so does the solution.
I understand what you are saying about the the ClientPermissions plugin. However that is simply blocking trade channel due to it being spammy and annoying, which is addressing the symptom and not the problem. I am not necessarily opposed to automated ads as long as they are more spread out and in in my opinion a simpler fix would just be to extend the frequency. I do agree that the main problem is with MacroMod, and it may be just as well if no automated advertising was allowed or at least allowed while players are afk. Perhaps we need to create another suggestion where a player would have to apply on the forums if they created a Macro for use with MacroMod so that staff could review and approve it.
Macromod is the sole reason trade chat is so spammy and annoying though. Sure, increasing the time to 5 minutes will reduce the problem, but removing that ability from macromod will completely fix it. (not that it's feasible to block anything macromod on ECC. It's already used too much)
Nono, it's quite the opposite. Spammy trade chat is the symptom, MacroMod being the problem. Perhaps increasing the amount of time per trade advertisements would lessen the problem, but disabling the ECHO command would fix it.
So based on what you are saying, you would be for increasing the number and frequency of messages? That would just make the current problem worse. Also keep in mind that as the number of players on the server grows than trade channel is just going to become more crowded, thus the reason something needs to be done now to limit the frequency of ads.
Okay I misunderstood what you were saying originally. To simply block automated messages from MacroMod then this would be a relatively easy fix. Maybe Jamie could comment on the feasibility or unforeseen issues of doing this. @JamieSinn
