Post Reply Home » Forums » Dark Age of Camelot » DAOC Discussion

Patch 1.68c on Pendragon : DAOC Discussion

Posted: February 6th, 2004
stagemaster
http://www.camelotherald.com/more/1322.shtml

Is it time to cry and pack it in?

************************************
~>Sanya states:

As some of you have no doubt observed, this patch contains some things designed to hinder, break, spindle, fold, and mutilate certain third party programs. We’d appreciate it if everyone could pop onto Pendragon in the next two weeks and make sure there are no performance or movement problems for our average customers who don’t need to cheat to be good at video games. Thanks!

************************************

This is in reference to the patch on Pendragon.... I haven't the minerals to look and see if xunleashed works :-)
Posted: February 7th, 2004
LLCoolJ
He has already said <b>numerous times</b> it won't affect this one, just the other ones that used packet sniffing, as opposed to memory sniffing.
Posted: February 7th, 2004
stagemaster
Sweet, thnx mate!
Posted: February 8th, 2004
notmyrealname32
Still waiting to hear if it will break the RT Chatlogger and associated macro/trigger things
Posted: February 8th, 2004
TheCaptain
I don't know that much about the inner workings of things but I do use the ChatLogger and triggers.

The new patch should not affect these programs in any way. All the chat logger does is take a look at the log files that DAoC creates anyway (even for people who don't use XU) and then parses them. The trigger program then looks at the second log that ChatLogger creates and reacts to it according to what you have it set up to do. Other than maybe needing an update to the DAoC service after the patch, these two programs should not be affected at all. It's not as if Mythic is going to start encrypting the log files. If they did, they would be pretty much useless to everyone that uses the log for anything.

Correct me if I'm wrong Admin or WyvernX?
Posted: February 10th, 2004
drmctchr
The normal DAoC log is time delayed to prevent triggers and macroing. The RT chatlogger reads either incoming packets ( most do this ) or DAoC's memory space. IF the former THEN RTChatlogger == broken until a way to decypher packets is made OR until memory is read in the stead ELSE IF later THEN RTChatlogger == is not affected.
Posted: February 10th, 2004
Admin
From what I have read, the rt chat logger uses memory sniffing, so it should not be effected.
Ready to join the community? Click here and see all of the benefits!
blue large dotWho is online
Users browsing this forum: No registered users and 29 guests
Post Reply