Mobs warp when rooted #591

New issue

Closed

opened 2024-02-01 03:41:25 +00:00 by TheTinkeringIdiot · 2 comments

TheTinkeringIdiot commented

2024-02-01 03:41:25 +00:00

(Migrated from github.com)

Describe the bug
When rooted, mobs warp to their attack target after a short time. The target halts immediately when the root lands, but after ten seconds or so immediately leaps to its fighting target. The root remains in effect and the mob cannot move other than this warping.

This may be related to #347 pathing issues, as moving around a rooted mob causes it to warp to where you were a few seconds ago, much like how pets commanded to follow run toward your location at the time the command was given.

To Reproduce
Steps to reproduce the behavior:

Target a hostile mob
Cast and land a root nano
Move out of the mob's combat range
Wait about ten seconds
The mob warps to you and its status (/set debug 1) changes to "Fighting"

Expected behavior
A rooted mob should not move at all.

**Describe the bug** When rooted, mobs warp to their attack target after a short time. The target halts immediately when the root lands, but after ten seconds or so immediately leaps to its fighting target. The root remains in effect and the mob cannot move other than this warping. This may be related to #347 pathing issues, as moving around a rooted mob causes it to warp to where you were a few seconds ago, much like how pets commanded to follow run toward your location at the time the command was given. **To Reproduce** Steps to reproduce the behavior: 1. Target a hostile mob 2. Cast and land a root nano 3. Move out of the mob's combat range 4. Wait about ten seconds 5. The mob warps to you and its status (`/set debug 1`) changes to "Fighting" **Expected behavior** A rooted mob should not move at all.

RaggyLP commented

2024-02-17 22:07:02 +00:00

(Migrated from github.com)

Wasn't able to repo this. Can you re-test @TheTinkeringIdiot? Might've been fixed in passing.

Wasn't able to repo this. Can you re-test @TheTinkeringIdiot? Might've been fixed in passing. ![image](https://github.com/project-rubika/issues/assets/156821187/f2663788-af4e-4714-8b6f-000d9659eeed)

TheTinkeringIdiot commented

2024-02-18 02:25:15 +00:00

(Migrated from github.com)

Yep, looks like this was fixed by the recent changes. Closing as fixed.

No milestone

No project

No assignees

1 participant

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#591

No description provided.

Rows
Columns