proposition for a new NPC special

[ChaosSlayer]

As you know "W" in npc special means that you need magic weapon to attack it. IN Db there is a line which determines when pets get magic attack.
I belive this also defaults to mobs.

However what I propose, is that instead of making this universal set a new special letter which will determine on a single mob bases if they posses a magical weapon. (since pets also defined in npc tables, this will be true for them as well)

this will grant ability of great variation in designing mobs and pets. Instead of ALL pets automaticly having magic attack at level X - you can make it so that only certain types of them do. For exmaple for mage - imagine that Earth pet while the strongest - does not have a magic attack, while air pet does (but much much weaker) - this means that earth pet would great vs normal mobs, but cannot be used againt magic only mobs.

this is just single exmaple of how can this feature can be used, but I can think of many scenarios (including mobs as well) where this could help in creating custom content (think of a quest where 1 group of NPC fights another group of NPC and is unable to to hit them, and your job would be go around and give the first group magical weapons)

simular flag could be implemented to allow mob/npc/pet to hit Bane only creatures

[ChaosSlayer]

I decided to bump this to see if perhaps I could get an official opinion from some of our devs

once again in short the idea to implement a special flag which will be set on mob to mob specific case if such mob/npc/pet posses a Magical Weapon (preferably an additional separate flag to overcome Bane restriction)

thank you for your time

[AndMetal]

My concern about your scenario is that, if you give someone a magic weapon, they can hit. So, why not just carry around a magical weapon (or summon one) for your pet?

There is already a rule, Combat:PetAttackMagicLevel(30), that gives pets magical attacks at level 30 by default. You could always increase that to something like 100, and they shouldn't get it unless the pet is level 100+. Then, you could figure out a way to get a magical weapon for that particular pet (player quests, modify spells_us.txt to summon an item, etc).

[ChaosSlayer]

Originally Posted by AndMetal

My concern about your scenario is that, if you give someone a magic weapon, they can hit. So, why not just carry around a magical weapon (or summon one) for your pet?

There is already a rule, Combat:PetAttackMagicLevel(30), that gives pets magical attacks at level 30 by default. You could always increase that to something like 100, and they shouldn't get it unless the pet is level 100+. Then, you could figure out a way to get a magical weapon for that particular pet (player quests, modify spells_us.txt to summon an item, etc).

well that depends on how your server set up. on my server I plan to have magic weapons to be ULTRA RARE and non summonable. it would be a major waste to give them to pets.

Another thing - even with given weaposn you won't be able to achive a condition where one pet can always hit magic while other can never hit magic - since weapon can be given to both pets just as easily breaking the system I am intent to set up


also this does not adress problem with NPCs: if I want to specificly make npcs who will or will not be able to hit magic - specialy if for exmaple some of player pets are set to be immune to non-magic weapons

So even if pets can be wroked around with current system, there is no way to enforce or prevent NPCs from having magic weapons by choice

[steve]

You can't expect the project to add code specific rules/conditions for things that just you 'might possibly' use on your server. Most people are running live-like servers, with very few differences from live.

Customization and more options is always nice, but I think this would be at the very bottom of the priority list, right after getting the project caught up to Live (if that ever even happens).

[ChaosSlayer]

Originally Posted by steve

You can't expect the project to add code specific rules/conditions for things that just you 'might possibly' use on your server. Most people are running live-like servers, with very few differences from live.

Customization and more options is always nice, but I think this would be at the very bottom of the priority list, right after getting the project caught up to Live (if that ever even happens).

those things gets added all the time at devs vim
and as a matter of fact most people running custom content
and cathign up with LIVE wise- half of features I propose has been allready long implemented on LIVE in expansions beyond T.