Please clean up the RMT yell frenzy

[Sirmarki]

Unfortunately, I can't add anymore to my blist, as its capped at 100.
Can we have a /safelist option?

I just don't think all these yells are sending out a good message to people who are taking advantage of the return campaign.

We need a GM to remove all yells in relation to people selling Job Points.

Maybe keyword blockers would help?

[Isola]

Holy for seriously. This is artardiculous.

[Isola]

It is very much time for policy change. The current system(s) do not/does not work.

The spam filter (for tells only) needs to be applied to yell, shout and say. And/or there NEEDS to be a personal option or ability to opt-into keyword banning. If you refuse to solve the problem, at least let us choose a way to block it.

I understand that it IS actually quite impossible to stop them. I know this. They have actual unlimited accounts in which to abuse the system with. So. You NEED to fix the source. The yells. The words.

[TullemoreAsuraFFXI]

Completely agree, the game should allow /blist capacity of 500 minimum. Once /blist capacity has be increased to 500 or more, there should be provider side capabilities that detect massive /blist additions to quickly discover and investigate Terms of Service violations.

Other Beneficial upgrades that can be done:

Have /yell(lvl) communication and disable the universal /yell and add ability to filter each particular level bracket of /yell(lvl).
Example: /yell99 serves for only those who have obtained a lvl 99 job and have the filter set to allow.
Example: /yell90 serves for only those who have obtained a lvl 90 job and have the filter set to allow.
Example: /yell80 serves for only those who have obtained a lvl 80 job and have the filter set to allow.
Example: /yell75 serves for only those who have obtained a lvl 75 job and have the filter set to allow.
Example: /yell60 serves for only those who have obtained a lvl 60 job and have the filter set to allow.
Example: /yell40 serves for only those who have obtained a lvl 40 job and have the filter set to allow.
Example: /yell20 serves for only those who have obtained a lvl 20 job and have the filter set to allow.
Example: /yell10 serves for only those who have obtained a lvl 10 job and have the filter set to allow.
Example: /yell3 serves for only those who have obtained a lvl 3 job and have the filter set to allow.
Example: /yell0 serves for only those who have no job level above lvl 2 and have the filter set to allow.
After creating channels for /yell0, /yell3, /yell10, /yell20, /yell40, /yell60, /yell75, /yell80, /yell90, /yell99 allow the display and use of these channels both inside and outside of cities.
Interface the filter selection so that it is quickly convenient from the menu, preferably with it's own lead category as to not bury it three+ levels deep into the current chat configuration settings.
Create text commands to allow and disable each channel. Examples: /allowY99 /disableY99 /allowY40 /disableY40

Increase allowable Linkshell active capacity to 2000. Enhance the Linkshell search interface to allow for all character names equipped with a pearl to be shown without truncation.

Allow for Linkshells #3 and #4 to be equipped.

Allow for the Unity communications to have capacity of 4000 or more, so there is no more "The maximum number of people are already participating in Unity chat. Please try again later." Error messages.

Create communications channels based around the traditional /seacom categories. Can use /c or /w as a designation beginning.
Examples: /cExp /cBattle /cMission /cQuest /cItem /cLinkshell /cSocial /cOther

Upgrade + Enhance + Overhaul the /seacom interface to include instructions about usage, instructions about etiquette, and the ability to search for key words displayed in the /seacom entry of any character that is displaying a /seacom.

Allow a /seacom to be set for each individual category with a blank /seacom being designated as disabled for that category. In this way each player can enable and display a /seacom for Exp ~ Battles ~ Missions & Quests ~ Item ~ Linkshell ~ Looking for Friends ~ Others.

With the enhancement of the /seacom interface for quicker search results; create and allow for content tags to be attached to /seacom. Example: a /seacom applied to the Exp category could be tagged with a level range bracket selection and desired vana'diel area. Example: a /seacom applied to the Item category could be tagged with a item type selection, a crafting source selection, a battle content type selection, a level usage selection etc, a auction house inventory category selection.
Detailed Example: Utu grip could be entered with text into the display of a /seacom under the {Item} category and then be tagged with {Omen} {LVL99} {Battlefield} {Grip} {Reisenjima}
Detailed Example: Sublime sushi could be entered with text into the display of a /seacom under the {Item} category and then be tagged with {Cooking} {Food} {Synthesis} {Item} {Meals} {Seafood}.
Allow for up to seven tags to be attached to eash active /seacom.


For those who further wish to denounce RMT and give constructive recommendations and advice:

