Install DLL to trace code to OS Debug Print functions.

Okay... just a quick note to say that that tutorial is now up.

It is as complete as I plan to make it in this first part, but as I work on getting other parts into DLLs I plan to make other parts in separate threads, hence the (Part 1.) bit.

It covers creating a new DLL and provides downloads for a build environment to do so. It covers adding imports to your game.exe and modifying your game to use the functions in the DLL.

All programming is based on x86 assembler, and specifically the dialects used in OllyDbg and the GoASM build environment I provide... but mention is made of terminologies in higher level languages like C, C++ or common Basic dialects which are synonymous to x86 Assembler. I also make reference to common dialogue differences in other Assemblers which people may be familiar with as GoASM is quite new and has some very unique features.

Although I point out that you can create DLLs in other languages and link them in the same way, there will be issues that are far easier to overcome in Assembler, and you should probably get a working Assembler DLL integrated before you port it to a higher level language anyway. x86 is common to us all, it is the language we are used to seeing in PT and it is what all our programs for PT end up in at one point or another. I don't see any reason why I should alienate people who would like to end up with Fortran source for their DLLs because I wrote a guide targeting C programmers or something, when whatever language we use it ends up as x86 and we need to know x86 to hack the client Exe to use our code anyway.

It is more wordy than any guide I (or anyone here I think) has ever written, but it does contain liberal source listings which I have hand Syntax Highlighted and commented to the level of overkill to make them as clear and legible as possible. I can take screen shots of my text editor for those who like pretty pictures, but you can't copy and paste code from a screen shot so I really don't see the point.

I apologias to our Brazilian readers who like to follow everything from a video guide, but you can't follow those at your own pace, and you could hardly make sense of the code (which is the main part of the tutorial) in a video window either.

Large reams of well written (I hope you find it is) and clearly formatted (I tried hard) text is really the only way (short of a seminar) that I can describe the process to you in a way that you may be able to follow.