PDA

View Full Version : ShowEQ 6.3.5 for Live 08/16/23



BlueAdept
08-16-2023, 06:21 PM
Announcing the release of ShowEQ version 6.3.5. Special thanks to Newby for the patch.

This version is compatible with the Aug 16th release.



BlueAdept (08/16/23)
----------------
- Update to version 6.3.5
- Support for EQ Patch 08/16/23
- Struct and opcode updates (Newby)


This new release is available in the files section of SourceForge at https://sourceforge.net/projects/seq/files/ShowEQ/Showeq-6.3.5/, or from the SVN repository at http://svn.code.sf.net/p/seq/svn/showeq/tags/v6_3_5/

Installation (tarball):


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


Installation (SVN):


$ svn checkout http://svn.code.sf.net/p/seq/svn/showeq/tags/v6_3_5 showeq-6.3.5
$ cd showeq-6.3.5
$ make -f Makefile.dist build
$ ./configure
$ make
$ make install

Shinigami
08-17-2023, 05:18 PM
Anyone else getting some strangeness with skittles? seems like it's showing only nearby ones atm in chardok. Could they have implemented some kind of countermeasures?

Shinigami
08-17-2023, 05:52 PM
Anyone else getting some strangeness with skittles? seems like it's showing only nearby ones atm in chardok. Could they have implemented some kind of countermeasures?
Nm. was something going on with my network. had to reset some hardware.. sorry to clutter boards with this

xerxes
09-09-2023, 03:40 PM
I also had oddness with this release where it would detect the client at the character select, but would not populate anything once zoning in.

I went back to my 6.3.4 directory and applied the patch, recompiled, and it started working.

I suppose it could be possible something happened with the first recompile, but I can't confirm.

xerxes
09-09-2023, 03:41 PM
It's worth noting either way, when ShowEQ starts, this is showing in the console:

Debug: connect2: Unknown opcode 'OP_ZoneSpawns' with payload type 'spawnStruct'
Debug: for receiver 'SpawnLog' of type 'SpawnLog' to member '1logZoneSpawns(const uint8_t*, size_t)'

cn187
09-09-2023, 04:15 PM
Looking at the code, I'm pretty sure that message has been occurring for quite a while (2006?)

It's not hurting anything, but I went ahead and cleaned it up.