Quote:
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.
Quote:
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