http://forum.square-enix.com/ffxi/th...ht=Scourge+RMT
http://forum.square-enix.com/ffxi/th...-WHERE-ARE-YOU

[TullemoreAsuraFFXI]

Completely agree, the game should allow /blist capacity of 500 minimum. Once /blist capacity has be increased to 500 or more, there should be provider side capabilities that detect massive /blist additions to quickly discover and investigate Terms of Service violations.

Other Beneficial upgrades that can be done:

Have /yell(lvl) communication and disable the universal /yell and add ability to filter each particular level bracket of /yell(lvl).
Example: /yell99 serves for only those who have obtained a lvl 99 job and have the filter set to allow.
Example: /yell90 serves for only those who have obtained a lvl 90 job and have the filter set to allow.
Example: /yell80 serves for only those who have obtained a lvl 80 job and have the filter set to allow.
Example: /yell75 serves for only those who have obtained a lvl 75 job and have the filter set to allow.
Example: /yell60 serves for only those who have obtained a lvl 60 job and have the filter set to allow.
Example: /yell40 serves for only those who have obtained a lvl 40 job and have the filter set to allow.
Example: /yell20 serves for only those who have obtained a lvl 20 job and have the filter set to allow.
Example: /yell10 serves for only those who have obtained a lvl 10 job and have the filter set to allow.
Example: /yell3 serves for only those who have obtained a lvl 3 job and have the filter set to allow.
Example: /yell0 serves for only those who have no job level above lvl 2 and have the filter set to allow.
After creating channels for /yell0, /yell3, /yell10, /yell20, /yell40, /yell60, /yell75, /yell80, /yell90, /yell99 allow the display and use of these channels both inside and outside of cities.
Interface the filter selection so that it is quickly convenient from the menu, preferably with it's own lead category as to not bury it three+ levels deep into the current chat configuration settings.
Create text commands to allow and disable each channel. Examples: /allowY99 /disableY99 /allowY40 /disableY40

Increase allowable Linkshell active capacity to 2000. Enhance the Linkshell search interface to allow for all character names equipped with a pearl to be shown without truncation.

Allow for Linkshells #3 and #4 to be equipped.

Allow for the Unity communications to have capacity of 4000 or more, so there is no more "The maximum number of people are already participating in Unity chat. Please try again later." Error messages.

Create communications channels based around the traditional /seacom categories. Can use /c or /w as a designation beginning.
Examples: /cExp /cBattle /cMission /cQuest /cItem /cLinkshell /cSocial /cOther

Upgrade + Enhance + Overhaul the /seacom interface to include instructions about usage, instructions about etiquette, and the ability to search for key words displayed in the /seacom entry of any character that is displaying a /seacom.

Allow a /seacom to be set for each individual category with a blank /seacom being designated as disabled for that category. In this way each player can enable and display a /seacom for Exp ~ Battles ~ Missions & Quests ~ Item ~ Linkshell ~ Looking for Friends ~ Others.

With the enhancement of the /seacom interface for quicker search results; create and allow for content tags to be attached to /seacom. Example: a /seacom applied to the Exp category could be tagged with a level range bracket selection and desired vana'diel area. Example: a /seacom applied to the Item category could be tagged with a item type selection, a crafting source selection, a battle content type selection, a level usage selection etc, a auction house inventory category selection.
Detailed Example: Utu grip could be entered with text into the display of a /seacom under the {Item} category and then be tagged with {Omen} {LVL99} {Battlefield} {Grip} {Reisenjima}
Detailed Example: Sublime sushi could be entered with text into the display of a /seacom under the {Item} category and then be tagged with {Cooking} {Food} {Synthesis} {Item} {Meals} {Seafood}.
Allow for up to seven tags to be attached to eash active /seacom.


For those who further wish to denounce RMT and give constructive recommendations and advice:

http://forum.square-enix.com/ffxi/th...ht=Scourge+RMT
http://forum.square-enix.com/ffxi/th...-WHERE-ARE-YOU

~ ~ ~ ~ ~ ~ ~

Attention: Square-Enix | Special Task Force | FFXI Development team : Is there any potential consideration for these proposals being implemented? The universal communication channel we're currently subject to [ /yell ] is advantageous and far too easily accessible for accounts that are polluting the communication there with RMT violations, advertisements for exploits, scams, schemes, unethical behaviors and dirtbags charging gil for capacity point camps they use bots to obstruct others from having access to. FFXI will be greatly benefited by enhanced, modern, and requirement accessed communication capabilities.

