Classic or era-based server content

[mgellan]

Originally Posted by provocating

I am not source control expert but I do not think this is viable. My source has gotten further and further custom. You have to think the current EqEmu source has code for instancing, AA's (cannot completely remove), bots, mercs, etc. Do you really want to keep all of that in there if it is not needed?

Stripping code out by actually physically removing it is silly - better to have a compiler directive to just not compile that code in versus removing it. P99 have removed AA code - how can they do AAs now without laboriously reinserting the code? That being said I expect that the coders who are trying to get as close to Live as possible would be saying "No fucking way, keep that classic shit out of the code, it's complicated enough"

At the same time, if necessary I'd fork the code, keep applying updates and not change much so the code doesn't become so totally different than the main code base so as to preclude applying reasonable updates that would be useful in possible future expansions...

Regards,
Mg

[provocating]

Well we have two different directives. My code will never go past Velious.

[AdrianD]

I suspect we need to coordinate an approach

Yes, yes.

1. Start with the current rev of eqemu and keep any changes required to "classic-ify" the code parameter driven and checked into the main code base so we're not creating a fork that will never get merged back into the main project.

I agree. What we do to customize our servers is our prerogative. My thought on this is to have a base for those interested in classic/progression.

[AdrianD]

2. Start with a current rev of PEQ and just create SQL patches to apply that if run sequentially will result in a "classic-ify'd' database.

I have done some of this as good as I can. I haven't gone as far as getting things proper on a patch to patch timeline.

3. Quests - open question, probably need to fork these entirely since I doubt any fixes made to quests are intended to revert them to classic.

Currently, with the sqls I have created, any quest npcs which are not part of a certain expansion will not be present in the table `npc_types`. Items which are not part of a certain expansion will not be present in the table `items`. This will effectively disable the quest in many circumstances.

Of course, there are npcs and items which are a part of the expansion and they are not accurate. Many other quests, when enabled, may not be accurate to the era. I have only edited a very small portion of quests to reflect the era they were introduced.

......................

I've devised a simple "nomenclature" in the expansion columns I've added to a few tables. Without a full explanation, I've given 50k+ npcs a non-default value and 60k+ items a non-default value. Lot's of work remains, though.

How classic or progression someone wants their server is again, their prerogative. I want to make it so the transition from what is now to something closer to an earlier era is simple. I've done this.

I always wanted to make it so this could be used for new community members. Therefore, I don't make many changes to the actual data. My peq DB is not very different from the guy who started up today.

Many first timers are not capable of making drastic code changes. This includes me. I'm not ready to go down a path where support will be hard to find by branching off from the main community. This is not a goal of mine.

I think it's great to discuss and even plan for the full-range of possibilities. This is why I asked the question.

I do not want to overcomplicate things and drive away support and assistance.

Thanks