Mobs and loot

[Argo]

Gentlemen,
my problem: in nearly every region/zone we got mobs with identical name but diffrent level, for example decayed zombie in camelot hills and decayed zombie in Avalon Marsh. Those in AM are ofcourse much higher in level than in CH. What's bothering me is that if you assign loot to the decayed zombie in CH then the decayed zombie in AM has exactly the same low level loot as his counterpart in CH. That is very irritating, don't you think so?

My idea: what if we would add to the Itemtemplate table a column named zone (which holds all the zones in a region). I don't know where the according code is for the lootdrops but if we would say inside the code, if you are a decayed zombie from zone x then drop only the loot that is assigned for you from this zone.

That way we could assign to mobs with identical names but diffrent zones, diffrent loot. If i could, i would code it but to be honest, i am a DB man not a coder Anyone up for it?

kind regards
Argo

[Graveen]

Argo, actually, the loot is processed versus the mob table or the npctemplate table ?

I think we should instead base loot on npctemplate_id instead of mob_id. The level of a mob is a strong differenciator (i mean, identical mobs with different levels are diffrent mobs).

This is effectively something to dig around, but i think pushing region into itemtemplate is very restrictive.

[Argo]

I think we should instead base loot on npctemplate_id instead of mob_id

That's exactly why i need you Coding Guys I didn't think of that at all. But instead of refering to npctemplate_id which is a unique identifier in npctemplate, we should refer to npctemplateid in mob, which holds the templateid from npctemplate. If you take a look at the npctemplate table you will see that a templateid will occur more often, holding all the looks, genders etc... where there is the npctemplate_id only once since it is a primary key.

To make a long story short, if we could do it that way we would winn a lot.

kind regards
Argo

[Graveen]

I'll try to free some time on friday ! /bow !

[Argo]

Thanks Graveen. i will fill the table then with the necessary loot data

[Argo]

a little 'remember me' bump

[Graveen]

It is ok. I only changed MobxLootTemplate table, not MobDropTemplate (not used on Storm).
In case the mob is coming from an NPCTemplate, the NPCTemplateID is used to find the loot table attached (MobXLootTemplate.MobName must contain NPCTemplateID, so a number). If the mob is not templated, its name is used.
If the mob have both, the code is trying to load NPCTemplateID loot table (and use it) then if not found, Mob.Name loot table: loot tables are NOT merged in one unique table.

This should allow total compatibility.

[Argo]

I am a bit confused now,
mobxloottemplate holds:
Mobname (NPCTID) Loottemplatename (Mobname or ItemTemplateID?) Dropcount (this is clear) and the MobXLootTemplateID (Unique key)

Loottemplate holds:
Mobname, ItemtemplateID, Chance, Count and Loottemplateid

How do i put these two tables in relationship with eachother?

NPCT 12406 and NPCT 11000 can bot be a Water elemental one in ava marsh with level 36, the other in camelot hills with level 5. in the table Loottemplate both are named water elemental, so how does daoc know on which mob to put the right loot?

I am more than confused

kind regards
Argo

[Graveen]

MobName: NPCTID *or* Mob name
LootTemplateName: the name of the loot template, as it appears in LootTemplate table (this is generally the mob name, but this is only a key, so you put whatever you want)

You confusion comes you think LootTemplate.TemplateName is refering directly the mob name, but it refers in fact the MobXLootTemplate.MobName entry.