Please make this a priority. Honorable players are utilizing /blist to squelch these offenders, due to the ease of access to new account creation without a buy-in requirement these undesirable vermin continue to infest the primary accommodation for players to communicate for content that is designed for cooperation occurring alongside our fellow honorable players populating FFXI servers.

[TullemoreAsuraFFXI]

Completely agree, the game should allow /blist capacity of 500 minimum. Once /blist capacity has be increased to 500 or more, there should be provider side capabilities that detect massive /blist additions to quickly discover and investigate Terms of Service violations.

Other Beneficial upgrades that can be done:

Have /yell(lvl) communication and disable the universal /yell and add ability to filter each particular level bracket of /yell(lvl).
Example: /yell99 serves for only those who have obtained a lvl 99 job and have the filter set to allow.
Example: /yell90 serves for only those who have obtained a lvl 90 job and have the filter set to allow.
Example: /yell80 serves for only those who have obtained a lvl 80 job and have the filter set to allow.
Example: /yell75 serves for only those who have obtained a lvl 75 job and have the filter set to allow.
Example: /yell60 serves for only those who have obtained a lvl 60 job and have the filter set to allow.
Example: /yell40 serves for only those who have obtained a lvl 40 job and have the filter set to allow.
Example: /yell20 serves for only those who have obtained a lvl 20 job and have the filter set to allow.
Example: /yell10 serves for only those who have obtained a lvl 10 job and have the filter set to allow.
Example: /yell3 serves for only those who have obtained a lvl 3 job and have the filter set to allow.
Example: /yell0 serves for only those who have no job level above lvl 2 and have the filter set to allow.
After creating channels for /yell0, /yell3, /yell10, /yell20, /yell40, /yell60, /yell75, /yell80, /yell90, /yell99 allow the display and use of these channels both inside and outside of cities.
Interface the filter selection so that it is quickly convenient from the menu, preferably with it's own lead category as to not bury it three+ levels deep into the current chat configuration settings.
Create text commands to allow and disable each channel. Examples: /allowY99 /disableY99 /allowY40 /disableY40

Increase allowable Linkshell active capacity to 2000. Enhance the Linkshell search interface to allow for all character names equipped with a pearl to be shown without truncation.

Allow for Linkshells #3 and #4 to be equipped.

Allow for the Unity communications to have capacity of 4000 or more, so there is no more "The maximum number of people are already participating in Unity chat. Please try again later." Error messages.

Create communications channels based around the traditional /seacom categories. Can use /c or /w as a designation beginning.
Examples: /cExp /cBattle /cMission /cQuest /cItem /cLinkshell /cSocial /cOther

Upgrade + Enhance + Overhaul the /seacom interface to include instructions about usage, instructions about etiquette, and the ability to search for key words displayed in the /seacom entry of any character that is displaying a /seacom.

Allow a /seacom to be set for each individual category with a blank /seacom being designated as disabled for that category. In this way each player can enable and display a /seacom for Exp ~ Battles ~ Missions & Quests ~ Item ~ Linkshell ~ Looking for Friends ~ Others.

With the enhancement of the /seacom interface for quicker search results; create and allow for content tags to be attached to /seacom. Example: a /seacom applied to the Exp category could be tagged with a level range bracket selection and desired vana'diel area. Example: a /seacom applied to the Item category could be tagged with a item type selection, a crafting source selection, a battle content type selection, a level usage selection etc, a auction house inventory category selection.
Detailed Example: Utu grip could be entered with text into the display of a /seacom under the {Item} category and then be tagged with {Omen} {LVL99} {Battlefield} {Grip} {Reisenjima}
Detailed Example: Sublime sushi could be entered with text into the display of a /seacom under the {Item} category and then be tagged with {Cooking} {Food} {Synthesis} {Item} {Meals} {Seafood}.
Allow for up to seven tags to be attached to eash active /seacom.


For those who further wish to denounce RMT and give constructive recommendations and advice:

http://forum.square-enix.com/ffxi/th...ht=Scourge+RMT
http://forum.square-enix.com/ffxi/th...-WHERE-ARE-YOU

Within this self-quote admittedly if all of my suggestions fully became implemented, it would be significant upgrades in coding and development. That being said, i am bumping this topic and if no effort is made with the NOV SE FFXI Digest, I will bring this subject up there.

[Alhanelem]

Completely agree, the game should allow /blist capacity of 500 minimum. Once /blist capacity has be increased to 500 or more, there should be provider side capabilities that detect massive /blist additions to quickly discover and investigate Terms of Service violations.

Other Beneficial upgrades that can be done:

