The Top 4 Most Depressing Facts about the Titanium Client

[Elizabetha]

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

Yeah, read about that thing with EQClassic, but from the replies in that thread I got the impression that Yeahlight would still finish the project and there was the glimmer of possibility he'd give it to someone else to host. One can dream.

Greater Faydark was always pitch black too, even with elf vision I remember getting lost in the dark. When I first got my Mask of Deception it got me killed more than once because I was always using it for Ultravision.

As a dwarf, I had some vision ability, but I didn't know how to configure my video properly early on. I remember my first trip to Kelethin. I spotted someone with a lantern headed that way and I asked if I could follow him. Hehe. I remember being scared shitless.

[Ele]

Classic vendor windows. Clicking every item to find out price.

[You must be logged in to view images. Log in or Register.]

[Elizabetha]

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

Classic vendor windows. Clicking every item to find out price.

[You must be logged in to view images. Log in or Register.]

Holyomigod I forgot about that completely!

Now you've unblocked memories of tradeskilling with that stupid slider... not being able to type in how many of a stack you want to pick up! Or even click left or right by one!

/e runs away screaming.

[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.

[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?

[Potus]

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

Yeah, as a Barbarian running from Permafrost to Blackburrow and back the tunnel between the two zones was a total nightmare. I don't care how high you cranked up the Gamma. [You must be logged in to view images. Log in or Register.]

Yup exactly. It was super scary as a young Barbarian to run anywhere. Plus vision items had a purpose.

I also miss the char mirror [You must be logged in to view images. Log in or Register.]

[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.

[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!