Disable PM's from login for non-P2P/Classic

[Crono]

Recently it's been abused by phishers and anti-Graalians as a way to spam every person on every server with PM's linking them to "Graal hacks" and whatnot. I propose disabling PM's from the login server fom un-upgraded accounts to prevent this. If they try to log on playerworlds, we can simply ban them (unlike the login server, where only globals can deal with them).

[Akios]

This idea is way too logical.

[Felix_Xenophobe]

Global pm pass purchased from gelat shop 3 bucks a pop. The graalonline way

[Stephen]

Originally Posted by Felix_Xenophobe

Global pm pass purchased from gelat shop 3 bucks a pop. The graalonline way

monthly

[ffcmike]

Perhaps prevent global PMs to players on servers you are banned on. Not a full solution but less punishing towards normal players.

[Crono]

Originally Posted by ffcmike

Perhaps prevent global PMs to players on servers you are banned on.

That doesn't fix it though. What if no GP's are on to ban the account when it starts spamming players? What stops them from simply creating a new account and doing it again?

[cbk1994]

Originally Posted by ffcmike

Perhaps prevent global PMs to players on servers you are banned on.

I'd like this plus not allowing non-upgraders. A lot of the times they're using upgraded accounts, so it would help a lot if PRs could ban them on Era to prevent it.

Ideally allow PMs to players with RC (staff) for non-upgraded players, but I think this is probably hard for Stefan.

[Crono]

Originally Posted by cbk1994

Ideally allow PMs to players with RC (staff) for non-upgraded players, but I think this is probably hard for Stefan.

Getting any type of seemingly basic update seems to be hard.

[Crono]

So we have players using basic trainers, which is no big deal because they get banned in seconds and are only spawning bombs or walking on the OSL wall. We now have someone lagging up everyone's clients to the point where the Graal client becomes unresponsive. Said person is now crashing the place with too many bomb spams. How nice, and he creates accounts in seconds which means everytime we ban him he just comes back after half a minute.

[cbk1994]

Bump because this is getting ridiculous.

[nightslayer317]

Fogles is a lonely boy, he needs some attention. Graal hackers used to be less sloppy and more dominant.

[cbk1994]

Stefan just replied to my email:

Hello,

I've disabled it on login.

cya,
Stefan

[fowlplay4]

Originally Posted by Crono

Said person is now crashing the place with too many bomb spams.

This has become a major problem on Zodiac, particular because the hacker will go into the OSL and crash everyone. We have a script that removes the bombs but it still generates too many and crashes the client.

We need a server update to fix this problem as well. Preferably a server option, pretty much every server on the login server-list except for UN has a classic bomb script.

A maximum bombs per second threshold (if they go they're disconnected and logged) to prevent putbomb/putexplosion spam hacking needs to be implemented. A server option like:

putbombthreshold=5

Classic features like putbomb, putexplosion have no place on custom system based servers like Zodiac and Era. So if you set it to 0 it would just disconnect them if they manage to create a bomb.

[ffcmike]

Originally Posted by fowlplay4

This has become a major problem on Zodiac, particular because the hacker will go into the OSL and crash everyone. We have a script that removes the bombs but it still generates too many and crashes the client.

We need a server update to fix this problem as well. Preferably a server option, pretty much every server on the login server-list except for UN has a classic bomb script.

A maximum bombs per second threshold (if they go they're disconnected and logged) to prevent putbomb/putexplosion spam hacking needs to be implemented. A server option like:

putbombthreshold=5

Classic features like putbomb, putexplosion have no place on custom system based servers like Zodiac and Era. So if you set it to 0 it would just disconnect them if they manage to create a bomb.

Same for disabling the default shootarrow(dir); type projectiles.

There was already a server option called limitfreeplayers2 which disabled default projectiles and bombs for trial players, but this option was disabled because it also prevented trials using the shoot(); function.

[ffcmike]

I noticed this was added to serveroptions list on Graal Bible:

putbombenabled=true/false
bomballowedtypes=all or comma separated text of bomb power (e.g. 1,2,3)
bombfilterlog=true/false - logs to logs/bombfilter.txt

http://www.graal.net/index.php/Server_options

Funnily enough putbombenabled apparently existed already:

http://forums.graalonline.com/forums...3&postcount=24