← Back to DevelopmentAging & Mixing viewer.dll generatorProgramsClan filesInternet Information ServiceOllyDbg tutorialsMiscellaneousSkinsLinks / Files

increase_consecutive_messages_limit

← Back to Miscellaneous
When you are a GM, and you use the same command over and over (for instance /@put or /@get) you hate to see that message telling you you are too talkative.

Inside the client, there's a conditional jump (JBE) taken if your number of consecutive message is below a limit. If it's above, the jump isn't taken and the annoying message appears.

OllyDbg - Client side

005598DA  |.  83F8 0A       CMP EAX,0A
005598DD  |.  A3 C8B03B03   MOV DWORD PTR DS:[33BB0C8],EAX
005598E2  |.  76 72         JBE SHORT 00559956


The default value, as you can see, is 0A.
Now you have 2 solutions : either increase the limit, or transform the conditional jump into an unconditional one (JMP) to completely disable the message.

1. Increasing the limit

Let's change it to 20 (= 32). The message will trigger after the 32th message.

OllyDbg - Client side

005598DA      83F8 20       CMP EAX,20
005598DD  |.  A3 C8B03B03   MOV DWORD PTR DS:[33BB0C8],EAX
005598E2  |.  76 72         JBE SHORT 00559956


2. Disabling the message

We simply need to convert the JBE instruction into a JMP one.

OllyDbg - Client side

005598DA      83F8 0A       CMP EAX,0A
005598DD      A3 C8B03B03   MOV DWORD PTR DS:[33BB0C8],EAX
005598E2      EB 72         JMP SHORT 00559956


Note that disabling the message won't allow you to spam endlessly.
The server also has an anti-flood mechanism that will disconnect you if you send too many message in a too short time.

That's why I believe the first solution, with a bigger value is the best. Because it'll remind you not to send too many messages.