Pets disappear when quickly zoning twice #725

Closed
opened 2024-04-12 00:40:35 +02:00 by JulianVallee · 3 comments
JulianVallee commented 2024-04-12 00:40:35 +02:00 (Migrated from github.com)

Describe the bug
Pets are not properly reassigned when quickly zoning twice in a row.

When the second zoning before the pet gets reassigned after the first zoning, there is no pet left to reassign. Not sure about the architecture, but could be a potential memory leak imo.

To Reproduce
Steps to reproduce the behavior:

  1. Summon a pet
  2. Zone to somewhere else
  3. Zone back again before the pet spawns (1-3 secs leeway, Pet XXX reassigned. should not be printed to chat)
  4. Pet is gone

Expected behavior
Pets should not disappear and reassigning should happen correctly.

**Describe the bug** Pets are not properly reassigned when quickly zoning twice in a row. When the second zoning before the pet gets reassigned after the first zoning, there is no pet left to reassign. Not sure about the architecture, but could be a potential memory leak imo. **To Reproduce** Steps to reproduce the behavior: 1. Summon a pet 2. Zone to somewhere else 3. Zone back again before the pet spawns (1-3 secs leeway, `Pet XXX reassigned.` should not be printed to chat) 4. Pet is gone **Expected behavior** Pets should not disappear and reassigning should happen correctly.
RaggyLP commented 2024-04-15 23:43:34 +02:00 (Migrated from github.com)

Confirmed, zoning in the manner described above will remove the pet from the character and not assign a new entity.

Confirmed, zoning in the manner described above will remove the pet from the character and not assign a new entity.
Unknownprk commented 2024-06-28 00:12:40 +02:00 (Migrated from github.com)

Potentially fixed now

Potentially fixed now
RaggyLP commented 2024-06-30 13:38:31 +02:00 (Migrated from github.com)

Re-tested using the 3 main pet classes, this now appears to be fixed! Closing as fixed as of 30/06/24.

Re-tested using the 3 main pet classes, this now appears to be fixed! Closing as fixed as of 30/06/24.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: prk/issues#725
No description provided.