Have /yell(lvl) communication and disable the universal /yell and add ability to filter each particular level bracket of /yell(lvl).
Example: /yell99 serves for only those who have obtained a lvl 99 job and have the filter set to allow.
Example: /yell90 serves for only those who have obtained a lvl 90 job and have the filter set to allow.
Example: /yell80 serves for only those who have obtained a lvl 80 job and have the filter set to allow.
Example: /yell75 serves for only those who have obtained a lvl 75 job and have the filter set to allow.
Example: /yell60 serves for only those who have obtained a lvl 60 job and have the filter set to allow.
Example: /yell40 serves for only those who have obtained a lvl 40 job and have the filter set to allow.
Example: /yell20 serves for only those who have obtained a lvl 20 job and have the filter set to allow.
Example: /yell10 serves for only those who have obtained a lvl 10 job and have the filter set to allow.
Example: /yell3 serves for only those who have obtained a lvl 3 job and have the filter set to allow.
Example: /yell0 serves for only those who have no job level above lvl 2 and have the filter set to allow.
After creating channels for /yell0, /yell3, /yell10, /yell20, /yell40, /yell60, /yell75, /yell80, /yell90, /yell99 allow the display and use of these channels both inside and outside of cities.
Interface the filter selection so that it is quickly convenient from the menu, preferably with it's own lead category as to not bury it three+ levels deep into the current chat configuration settings.
Create text commands to allow and disable each channel. Examples: /allowY99 /disableY99 /allowY40 /disableY40

Increase allowable Linkshell active capacity to 2000. Enhance the Linkshell search interface to allow for all character names equipped with a pearl to be shown without truncation.

Allow for Linkshells #3 and #4 to be equipped.

Allow for the Unity communications to have capacity of 4000 or more, so there is no more "The maximum number of people are already participating in Unity chat. Please try again later." Error messages.

Create communications channels based around the traditional /seacom categories. Can use /c or /w as a designation beginning.
Examples: /cExp /cBattle /cMission /cQuest /cItem /cLinkshell /cSocial /cOther

Upgrade + Enhance + Overhaul the /seacom interface to include instructions about usage, instructions about etiquette, and the ability to search for key words displayed in the /seacom entry of any character that is displaying a /seacom.

Allow a /seacom to be set for each individual category with a blank /seacom being designated as disabled for that category. In this way each player can enable and display a /seacom for Exp ~ Battles ~ Missions & Quests ~ Item ~ Linkshell ~ Looking for Friends ~ Others.

With the enhancement of the /seacom interface for quicker search results; create and allow for content tags to be attached to /seacom. Example: a /seacom applied to the Exp category could be tagged with a level range bracket selection and desired vana'diel area. Example: a /seacom applied to the Item category could be tagged with a item type selection, a crafting source selection, a battle content type selection, a level usage selection etc, a auction house inventory category selection.
Detailed Example: Utu grip could be entered with text into the display of a /seacom under the {Item} category and then be tagged with {Omen} {LVL99} {Battlefield} {Grip} {Reisenjima}
Detailed Example: Sublime sushi could be entered with text into the display of a /seacom under the {Item} category and then be tagged with {Cooking} {Food} {Synthesis} {Item} {Meals} {Seafood}.
Allow for up to seven tags to be attached to eash active /seacom.


For those who further wish to denounce RMT and give constructive recommendations and advice:

http://forum.square-enix.com/ffxi/th...ht=Scourge+RMT
http://forum.square-enix.com/ffxi/th...-WHERE-ARE-YOU

I can see where you're going with this but this is an obnoxiously complicated method and I don't really want to deal with a dozen text commands.

Equally unrealistic (perhaps) but infinitely simpler would be if banned or deleted characters were automatically removed from blacklists.

[TullemoreAsuraFFXI]

Another idea i had about this topic and /blist in general. Square Enix could add a feature to the /blist interface to where the game could detect if the offending account is still active or if it has be deactivated, then display the results. In this way we could browse through the names and remove /blist entries from our /blist for the deactivated accounts that we deem to be no longer a present threat.

[Sirmarki]

Another idea i had about this topic and /blist in general. Square Enix could add a feature to the /blist interface to where the game could detect if the offending account is still active or if it has be deactivated, then display the results. In this way we could browse through the names a remove /blist entries from our /blist for the deactivated accounts that we deem to be no longer a present threat.

That would require a fair amount of server CPU usage and I'm also not sure where that would stand with data protection laws in a lot of countries/regions.

[TullemoreAsuraFFXI]

Rather than a report on the account being active, maybe there can be a report for the time stamp on the last occurring login.