Since GMs won't patch it...

Finally figured out how to stave off DC hack.


Open task manager

Go to Processes

Right-click Maplestory.exe

Go to set priority

Set to Realtime


Doing this will greatly reduce (even remove if your comp is good enough) your chances of dc'ing, even from multiple spammers. Supposedly this also reduces normal boss lag, but I have yet to confirm this. Unfortunately this method has some negative side effects; Other programs run slower/lag and while you won't DC, you will probably lag very badly. Lastly there's no way to test it until someone tries to DC you.


Hope this is in the right section :x

Interesting.

So does this block the Vista Zakum DC glitch, too?

So does this block the Vista Zakum DC glitch, too?

To be honest, I've only recently learned of it. Who knows what other good/bad effects it could have?

Setting it to real-time will create more problems than if you put it to one of the other 2 settings though.

Setting it to real-time will create more problems than if you put it to one of the other 2 settings though.

I put it on high and still got DC'd.


EDIT: A few mins after replying to that my comp crashed... lol...

I've always used this, but never for Maplestory.
For example, saving long, edited video clips - it cuts down the time by about half.

some negative side effects; Other programs run slower/lag and while you won't DC, you will probably lag very badly.

One step forward, two steps back.

I think i love this thread @_@

I set mine to High, and went to ch 1 FM entrance. Normally I would had a good ~2 second lag between using a skill, and the MP being taken away, but with it set to high, its almost instant.

Performance also seems improved when on my dawn warrior. Potting seems a little bit faster.

Overall, this may have helped me stay alive

Very awesome if this does work, I'll try this on friday when I'm scheduled to get disconnect hacked.

Please do inform us of the results, this is the happiest bit of maple news I've gotten in a while.

if your solely playing maple in full screen mode and running nothing else, this would help. But if your computer has anything running in the background (whether active or not) it can cause a conflict between the two which more often than not causes windows to crash. I don't know exactly all the right terms for why it happens but lets just say use at your own risk and try to only do it when you really need it or a system idle process can cause your processor to freak out and crash windows and you'll be worse off than a simple d/c

I've recently also have been using this, but for Dungeon Fighter. It does reduce lag, however... Your computer may crash if you set it up that high (I believe it has something to do with RAM consumption)

My computer normally freezes or crash when I do set the priority up -holds power button-

I just tried Papping with High/RealTime priority and I didn't really lag at all, had .NET messenger and Firefox running in the background.

Putting anything to RealTime sets it above the system.

That is, Maple will have priority over the system. Of course it'll crash.

So you're just changing priorities? <_< I already knew about this.. but I doubt it'll change anything significant except minor lag.

Putting anything to RealTime sets it above the system.

That is, Maple will have priority over the system. Of course it'll crash.

Doesn't that only mean that if resources are needed to run maple properly, they will go to maple until the resources aren't needed anymore? That is, if you're able to run Maple without lag, you can let the processor and gcard work with the system whenever Maple doesn't need 100% power from them. And that 100% power doesn't happen often.

Doesn't that only mean that if resources are needed to run maple properly, they will go to maple until the resources aren't needed anymore? That is, if you're able to run Maple without lag, you can let the processor and gcard work with the system whenever Maple doesn't need 100% power from them. And that 100% power doesn't happen often.

I think he means Maple will take more resources than whats needed just to run Windows.

This will only stop spam-flood induced DCs, not the ones that exploit actual glitches.

To compliment this you can also adjust your network settings to be sure that HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\ParametersTcpWindowSize is maxed at FFFF (65535)

That will reduce the number of times per second your own machine tries to reply back "acknowledging" the spam attack and adding to the lag. Part of the reason a spam attack DC's you is because your computer wastes all it's bandwidth on the spam and doesn't have enough leftover to reply to the real server traffic to keep the connection open.

The more adventurous can experiment with Scaling and SACKS as well to try to prevent flood DCs.

http://support.microsoft.com/kb/224829/EN-US/

All this does for me is make the game lag.. like.. a slight delay of 2-3 seconds (I press jump, for example, and I jump 2-3 seconds later).

But then again, the comp I use is epic fail.