Exp limit

From what I recall:
- the infamous DC(4) errors are triggered by the client, not the server. I call it the "attempt at securing the client" :P .
This includes hitting the maximum amount of exp gained in a defined time, gathering 2 duplicated items in the inventory, ..

- DC(1) happens when the server trolls your memory, and ends up crashing because it allocated too many objects and has no handler for malloc.32 (no clue how it's called in Windows) failure.

- DC (without a number) can happen when the server disconnects you for gaining too much experience in a defined time (that's what people love to call the 2 billion limit of doomed doom)

I've tried to investigate this 2 billion error because it has happened to me quite a lot when slaughtering some oversized hellspawn in ET2, with tons of drops on the floor and alot of exp gained. But I've never managed to get where the error was triggered server-side.

And since I love lazy solution, I just divided the exp values in the exp table by 100, and the exp given by monsters by 100. Problem solved, the exp values are too low to hit the limit.

I much prefer that solution too. Also means you don't hit the top end of Exp table for many many levels to come too. :thumbup:

Two of those (not DC(4)) are coming from the server though... so that may explain why I see people saying they have fixed DC(4) in their server.

I suppose the real "myth" I'm talking about is the idea that all over exp DCs are DC(4)... which it has become synonymous with.

That thinking is wrong. Not all DC(4) is Exp, and not all Exp is DC(4). In fact... the number of disconnect messages (all originally containing the same text string) in each client varies, so the numbers can't even be consistent between clients, let alone the reasons for them. :(:

The fact of the myth is that PT disconnects you (for one of several reasons) when you level too fast. It also disconnects you for other reasons, and it's never very descriptive as to why you where disconnected.

If it was, that would make debugging and user complaints much easier to solve... but it would also make cheating with hacks an absolute doddle.

Quote:

---

Originally Posted by Gregoo

And since I love lazy solution, I just divided the exp values in the exp table by 100, and the exp given by monsters by 100. Problem solved, the exp values are too low to hit the limit.

---

There are 2 ways:

1. to do it manually.
2. to use Filterheadz Exp Table Editor v1.0.

I saw that you suspected him because of the connection between my machine to his server, can I trust him?

if it helps, the disconnect packet is 0x48470033. (thanks telatoro). I used to send this packet in my emulator when my emu detected some suspicious activity from player.

Dc(4) means hacking attempt. -> see server log to details on what cause it.

is triggered by client sometimes and sometimes is triggered by server.
when is triggered by client checksums (like player inventory or player xp checksum) it sends a packet to server and it goes to log error function and then the disconnect packet is sent to client.
when is triggered by server on checksums (like player positioning, also player xp, items on player, memory client responses checksums) its redirected to log error function and then dc packet sent to client.

So i recomend if possible in your case check your server logs to see wich is the specific error that is generating the DC4, then look if is client or server, for client look then when you generate the packet to server with the error parameter, or in server the calls for error log with that error parameter.

Quote:

---

Originally Posted by tnrh1

I saw that you suspected him because of the connection between my machine to his server, can I trust him?

---

Unfortunately, Filterz mixed two projects into one. He was working on a "chat" solution at the time he wrote the level table editor, and thought it would be a good base for an automatic update system for the editor.

I believe he has since turned off the server it tries to connect to, since he has suspended PT development and so no updates will be posted.

He stated (and my tests agree) that you can run his tool with your Network Adapter disabled, and it will run fine. (you could also pull the RJ45 if you run wired or, as I did, use a Virtual Machine with no virtual NIC at all)

The fact remains that if he programmed automatic update capabilities into it, then it could update to become a trojan. And if he is no longer monitoring the update server, it could be hijacked and do so without even his knowledge.

So your concern is quite justified. But if used carefully, the program (as it stands) does function as advertised. :wink:

the algorithm of the monter's exp decides 2kk. if beyond this exp limit,it will become negtive,the reason is in server.exe.i can give you a clue,you should continue the next step by yourself, find [ebx+3ABC] in your server.exe, the exp you got will be writen in it.you just need to modify the algorithm to solute it.at last,i think someone here mistakes the topic,we are talking about the exp from one monster,not 2 billion after a long time we got from many monsters. sorry for my poor english..

The 2 billion exp dc 'High Experience Gain' is caused at 450099 (server side obviously)

It's inside the function that checks if the save data is valid, you'll see it returns -9 for this 2 bil exp error. (ah and it depends on the character level, for high levels its 2 bil limit, lower levels its a lower limit. above 110 I think it doesn't even check anymore)

It compares the Begin EXP at the time you logged in with the EXP the save data contains, if it's bigger than 2 billion -> dc (and rollback because this save data gets ignored).

I wouldn't remove this check though, as it will enable a cheater to set their exp to max and that's it, he's max level, pretty easy.

Anyway, in the current system a cheater can set their EXP + 2bil each time he logs in and this way he can also get to max level, but he'll have to relog alot (but might be worth it).

Currently the GameServer (or 'SubServer' some might call it) sends a 'Kill Monster' packet to the client when he kills a monster, that packet contains also the EXP that was gained. The LoginServer never knows about this EXP gain because the GameServer is not connected to the LoginServer.

To prevent cheaters from gaining fake EXP you should connect your GameServer with your LoginServer (by writing your own code). And instead of the GameServer sending the 'Kill Monster' packet to the Client, it should send it to the LoginServer, and the LoginServer would send it to the Client. This way the LoginServer can validate the EXP gain, and thus increase the 'Begin EXP' with the EXP gained, you can then also remove the 2 billion cap (just make it 0 to prevent any exp cheating).