EQBuilder 2.0

[gaeorn]

Would it be good to put this into a project someplace so those interested can combine efforts?

[Andrew80k]

Small update....

I got the code mostly updated and working on Linux but I'm still stuck on a windows version. I took a break to try to get the windows compile going. I had it down to 5 errors and in fixing those I now am up to around 70. I'll get it eventually, but I'm going to take a break from that and start my live collects to see where I need to start adjusting the structs and see if I can get it enough along to distribute back out for folks to start collecting...

[Sylaei]

I have gotten eqemucollector to compile but I am still getting errors on the linking.
This is one of the errors, but I haven't had much time to research them.

EQStreamPair.obj : error LNK2001: unresolved external symbol "class std::vector > StreamDestroyHandlers" (?StreamDestroyHandlers@@3V?$vecto
r@P6AXPBVEQStreamPair@@@ZV?$allocator@P6AXPBVEQStreamPair@@@Z@std@@@std@@A)

I am building it on a virtual pc running xp and visual c++ 6.0. I didn't have any luck building it with visual studio 2003.

I have had to move some files around and things of that nature. I assume this means that the source I downloaded wouldn't have compiled back when it was commited to sourceforge.

Also I am only working on the CLI version at this point. There is a DumpHeaders project that is missing from the cvs. At this point I don't think it is required.

[Andrew80k]

I'm using Visual C++ Pro 2008 to work on it but I'm running into many of the issues you are on Windows I'm sure. Are you removing the MFC stuff? I'm considering going that route, but if you are going to work on the Windows version I may just defer to you and stick with the Linux version since it is actually working...

[trevius]

If you have the collector or any of the other tools compiling under Linux, maybe we should get an SVN setup for them or add them somewhere in the existing SVN. I think all of those programs are pretty small, so it could probably be added directly into the trunk of the /utils directory of the EQEmu server source code. That way, people can work together to get them working easier. I think CD and KLS would be ok with adding you guys to the SVN if you are working on the collector/builder tools.

I assume that if the collector is working under Linux, that it can just watch the packets going to a Windows box if both the Windows PC and Linux PC are connected to a hub. That is how ShowEQ works anyway. I already have this setup going for ShowEQ packet collects, so it would be very easy for me to use it. It would be nice to have the packet sniffer working on Windows to make it so anyone could use it, but the others are fine being Linux only IMO.

Interesting stuff!

[Andrew80k]

Originally Posted by trevius

If you have the collector or any of the other tools compiling under Linux, maybe we should get an SVN setup for them or add them somewhere in the existing SVN. I think all of those programs are pretty small, so it could probably be added directly into the trunk of the /utils directory of the EQEmu server source code. That way, people can work together to get them working easier. I think CD and KLS would be ok with adding you guys to the SVN if you are working on the collector/builder tools.

I assume that if the collector is working under Linux, that it can just watch the packets going to a Windows box if both the Windows PC and Linux PC are connected to a hub. That is how ShowEQ works anyway. I already have this setup going for ShowEQ packet collects, so it would be very easy for me to use it. It would be nice to have the packet sniffer working on Windows to make it so anyone could use it, but the others are fine being Linux only IMO.

Interesting stuff!

Yeah, that's pretty much exactly the way the linux version works. That's been one of my hangups. I couldn't locate my hub. I've been using a pair of routers and the hub was never unpacked from my last move. So it was MIA. I've actually had the linux version running for a few weeks, but couldn't test it until I located the hub. Finally found it and will be starting the collection testing here in the next few days. It is my fervent hope to get the collector out publicly in the next 2 weeks. Matters not at all to me how people want it disseminated. It's up to the community. I can post a diff of the changes, or post it in it's entirety and then someone can update the svn (probably the best way). It uses a bunch of stuff from common, but will need it's own version of the common files since we don't chase live, the common stuff that needs to be changed for it to monitor live can't be changed in the emu version. I have sort of done that, but not completely. I will do it prior to posting it. I'd rather wait until I get some testing done to post it. That way I can adjust the structs/opcodes a bit more that I'm pretty sure are off a little. Shouldn't really be that much changing to be honest.

[trevius]

PM me your gmail email address if you have one. I have something that might help you with doing the opcode work.

Cavedude or KLS might need to chime in on if we want to start including these tools in the standard EQEmu download in the utils directory. Either that or we can always setup a new SVN page just for these tools. You may want to PM your gmail address to Cavedude and KLS as well in case they want to get you added to the SVN if it is decided that we want to just add them to the /utils folder. Sylaei might want to send their Gmail address as well to us just in case.

I think that many of the structures should be similar or matching EQLive with what we have already for SoF. For the ones that are not matching yet, it should be fairly easy to make the needed adjustments to make sure they do match.

Once the tools are on an SVN somewhere that I have access to, I can certainly help to finalize any structure or opcode issues that might remain. I am getting good at that stuff :P

It is going to be awesome to get this stuff working again. I have really been dreading trying to do SoF AAs all manually from ShowEQ packet logs. Once the tools are working again fully, collecting the AA information should only take me an hour or so to log in each class and collect and then convert them into the table. Then, I am sure there will need to be some cleanup done to finalize it, but that is much easier than the part of converting each packet manually into a database entry!