Search:

If you are getting that error, then you haven't patched correctly...

The patch requires the latest files from CVS, and then needs the patch applied.

(dateLen:3926...

If you are getting that kind of error, then your everquest.h file is probably earlier than the revision 1.65(last updated 4 days ago in CVS)

The quick and dirty patch should install without errors...

Thanks... but the real credit should go to Zoolander for posting the structs, and some basic instructions.

All I did was turn the results into a .diff file to make it easier on the rest of ya.

Agreed...

I just threw it up in the patch section as an alternate way for people to find it. Some people might actually look for patches, afterall.

It was just a quick and dirty way to get...

Nah, I only jumped on that guy, cause all he did was post a link to the thread when a link was a couple messages above his.

Oh, and even tho I made the patch file, the true credit is not mine...
...

Trying to up yer post count, eh fuqjak?

Maybe you didn't notice... but that post you reference happens to be in this very same forum.

In any case, those who post in this dev forum are usually...

Thanks for the redundancy...

Look up 4 posts from this one.

There's a patch for this already...

Tho it's not in CVS yet.

check this thread:

http://seq.sourceforge.net/forums/showthread.php?s=&threadid=3627

not yet... but submitted as a patch already.

It might help if ya check out the latest patch info in the dev section...


Take a look over here:
http://seq.sourceforge.net/forums/showthread.php?s=&threadid=3627

Changes worked for me......

It's amazing... I was actually able to understand and make the changes needed...


But for those who have slower systems, or don't quite understand it... here ya go.


Don't ask me how to apply...

In my view, adding this new forum would be a good thing. Those who want to keep things the same, can simply ignore the new forum... but adding a new and likely high traffic area of communication can...

I don't think the IRC channel is that bad... I did check it out a while back... Wasn't hostile at all... but there is a huge delay in response time (cause people are usually doing other things, and...

Well, it was my hope that this thred would spark some conversation, and get us to share the info we have, or at least let us put in requests for info that others might have that would make your work...

Alright, I'd like to help make this program work again...

I know that there are likely several steps needed to get it working, but I am a bit clueless as to what most of them are.



First of...

Yeah, I started this thread in R6 for a reason...


Did you ever notice that this particular forum never seems to have any new messages whenever SEQ is working?

Could it be that when SEQ is...

Well, I'm not sure on how valid this info is, due to SEQ decode issues...

But if SEQ is still spitting out data the way it should, then I have a few opcodes to toss out. Keep in mind tho,...

After tracking down where the error comes from, and looking at the source(I still suck at programming, tho I can still usually read code, can't fix it tho), I'm amazed that it even functions at...

Ok, I'm finding more and more potentially useful opcodes... However, I am not able to find corresponding listings.

My questions are these:

1: Is it alright to make a couple new listings in...

Many thanks...

After a bit of looking, I finally realized that I needed a "new" account for that section. Anyhow, it's up there now. I hope it proves useful to the masses.

After this, I may...

With me, I'm getting some slightly different results...

I seem to be suffering from "warm up time". When SEQ starts, it gives me all those unknowns, and refuses to show ground spawn(dropped items...

Ok, I was able to follow the commands above, and now have a nice new .diff file... (had to add ".diff" to the end of the command) Only problem now is(i'm such a newb) I can't seem to locate a way...

Ok, I found several more missing opcodes...

I also don't know what a few others would be called...

For example, 0x0019 is a message to adjust your HP(both increase and decrease). I don't know...

Well, it was an easy check... but I've found it.

The new RemDropCode should be "0x00d0"

Simply update that in your opcodes.h file and recompile.


Now I'm not much of a coder these days, so...