Spawns showing as triggers

nightgod · Post by **nightgod** » Wed May 12, 2004 1:42 am

JUSt downloaded and recompiled and I am still getting some regular spawns showing as triggers, specifically in sncrematory-no rhyme or reason to it, and didn't happen in other zones tonight.

Lax · Post by **Lax** » Wed May 12, 2004 1:50 am

can you please be more specific?
no shit it didnt happen the other night, because shit wasnt being correctly identified as triggers.

Code: Select all

10 May 2004 by Lax:
- Fixed problem relating to false negatives determining if a spawn is a TRIGGER (e.g. flavor
  text, trap, etc).  This solves crash issues in the latest zip with the custom caption
  system.  This also solves non-crash issues identifying "invisible spawns" in spawn searches,
  as well as spawns that were previously identified as NPCs in MQ2Map.

what mobs in what zones
Target them and see what body type they have (/echo ${Target.Body} )

If the body type says UNKNOWN BODYTYPE it will be identified as a trigger.

nightgod · Post by **nightgod** » Wed May 12, 2004 2:00 am

A sewer gnat
A decaying slimesnipper
An acid larvae
A muck-covered fly

In sewers in GoD (crematory to be precise)

All showing as UNKNOWN BODYTYPE

Didn't mean it didn't happen the other night, I meant it didn't happen earlier tonight in other zones.

Lax · Post by **Lax** » Wed May 12, 2004 2:08 am

k unfortunately I cant test on those

Get the body type IDs for me

${Target.Body.ID}

and I'll see what else I can drum up for detecting triggers.

nightgod · Post by **nightgod** » Wed May 12, 2004 2:18 am

bah...they quit out of the expedition and I got booted before I got any IDs LOL-will get you some next time I run into it.

nightgod · Post by **nightgod** » Wed May 12, 2004 2:21 am

OK, were a couple of them in Barindu-they gave back an ID of 0

Lax · Post by **Lax** » Wed May 12, 2004 3:29 am

Okay, I found the ones in Barindu for testing. This issue should be fixed for the patch update.

Some Guy · Post by **Some Guy** » Wed May 12, 2004 7:13 pm

Having this issue in other areas.
Some dragons are showing up as UNKNOWN BODYTYPE, with an ID of 29.

Lax · Post by **Lax** » Wed May 12, 2004 7:19 pm

ok, I'll fix that, let me know of any others

MacroFiend · Post by **MacroFiend** » Wed May 12, 2004 7:57 pm

I don't know how curent this is ... but EQEmu has bodytypes 11 and 60 set to non-targetable spawns.

TheUnholy · Post by **TheUnholy** » Wed May 12, 2004 10:22 pm

I noticed wizard's familiars showing up as triggers on the map proceeded with a #. also a vast amount of npc pets (shadowknight mobs with their skeleton pets) showing up marked as triggers. newest zip, was about 30 min ago (10:22pm est here)

Lax · Post by **Lax** » Wed May 12, 2004 10:30 pm

If you find issues like this, TARGET whatever it is, type "/echo ${Target.Body.ID}"
Record what it is specifically (wizard's pet, whatever), and this number. Report it to me and it will get fixed.

Lax · Post by **Lax** » Wed May 12, 2004 11:39 pm

Note: Many "named" npcs that are untargetable *ARE* triggers, people are just finding this out because /who doesnt show some of them now. I'm changing /who so that if you supply ANY parameters, the "invis" option is implied.

s16z · Post by **s16z** » Wed May 12, 2004 11:54 pm

Kael:
Derekor the Vindicator - Body.ID = 9

Lair of Terris Thule:
Sentry of Nightmares Pet - Body.ID = 8

Couple other, like burrower in The Deep, and Manaetic Behemoth in PoI, but didn't get IDs at the time.

MSMage · Post by **MSMage** » Thu May 13, 2004 12:59 am

Lord Inquisitor Seru = ID 16
Now how long would that one have taken to find? lol