|
|
 |
 |
 |
 |
|
 |
 |
|
 |
 |
|
 |
|
Support::Packetcollector Any PacketCollector related problems or questions should be posted here. |

06-01-2010, 02:56 PM
|
 |
The PEQ Dude
|
|
Join Date: Apr 2003
Location: -
Posts: 1,988
|
|
Sorry to keep being a bother, but checking Zones Points and Zone Config outputs the entries commented out. Any chance that can be changed?
Also, how difficult would it be to add an option to UPDATE npc_types instead of INSERT? If checked, the SQL may look like:
Code:
UPDATE npc_types set field1 = $field1, field2 = $field2 where name = $name and id >= @StartingNPCTypeID and id <= @StartingNPCTypeID + 999;
That would help me to use new collects to update already built zones, since you've added proper texture and face parsing! Of course, the default option should probably create INSERTS for new zones
I can't thank you enough, this seriously is the best parser EQEmu has ever seen! My hope is the next version of the PEQ database will have every zone supported by our client at least spawned with doors, objects, fog, etc.
|

06-01-2010, 03:05 PM
|
 |
Administrator
|
|
Join Date: Feb 2009
Location: MN
Posts: 2,072
|
|
Quote:
Originally Posted by cavedude
Sorry to keep being a bother, but checking Zones Points and Zone Config outputs the entries commented out. Any chance that can be changed?
Also, how difficult would it be to add an option to UPDATE npc_types instead of INSERT? If checked, the SQL may look like:
Code:
UPDATE npc_types set field1 = $field1, field2 = $field2 where name = $name and id >= @StartingNPCTypeID and id <= @StartingNPCTypeID + 999;
That would help me to use new collects to update already built zones, since you've added proper texture and face parsing! Of course, the default option should probably create INSERTS for new zones
I can't thank you enough, this seriously is the best parser EQEmu has ever seen! My hope is the next version of the PEQ database will have every zone supported by our client at least spawned with doors, objects, fog, etc.
|
Should be an option between Insert and Update really.
|
 |
|
 |
 |
|
 |

06-01-2010, 03:20 PM
|
Developer
|
|
Join Date: Feb 2004
Location: UK
Posts: 1,540
|
|
Quote:
Originally Posted by cavedude
Sorry to keep being a bother, but checking Zones Points and Zone Config outputs the entries commented out. Any chance that can be changed?
|
I had misread your original request which is why I left them commented out. I've changed it locally and it will be in the next release, which won't be until tomorrow at least.
Quote:
Also, how difficult would it be to add an option to UPDATE npc_types instead of INSERT? If checked, the SQL may look like:
Code:
UPDATE npc_types set field1 = $field1, field2 = $field2 where name = $name and id >= @StartingNPCTypeID and id <= @StartingNPCTypeID + 999;
That would help me to use new collects to update already built zones
|
I assume that if the option to generate UPDATEs like that is selected, then you wll also not want the INSERTs generating for the spawn tables ?
Finally, you are not being a bother at all. Of anyone, you know best as to how a tool like this needs to work from a user's perspective 
|
 |
|
 |

06-01-2010, 03:24 PM
|
Developer
|
|
Join Date: Feb 2004
Location: UK
Posts: 1,540
|
|
Code:
UPDATE npc_types set field1 = $field1, field2 = $field2 where name = $name and id >= @StartingNPCTypeID and id <= @StartingNPCTypeID + 999;
I've just thought of an issue with this. What about the case where multiple mobs exist with the same name with different attributes (level, hp, possibly other attributes) ?
Do you only want a selected number of fields included in the update, like face, texture, etc ?
|

06-01-2010, 04:23 PM
|
 |
The PEQ Dude
|
|
Join Date: Apr 2003
Location: -
Posts: 1,988
|
|
Yes, I know in my case if I choose the UPDATE option, I'll only be looking to update the npc_types, and will leave all other options unchecked.
That's a good thought, about NPCs with the same name and different levels or other critical stats. What I am mainly looking for is the appearance data, so yes if the query could be limited to textures, face, the various color and hair columns, armortints, and melee columns, etc that would be ideal! Also, I noticed the Drakkin specific appearance columns aren't parsed, are they not sent? No big deal if not. The data I am working with now is far more detailed than ever!
|

06-01-2010, 04:35 PM
|
Developer
|
|
Join Date: Feb 2004
Location: UK
Posts: 1,540
|
|
Good catch about the drakkin data. I decode it from the packet, just don't include it in the INSERT. I'll include that in the list of things to add.
|

06-01-2010, 05:31 PM
|
 |
Administrator
|
|
Join Date: Feb 2009
Location: MN
Posts: 2,072
|
|
I've only posted TSS and SoD because I felt I had all of the zones. I have quite a few bits and pieces of others
EDIT: Yes Derision I got PoK to work after some trial and error, but there was a dramatic difference which makes no sense but yeah 8 D.
|
Thread Tools |
|
Display Modes |
Hybrid Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -4. The time now is 04:19 AM.
|
|
 |
|
 |
|
|
|
 |
|
 |
|
 |