Removing Non-Titanium Version Checks

[trevius]

If one of the mods/devs think this should be in code submissions, feel free to put it there. The more I think about it, the more sense it makes that this get set in the source. At least until some real progress is made towards Anniversary Edition or Live.

[rojadruid]

Originally Posted by trevius

If one of the mods/devs think this should be in code submissions, feel free to put it there. The more I think about it, the more sense it makes that this get set in the source. At least until some real progress is made towards Anniversary Edition or Live.

Droping 6.2 will probably not happen. too many people still use it. I myself use it.

[KLS]

6.2 is not getting dropped.

[ChaosSlayer]

how about a line in server ini file to tell server which version to look for, so it don't go looking for all 3 all the time?

all 3 will still be codded in, but it will only be looking for the one specified

[EvoZak]

I thought you HAD to use Titanium? Looks like there is protocol support for other clients. Just code that never got removed, or...?

[ChaosSlayer]

the 6.2 prtocol stil valid for people who had THAT patch to live which existed untill SPECIFIC DAY, and that patch can no longer be obtained by any means - thats why NOW titatium is your only option, but soem peopel stil have 6.2 stashed

[trevius]

Well, leaving 6.2 in is easy enough, but the order can easily still be changed so that it checks for 7.0 first, since that is by far the most common one used.

The code would look like this:

#include "../debug.h"
#include "patches.h"

#include "Titanium.h"
#include "Client62.h"
//#include "Anniversary.h"
//#include "Live.h"


void RegisterAllPatches(EQStreamIdentifier &into) {
	Titanium::Register(into);
	Client62::Register(into);
//	Anniversary::Register(into);
//	Live::Register(into);
}

void ReloadAllPatches() {
	Titanium::Reload();
	Client62::Reload();
//	Anniversary::Reload();
//	Live::Reload();
}

I can certainly understand leaving 6.2 in there for the few that still use it, but at this time I see little need for the Anniversary or Live checks.

So far, I have still noticed 0 issues with having this on my server. I haven't seen any noticeable performance increases either, but it is still too early to tell. I think this change combined with the fix for the "lag bug" may at least help reduce log file sizes as well as maybe a very slight decrease in bandwidth utilization.