Mix error

Bobsbol, I am not using ultimatept files.
I have worked on the ultimatept files to be the easier files to work with for the begginers, its not have alot of features.
I am using the jobchanger files and the "updated mix editor" like you have said.
I hav'nt find any guide or posts about how to make mixes with the mix editor in olly or hex.
That would be very great if you can explain me how to do it or give me just the basic so I can start from somwhere cause it looks like i am not going my mix table from that damn editor.
thanks.

No... I've not seen any guide or post about how to change the table in Olly or Hex either... which is why the comment "I know everyone here knows how to do this already" sticks out in my mind.

It was a years old post, and maybe the likes of Sandurr, Shagpub, QuantumFusion etc did know, and didn't need a guide. Maybe even Telatoros generation did, but I don't.

Watching what the mix editor does to a server it does know about, the mix tables are in code, not data. So changing their operation is something like changing Maps to hunt-maps or changing the cooldown on skills... that's about as much as I know.

It's not the sort of thing I care to do... If I'm going to release a developed server it will work like one of the official servers, so I'd only really change the jPT tables to add the newer mixes as they work on the newer official clients and there are things which I want to do which are more important to me than that. But if I looked at it again I imagine there is selection sequence code which should stand out. Compare the edits it makes to a server it knows about, and search for similar code in your server.

Then run your server in a test environment under Olly, with breakpoints anywhere that looks promising. Log in, and perform a mix... just about any mix will do. Hopefully the server will break at the code it uses to mix... then you know which code section it is actually using.

The reason there will probably be several sections which look promising is that developers often jump out to their updated code sections, in the middle of a sequence, or at the beginning and jump back either at the point they left (if they jumped out in the middle) or to the end of it (if they jumped out at the beginning and replaced everything). Then they don't clear out the old code... it just doesn't get executed any more. So it's easy to find code which is now redundant, and that's just confusing.

Once you know the code section that works, you need to read through it and try to understand what it does, to know which constants to change in the code. I imagine some of the Ultimate guys will be able to do that, but if you are struggling, post the code here and I'll pass my eye over it to see if we can't work it out... then you can write a tutorial. As us youngsters have been mollycoddled with "Mix Editors" for far too long. XD (this is why I prefer guides to tools releases unless the tools come with source)

Quote:

---

Then run your server in a test environment under Olly, with breakpoints anywhere that looks promising. Log in, and perform a mix... just about any mix will do. Hopefully the server will break at the code it uses to mix... then you know which code section it is actually using.

---

My weaknes is olly, then let me make sure I've understood you.
I will open the server with olly run it and then run the game and then make a mix?
open the olly and and see the code the the mix use?

i'll test it and let you know.

edit:when I open the server in olly and press run the server open and then just stuck..Cant test it like that, or I am doing somthing wrong?

Quote:

---

Originally Posted by tnrh1

My weaknes is olly, then let me make sure I've understood you.

---

Sure.

Quote:

---

Originally Posted by tnrh1

I will open the server with olly run it and then run the game and then make a mix?

---

Only after you have put breakpoints on any code which "looks like" mixing code.

Quote:

---

Originally Posted by tnrh1

open the olly and and see the code the the mix use?

---

You shouldn't need to "open olly" again, it's already running your server, and unless you didn't set a breakpoint on the true (still active) mix code, it will stop the server and pop up listing the assembler code for that active mix table. Then you can disregard all the other code you set breakpoints on that you thought it might be. XD

Quote:

---

Originally Posted by tnrh1

edit:when I open the server in olly and press run the server open and then just stuck..Cant test it like that, or I am doing somthing wrong?

---

If it really is stuck, that means someone put anti-debug code in your server, which would also break any attempt to change mixes, or anything else. Maps, levels etc. I'm sure you didn't do that.

What is more likely is that Olly sits there running the server initialisation (the bit where the server say "Initializing server (4096)" or whatever).

At this point, the server is firing off it's 604 odd threads... and thread creation is slow under a debugger, because any breakpoints and the general SEH have to be patched for each thread as it's created. Olly does this rather like Thinstall, Sandboxie the WoWVM or NTVDM I believe... thread creation has become a privileged instruction and so causes an exception which is not handled by the program so it falls to the OS... the OS is shielded by Olly, as Olly is now the OS on which your program is running, and Windows just the OS that Olly is running on. XD So Olly handles the exception by creating the thread as requested, but not starting it. Then it adds all the breakpoints to that thread, and a callback to halt it's operation if any other thread needs to break... if one thread was being debugged, stepped or traced while others carried on, you would get threadlock real fast. XD

So yea... creating and destroying threads takes a lot longer in the debugger than native on Windows... but that shouldn't stop the server starting up... just... slowly.

There is no WM_PAINT loop, callback or thread during this time either, so the server window will not even be repainted if you move it, or something else covered it over.

You should still see the thread count going up in Ollys' log window, or the status bar, to indicate that it is doing something.

You forgot the part where server.exe initialized under Olly fires tons of exception, for tons of reasons that cannot be processed.
And that's why there's an Attach function in Olly.

Quote:

---

Originally Posted by Gregoory

You forgot the part where server.exe initialized under Olly fires tons of exception, for tons of reasons that cannot be processed.
And that's why there's an Attach function in Olly.

---

"Attach" attaches Olly to an existing running process doesn't it?

I've never used it, for the client, the server or anything else. I always load directly into Olly, with it's default break on "winmain" if found. It has never "fired an exception" for me... even when I've done something blatantly stupid that I would expect to send me to BSOD or something equally dire... Olly has caught the exception and handles it in it's own way then. But it doesn't generate exceptions before I've started to poke it with various pointy sticks to see what makes it flinch. XD

Maybe I'm just lucky. ^_^

http:// www.zshare.net/video/75048019f2ccee51/

The above link (broken down as RZ is doing something very odd with zshare URLs) illustrates my "usual" experience starting the server under Olly You may want to download it if you want to read anything off that screen, but what it's doing is still... viewable; in the web player. XD

If you start your server, then attach it to Olly, all the threads are already created and the hundreds of threads are patched real quick. That's just what I was saying.
Also if you have, for instance a field in your GameServer/Field and the files missing in the Field/ folder, that's the kind of exception I'm talking about.

About what you just added, sorry I don't read your messages if they are more than 10 lines long, so I won't waste my time watching a video of a server starting. Might be of interrest for others.

LMAO. No, it's far from the most riveting video... can't wait to see the ending. zzZZZzzz.

But the point is that I usually go around inserting my break points before the exe even starts, so I put up with is starting slow... from the Video, (in stunning "Real Time") you can see that patience is a requirement.

You know that Gregoo.. I don't expect you to sit the watching what you've probably seen many times before. :lol: