Go Back   EQEmulator Home > EQEmulator Forums > Development > Development::Bug Reports

Development::Bug Reports Post detailed bug reports and what you would like to see next in the emu here.

Reply
 
Thread Tools Display Modes
  #1  
Old 10-19-2008, 04:09 PM
janusd
Sarnak
 
Join Date: Jan 2008
Posts: 47
Default Pc Hatelist and pets

After the changes to the PC hatelist, pets seem to be somewhat bugged from how they're supposed to work. Originally, with my pet, I could target a mob and tell my pet to attack it and regardless of where my pet was, it would recieve the order and move to attack. Now, my pet has to be within a certain range of the mob, regardless of my own range to the mob. Aside from creating small issues in using pets, this is potentially exploitable.

I think this issue largely arises from the recent client hatelist changes in that a pet originally would get its hatelist from the client's hatelist.

Also, when using a pet, were mobs hitting me, the pet, once done with one mob, would default to the next mob on my hatelist that had been hitting me. Now I have to actively tell the pet to attack before it will.
Reply With Quote
  #2  
Old 10-20-2008, 12:43 AM
AndMetal
Developer
 
Join Date: Mar 2007
Location: Ohio
Posts: 648
Default

I think it was part of this change in Revision 108 in SVN:
Quote:
==10/17/2008
KLS: Tweaks to /pet attack
zone/attack.cpp diff:
Code:
@@ -4999,7 +4999,7 @@
 		if (mypet->IsFeared()) break; //AndMetal: prevent pet from attacking stuff while feared
 
 		if((mypet->GetPetType() == petAnimation && GetAA(aaAnimationEmpathy) >= 2) || mypet->GetPetType() != petAnimation) {
-			if (mypet->GetHateTop()==0 && target != this && DistNoRootNoZ(*target) <= (RuleR(Pets, AttackCommandRange)*RuleR(Pets, AttackCommandRange))) {
+			if (target != this && mypet->DistNoRootNoZ(*target) <= (RuleR(Pets, AttackCommandRange)*RuleR(Pets, AttackCommandRange))) {
 				mypet->SetHeld(false); //break the hold and guard if we explicitly tell the pet to attack.
 				mypet->SetPetOrder(SPO_Follow);
 				zone->AddAggroMob();
I'm not sure what the intention was behind the change (KLS usually makes those changes for a good reason), although I think we might need more of a Line of Sight check rather than a distance check.
__________________
GM-Impossible of 'A work in progress'
A non-legit PEQ DB server
How to create your own non-legit server

My Contributions to the Wiki
Reply With Quote
  #3  
Old 10-20-2008, 02:29 PM
KLS
Administrator
 
Join Date: Sep 2006
Posts: 1,348
Default

Good point there should also be a distance check to the pet. There's no los check on live so I'm not adding one here. The default pet attack range also feels like it needs increasing.
Reply With Quote
  #4  
Old 10-20-2008, 03:28 PM
janusd
Sarnak
 
Join Date: Jan 2008
Posts: 47
Default

Yes it does, KLS. On Live, the raige was pretty fairly large (not insane like 400, but closer to 150 I'd say. Maybe 200)
Reply With Quote
  #5  
Old 10-20-2008, 05:33 PM
joligario's Avatar
joligario
Developer
 
Join Date: Mar 2003
Posts: 1,498
Default

Pet distance was already defaulted to 150 on TGC from what I remember. I think 200-250 might be better.
Reply With Quote
  #6  
Old 10-20-2008, 10:25 PM
janusd
Sarnak
 
Join Date: Jan 2008
Posts: 47
Default

If it's set at 150, then it should be about 250. Never tested the actual range on PEQ.
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

   

All times are GMT -4. The time now is 11:51 PM.


 

Everquest is a registered trademark of Daybreak Game Company LLC.
EQEmulator is not associated or affiliated in any way with Daybreak Game Company LLC.
Except where otherwise noted, this site is licensed under a Creative Commons License.
       
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Template by Bluepearl Design and vBulletin Templates - Ver3.3