Brainstorming: Partial DB Standard
Greets all. I just wanted to throw down a brainstorm that I have many many months ago and see what people think the Pros/Cons are.
Since EQEmu is an open-sourced application, users can do pretty much whatever they want with any bit or byte they want. This has lead to the segregation of efforts in many different facets of the project, namely NPCIDs, Items and Quests. These three categories represent the largest portion of the database and thus the largest point of segregation. Granted, people have migrated towards consolidating DB's and we have never really had more than 3 or 4 mainstream DB distros out at any given time... this is a good thing, sort of.
I know I have spoken on these boards before about centralization of data and efforts pertaining to the EQEmu effort and have been met with very good insight from others. Here is a refined version of my thoughts:
Standardize certain portions of the database. For instance: 'Reserve' the first 250,000 NPCID's for EQLive-like mobs. Any custom created content *should* start at 250,001. Enact a similar reservation for ITEMID's, NPC types, factions etc. This should allow for the seamless creation of a Npc, Item and Quest set that would work 'right out of the box.' Also, people can offer up their custom DB mods to the public and be able to state:
"This add-on uses NPCID 300000-310000, ITEMID 300000-310000, blah blah blah"
This will allow serverops to see where/if this mod can fit in to their db. Additionally, as long as the db mod is totally self related or related to itself and the 'base' DB, then a serverop can just use a script and bulk change the NPCIDs/ITEMIDs/etc into a range that will fit on his/her server.
All the numbers I used in my example are trivial as its the concept that I would like to discuss. To answer the obvious: Yes I know this is potentially a HUGE effort and NO it won't mandatory, just standardized.
Aight, open floor! Questions, comments, concerns, ideas?
__________________
GM/ServerOP - Shadows of Norrath
|