ShowEQ 5.6.0.0 for Live 9/20 or so

[purple]

Better late than never, here's an official showeq release with compatibility for Serpents Spine. Most stuff should be working ok. The new gray cons kinda suck on the map since spawn points and unknowns are also gray. You can change the spawn con colors using Options->Con Colors. If you see problems with anything, bring it up.

Special thanks to showeq42 and ksmith for all the help with this release.

Changelog:

purple (9/30/06)
----------------
+ Updated version to 5.6
+ Serpent Spine compatibility
+ Upped max level to 75 (showeq42)
+ Realigned structs (showeq42)
+ New variable length movement op (showeq42)
+ Updated yellow con range to 3 levels (showeq42)
+ Updated cons to be consistent with in game (showeq42)
+ Cleaned up showeq42's patch. Thanks to ksmith for help on the positioning packet cleanup.
+ Regenerated staticspells.h
+ Updated zones.h
+ Updated races.h
+ Named some weapon materials (uRit1u2CBBa)

Fetch the new release from the files section of sourceforge. If you'd like to see if the new sourceforge CVS anon mirror actually works better, try it in an hour. Who knows! Just be sure to use the new CVSROOT.

To install:

$ tar xjvf showeq-5.6.0.0.tar.bz2
$ cd showeq-5.6.0.0
$ ./configure
$ make
$ make install

If you have problems with ./configure, try:

$ LIBC=gnu ./configure

If you usually use a package for your distribution, I'm sure they will be along shortly, so keep your pants on.

[tanner]

Format: 1.7
Date: Sat, 30 Sep 2006 19:13:55 -0500
Source: showeq
Binary: showeq-dev showeq showeq-doc
Architecture: source i386 all
Version: 5.6.0.0-1
Distribution: unstable
Urgency: low
Maintainer: Robert J. Tanner
Changed-By: Robert J. Tanner
Description:
showeq - realtime packet analyzer for Everquest
showeq-dev - development tools for ShowEQ
showeq-doc - documentation for showeq
Changes:
showeq (5.6.0.0-1) unstable; urgency=low
.
* New upstream release
* http://www.showeq.net/forums/showthread.php?t=5718
Files:
60610f1fc800bc590b0a59b5f0c65a4b 807 x11 optional showeq_5.6.0.0-1.dsc
acb87898b0f37b14cd318e709929e818 1039743 x11 optional showeq_5.6.0.0.orig.tar.gz
e13dc106bca7ea6f78477fcd0054e453 388229 x11 optional showeq_5.6.0.0-1.diff.gz
03ec4856fed63ed45211ae415000fcb5 11236238 doc optional showeq-doc_5.6.0.0-1_all.deb
4868fbcbede8e3e7f2a234317cf3a68a 4504170 x11 optional showeq_5.6.0.0-1_i386.deb
8d99eea2b173c1633a27f84af6833982 86412 x11 optional showeq-dev_5.6.0.0-1_i386.deb

[dudex]

THANK YOU!

Question: tanner - last time I clicked your "ShowEQ Debian Package Installation HOWTO" link, followed the instructions, and everything just worked. However, this time I got:

showeq is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 135 not upgraded.

This is immediately after 1) running aptitude and hitting update, and 2) opening a terminal and typing apt-get update. It hit 16 locations from ftp://ftp.real-time.com sarge/.

What am I doing wrong?

[tanner]

Format: 1.7
Date: Sat, 30 Sep 2006 19:13:55 -0500
Source: showeq
Binary: showeq-dev showeq showeq-doc
Architecture: i386 all
Version: 5.6.0.0-0sarge1
Distribution: stable
Urgency: low
Maintainer: Robert J. Tanner
Changed-By: Robert J. Tanner
Description:
showeq - realtime packet analyzer for Everquest
showeq-dev - development tools for ShowEQ
showeq-doc - documentation for showeq
Changes:
showeq (5.6.0.0-0sarge1) stable; urgency=low
.
* New upstream release
* http://www.showeq.net/forums/showthread.php?t=5718
Files:
39e27b714d42a601a4503dd24636eda2 2235178 doc optional showeq-doc_5.6.0.0-0sarge1_all.deb
556178bd46fa9b9269312f1388525d9e 6785608 x11 optional showeq_5.6.0.0-0sarge1_i386.deb
8496b8cf7b68c79958b8d37f75c9f05a 86438 x11 optional showeq-dev_5.6.0.0-0sarge1_i386.deb

[tanner]

THANK YOU!

Question: tanner - last time I clicked your "ShowEQ Debian Package Installation HOWTO" link, followed the instructions, and everything just worked. However, this time I got:This is immediately after 1) running aptitude and hitting update, and 2) opening a terminal and typing apt-get update. It hit 16 locations from ftp://ftp.real-time.com sarge/.

What am I doing wrong?

You are running sarge and the previously posted release was for sid.

I just created a sarge package, things should work properly now.

[uRit1u2CBBA=]

5.6.0.0 works fine with EQ's 10-04-06 patch.

[tanner]

Format: 1.7
Date: Sat, 30 Sep 2006 19:13:55 -0500
Source: showeq
Binary: showeq-dev showeq showeq-doc
Architecture: amd64 all
Version: 5.6.0.0-1
Distribution: unstable
Urgency: low
Maintainer: Robert J. Tanner
Changed-By: Robert J. Tanner
Description:
showeq - realtime packet analyzer for Everquest
showeq-dev - development tools for ShowEQ
showeq-doc - documentation for showeq
Changes:
showeq (5.6.0.0-1) unstable; urgency=low
.
* New upstream release
* http://www.showeq.net/forums/showthread.php?t=5718
Files:
8d80c1edba6df4e3553ab949d5ab0a11 3378198 doc optional showeq-doc_5.6.0.0-1_all.deb
3246642977a41d23ab7695bc9e24341d 4549870 x11 optional showeq_5.6.0.0-1_amd64.deb
0fdfb2590440e70c85506a7083410f7a 86400 x11 optional showeq-dev_5.6.0.0-1_amd64.deb

