Sorry, GS1 has been disabled in PMs.
 

On Era, I tried to send a PM containing a link to a page on the forums.

It said "Sorry, GS1 has been disabled in PMs."

I'm not sure if this is local to Era or not, so I posted it here.

Your link probably contained a #, and that's why it refused to send it.

It's local afaik. Should be part of the swear filter, to disable the use of things like #a or #n in mass messages.

Should make it ignore links then. :]

Huh?

It should detect where it is an attempt to use #a or #n, or part of a URL, or other such use, in which case it should be allowed and displayed correctly!

The era word filter could be changed to only filter full words. Why are stuff like #a and #n filtered though? Somehow it was the intention of that feature in PMs to be used.

Because it was pretty damn annoying, people used those in masses and all the newbies got confused, and so on.

"#n just admitted he loves boy!!!!!!! ewww lol."

NO I DIDN'T.

"omg i just saw #a hacking! tell staff"

I WASN'T!

The only use for it that I can think of that is midly useful and not annoying is the introductory PM from the NPC server or something, and I'm pretty sure you can use actual GS2 in those so it doesn't really matter.

P.S. Crow, I removed the F word and such from the built in swear filter because I was going to release the *ChatFilter npc that just replaces bad words with ok words.
But for some reason the NPC version keeps filtering ',' and removing it.
I tried to do a hackish fix by filtering ',' to ',' but then that only let me use ',' on it's own, and if it was attached to the end of a word (eg 'word,') it'd still remove it.

So you might want to get somebody to readd the swear words to the filter, or if you can, fix *ChatFilter, because replacing the text can be pretty fun sometimes.

I know it does that, thats why I coded my own one o.O Don't you remember? It eats quite a bit of cpu though, because Graal doesnt have a built in function to replace text in a string :(

GS1 stuff like #a #n etc. should be allowed in PMs - it's the staffs job to monitor that it doesn't get abused. It's quite useful for things like...


"Hello #n! I'm selling:

Potatoes

If you are purchasing any, please PM me about it!"

It can make masses so more personal, in a good way.

There are much better ways to harass people in PMs. And, you can't really report it to staff, because history can be faked. I'm tempted to post it here, but I probably better not.

Why not have it so names made using #a and #n and etc are in a different font color? That way you can tell it's not directly to you.

Also, regarding disabling it and its "uses"; what about #1 and #2 and etc, which are useful on their own, but when we actually try to list number options we get "sword1.png"

There is no need for any player to have the ability to PM another player saying "I'm buying a #w, do you happen to have one? :D" or "#c #c #c #c #c #c #c #c #c :3" and so forth, as well as what Kia345 said about it completely interfering with people's preference of displaying rankings such as "#1: *kia345" or whatever you choose.

GS1 shouldn't be in the scripted PM window, end of story. That's my opinion and I'm sticking to it.

Regardless of GS1 in PMs, it still should allow links to be sent.

There's not quite a lot we could do about that, since it's not a locally scripted thing, where we could be like

especially for PMs. I think that's the fault of the Wordfilter Rules file, itself. If I remember correctly from seeing it last time, it is set to 100percent accuracy, on FULL word association (as oppose to PART) for things like #a, but even if you say #about, it still filters it out and returns the error.

Then just disable it, and warn people who use the codes. That's the job of a GP.

That is a social solution to a technical issue. That is bound to cause trouble.