The Top 4 Most Depressing Facts about the Titanium Client

[a_gnoll_pup]

bump for classicness.

just gauging interest to see how many people would be willing to contribute.

I've recently began work on merging the capability for having both EQ Titanium and EQMac's windows client (The one that Secrets/Rogean made) working together in unison.

So far I have converted the EQStreamInterface interface to support both EQStream and EQOldStream, a new class I made to support packet handlers with the old client. It will make a new stream depending on what kind of client is connecting, the first packet identifies the stream type, the first opcode identifies the 'patch' (ie; Mac, Trilogy, etc) just like EQEmulator does to support multiple clients at the moment.

The EQOldStream class is based heavily off of EQClassic's work of a packet parser implementation from their public release, but made into an interface that can plug in to EQEmulator and thus use their patch system.

There's a crash issue with it so if anyone is good at debugging multithreaded networking applications I would appreciate the help. The mac client is identified in the stream now, but nothing past that. I used Visual Leak Detector to make sure that the new class does not leak memory, so far that's turning up just fine, so it's something else.

If anyone is interested (and is a programmer) in contributing to this project that Project 1999 could potentially use someday to support both the Titanium and classic-era clients at the same time, I'll put it on Github as a fork of EQEmu. I'm not going to want to do this alone, but I will if I have to. This project will be entirely open source and potentially be merged into EQEmulator's main branch for all servers to use when it's all said and done.

Yes, this means this functionality will work on EQClassic's client if it ends up getting finished after the Mac client is completely done and working, for those who are wondering. It also will support all of EQEmulator's functions (Perl/Lua parsers) up to the era for the client you plug into it.

[Halius]

Originally Posted by a_gnoll_pup [You must be logged in to view images. Log in or Register.]

bump for classicness.

just gauging interest to see how many people would be willing to contribute.

I've recently began work on merging the capability for having both EQ Titanium and EQMac's windows client (The one that Secrets/Rogean made) working together in unison.

So far I have converted the EQStreamInterface interface to support both EQStream and EQOldStream, a new class I made to support packet handlers with the old client. It will make a new stream depending on what kind of client is connecting, the first packet identifies the stream type, the first opcode identifies the 'patch' (ie; Mac, Trilogy, etc) just like EQEmulator does to support multiple clients at the moment.

The EQOldStream class is based heavily off of EQClassic's work of a packet parser implementation from their public release, but made into an interface that can plug in to EQEmulator and thus use their patch system.

There's a crash issue with it so if anyone is good at debugging multithreaded networking applications I would appreciate the help. The mac client is identified in the stream now, but nothing past that. I used Visual Leak Detector to make sure that the new class does not leak memory, so far that's turning up just fine, so it's something else.

If anyone is interested (and is a programmer) in contributing to this project that Project 1999 could potentially use someday to support both the Titanium and classic-era clients at the same time, I'll put it on Github as a fork of EQEmu. I'm not going to want to do this alone, but I will if I have to. This project will be entirely open source and potentially be merged into EQEmulator's main branch for all servers to use when it's all said and done.

Yes, this means this functionality will work on EQClassic's client if it ends up getting finished after the Mac client is completely done and working, for those who are wondering. It also will support all of EQEmulator's functions (Perl/Lua parsers) up to the era for the client you plug into it.

Somebody help this guy out! I am not a programmer so I can't help you at all but I think it would be great if EQMac's client could be used here, then you could choose between classic (for those that want complete nostalgia), or velious/pop. Appreciate the work you are doing to get this working!

[t0lkien]

I don't know. I'm all for classic rules, but forcing classic UI is overkill IMO. p99 will lose a lot of players who just hated it and get pissed off at being forced to use it. It's a little ADD IMHO.

[a_gnoll_pup]

Originally Posted by t0lkien [You must be logged in to view images. Log in or Register.]

I don't know. I'm all for classic rules, but forcing classic UI is overkill IMO. p99 will lose a lot of players who just hated it and get pissed off at being forced to use it. It's a little ADD IMHO.

This is why the EQMac client is so wonderful. It supports both the Planes of Power UI, Velious UI, and Classic UI with a boolean flag to turn the new UI on or off. It's also DirectX 8 which means a LOT of things would be fixed and extra functionality would be awesome. Titanium would still be an option, too, with the setup.

[heals4reals]

Notice the AC and ATK caps in OP. That implemented here?

[Nirgon]

Someone started work on a classic UI here. IMO that work just needs to be finished and the use of the UI to be mandatory, similar to the spell file. However, the implementation imo would be that your char is frozen until you /load those UI files. Probably a Secrets secret fix.

[Nirgon]

Last thing I tried helping with involved using a hex editor to make pixels fly.

Homie don't play hex editors.

[Stinkum]

Originally Posted by Halius

Somebody help this guy out! I am not a programmer so I can't help you at all but I think it would be great if EQMac's client could be used here.

[Nirgon]

I'd add that the interest would be P99 *requiring* use of the Velious and classic UI and that this could be branched server code to determine which for Nilbog's timeline.

I'd like to see if it could require the original UI up to Velious and then the Velious UI some time into Velious (I don't think it was a day 1 change?).

[Halius]

Originally Posted by Nirgon [You must be logged in to view images. Log in or Register.]

I'd add that the interest would be P99 *requiring* use of the Velious and classic UI and that this could be branched server code to determine which for Nilbog's timeline.

I'd like to see if it could require the original UI up to Velious and then the Velious UI some time into Velious (I don't think it was a day 1 change?).

I think this would be a good idea, only problem is people that are used to custom UIs at this point would probably hate this idea considering the server has been open for so long already.