[tanner]

NOTE! This is for Debian sid (unstable) -and- amd64, i386 will be along shortly.


Format: 1.7
Date: Wed, 11 Oct 2006 03:58:46 +0000
Source: showeq
Binary: showeq-dev showeq showeq-doc
Architecture: source amd64 all
Version: 5.6.0.0-2
Distribution: unstable
Urgency: low
Maintainer: Robert J. Tanner
Changed-By: Robert J. Tanner
Description:
showeq - realtime packet analyzer for Everquest
showeq-dev - development tools for ShowEQ
showeq-doc - documentation for showeq
Changes:
showeq (5.6.0.0-2) unstable; urgency=low
.
* Con color patch (Thanks purple!)
Files:
e2ddedbfe832431a0eec28987e5fa198 807 x11 optional showeq_5.6.0.0-2.dsc
acb87898b0f37b14cd318e709929e818 1039743 x11 optional showeq_5.6.0.0.orig.tar.gz
fa996ebd4b788a64d03aa53a23e5611f 387753 x11 optional showeq_5.6.0.0-2.diff.gz
6e3b7fc72ef64f48ab8944529ff134e9 3378430 doc optional showeq-doc_5.6.0.0-2_all.deb
9cba48dfa13f7a8d13cc092c52782c33 4550066 x11 optional showeq_5.6.0.0-2_amd64.deb
b0c8226b92cef86f29765eeb22f6faf3 86466 x11 optional showeq-dev_5.6.0.0-2_amd64.deb

[beamfoam]

--itemdb-enable is still broke, is there any plans to fix it? If not, could someone point me what to look at to fix it myself?

Output i'm getting:
Level: 0: Expected '|' but found '' at pos 7750870 field 6
Level: 0: Expected '|' but found '�' at pos 7759986 field 6
Level: 0: Expected '|' but found '�' at pos 7759986 field 6

(Map is not loading, this line just repeats every few seconds.)

Thanks.

[purple]

The problem is that the items that come over when you zone are no longer in serialized format. They used to be a |-separated string. Now it's a struct.

What does the itemdb in seq even do anyways? It hasn't been a high priority to me since I didn't even know if it was working before. That change happened a good while ago.

[uRit1u2CBBA=]

It worked at one point, but stopped using it since it was really lagging out my P-133 that I ran it on. I've had "--itemdb-disable" in my seq script ever since.

[Cryonic]

The item information was used to more accurately calculate a players health, stamina and mana with instant update as you swapped out items. That functionality died AGES ago (possibly pre-5.x) and was never a priority to fix since the values could be calculated from the combat information flowing over the wire.

[beamfoam]

I use it for vendor mining

Anyway, i got impatient waiting for replies last night and started looking at the code, and i basically found out what you're confirming, that the item data is now binary instead of '|' separated. Does this mean that it used to actually be '|' separated when transmitted over the wire?? (that'd be a silly waste of bandwidth, wouldn't it?)

So i basically need to make a 1) way of converting it to '|' separated (probably less coding) or 2) Change all the functions that rely on '|' separated data to use a struct instead?

[purple]

I'm sorry it took me 22 minutes to reply to your first post!

Yeah, all items used to be | separated coming across the wire. This is the serialized format. Now, for some reason, for OP_ItemPlayerPacket, it is a packed stream instead. The "easiest" way to make it work is to write something that unpacks the stream and creates a serialized item and then call AddItem with it.

But this is still a pain in the ass since you'd have to pull off the stream (the seq NetStream class may help here) knowing what all the fields are and then pass to something else that knows what all the fields are. Having multiple places need to be updated when there are item struct changes is annoying.

You can't change all functions that use serialized items over since the new packed items are only used in OP_ItemPlayerPacket. All the other item ops still use serialized items. This is why I don't understand why it was changed. ItemPlayerPacket only comes across while zoning (or I guess also when you shroud) so the fact that it is big isn't that huge of a deal.

And really the savings from losing all the |'s isn't that much anyways. I wouldn't be surprised if the conversion to binary actually grew the items. So they had to have a better reason than that. More than likely whoever wrote it the first time is long gone and whoever writes it now likes packed formats.

If you're interested in fixing this stuff, be sure to use eqitems.13thfloor.org for item format information. Note that the item format has changes that aren't reflected in format 4 of the itemDB also. I didn't look at it hard enough to see what is stored locally, but it doesn't look like it has changed (it is still on version 1) so it must not store any newer stuff.

If you just care about vendor mining, you could also just hack out the connect for ItemPlayerPacket in interface.cpp and still pickup items from vendors.

[beamfoam]

Yea, i'm quick like that.

Ok, well i'm trying to fix the code, but have bumped into a problem.

The huge item packet you get when logging in (all items in bank and on person i presume) is just a stream of item packets - the problem is, certain items have a longer header (the data before the item Name)

Bags seem to be 4 bytes smaller.
Evolvers seem to be 21 bytes bigger.
... maybe more inconsistencies

I can't find an obvious way to detect this - has this been done before in seq? or is there any other code i should look at?