Enemy OM Data

[pacampbell]

When monsters respawn, it seems destructible parts state is not cleared. It is suspected this is an issue related to "OM" data. The task involves looking through all the existing handlers for the group 13 (INSTANCE) packets and double check to see if what was implemented makes sense.

During a quick observation, one such handler which immediately sticks out is the handler for EXCHANGE_OM_INSTANT_KEY_VALUE. There is an NTC sent during this req/res but the NTC is only sent to the requestor and not other members in the party. There may be similar instances of this in other instance handlers related to OM state.

There also are a few unknown/unimplemented NTC packets around the same location as other INSTANCE/OM packets related to enemies. It may be that one of these needs to be used.

• S2C_INSTANCE_13_35_16_NTC
• S2C_INSTANCE_13_36_16_NTC
• S2C_INSTANCE_13_37_16_NTC
• S2C_INSTANCE_13_38_16_NTC

Finally there is a curiously named NTC called S2C_INSTANCE_ENEMY_BREAK_REGION_NTC which currently is not used.

[pacampbell]

Found the issue with the destructible parts. There was context information associated with the party which was not getting cleared when the instance was reset. We should still chase some of these OM instant packet handlers though.