Further DOL Suggestions

[Etaew]

After the meeting, log located: http://www.dolserver.net/?nav=userfiles ... tail&id=16

Any further discussion or suggestions can be carried out here:

[Etaew]

Tiv and Morchant have both expressed their opinions after reading the log about the requests for the Logger to be open source, they are both against this, and think it will increase the hacks and tools availiable against DOL and Live.

It works needs to continue to develop a logger, then only that team should possibly get the source.

[Smallhorse]

As the developer of the DAOCLogger I have to say the following:

The loggers source code will not be made public, for serveral reasons.

Some of them are:
1) An open sourced logger can be abused/rewritten VERY easily to make a radar or any other cheating tool and I am totally against this. The logger itself is NO cheating tool. I don't want to help anyone that tries to gain benefits over others with such tools.
2) Having it open source makes it easier to detect and prevent it in the future from working.
3) Some of the code that went into the logger was developed in private projects of mine. While I am totally for open source code, most programmers will agree that not every line of code they write is fit to be public

Of course the logger can/could be reverse engineered. However I think anyone that CAN do this AND understand the assembler source is more than capable enough to write their own utilities

[Corillian]

The case for open sourcing the logger was only under the circumstances you would become unable to update it as it does need to be updated. Disassembling it or DAoC in order to re-crack the algorithm would be a huge waste of time (as was stated during the meeting) so it would be nice if we could come up with a solution to this problem.

[Etaew]

The other thread is for continuing discussion, this thread is for those commiting to work, thanks.