Is there any reason why the default.pl couldn't be used like I mentioned to make all of the pet stuff work with 1 simple script? I posted an example. Maybe there is something I am not thinking about. Here it is again:
default.pl Code:
sub EVENT_SPAWN { |
because the player burns the mana for casting the pet if you do it that way.
|
Ahh, I see. There is probably a way to correct that (at least most of the way) by using some of the following commands:
GetActSpellCost(spell_id, cost) CastingSpellID() GetMana() GetMaxMana() SetMana(amount) But most likely it would take a sub EVENT type to allow what you would be needing to do. A sub EVENT_CASTING would do the trick I think. That and/or a new function that could actually check certain fields of the spell table and get their values would be sweet. Then, you would just check for those type of spells and do an interrupt on them if they are cast. Then, you would just use the new command to do what you were wanting to do in the first place with this line: Quote:
|
I think adding the new sub EVENT is the hassle, so I added the spells to the blocked_spells table instead.
|
All times are GMT -4. The time now is 10:04 AM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.