View Issue Details

IDProjectCategoryView StatusLast Update
0017610Return of ReckoningGeneralpublic2023-12-09 15:17
ReporterReturnOfReckoning Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionopen 
Summary0017610: When attempting to cast Rune of Adamant out of range, the rune is placed at last spot when the cusor was in range
DescriptionReporter: aaearon

<!--
Issues should be unique. Check if someone else reported
the issue first, and please don't report duplicates.
Only ONE issue in a report. Don't forget screens or a video.
-->

**Expected behavior and actual behavior:**

When attempting to place the Rune outside of it's range (80 ft), the expectation is that a message should be returned saying something like the target position is out of range. What actually happens is that the Rune is casted and placed at the last spot the cursor was in range at.

**Steps to reproduce the problem:**

Press the ability to bring up the placement indicator first within the 80 ft range. Then move the cursor outside of 80 ft range and press it again the place the Rune. No error message regarding target position range is given, instead the rune is placed at the last position the cursor was at within the 80 ft range.

**Testing Screenshots/Videos/Evidences (always needed):**
<!-- Drag and drop an image file here to include it directly in the bug report,
     no need to upload it to another site -->
Here you can see the placement indicator is at the last spot within the 80 ft range.
![image](https://user-images.githubusercontent.com/812640/91038778-a413a100-e60b-11ea-8b05-65e0ac390635.png)
Here you can see that the Rune was placed at the last spot within the 80 ft range when I cast it. Instead I should receive a target position out of range message.
![image](https://user-images.githubusercontent.com/812640/91038873-d02f2200-e60b-11ea-9277-a6d734b4c035.png)

<!--
Note that game critical and game breaking bugs may award a manticore/griffon (realm specific) at the leads discretion however, asking for one instantly disqualifies you from this reward.
-->
TagsAbility

Activities

ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:17

reporter   ~0032881

Commenter: aaearon

I was able to reproduce this on my Zealot with Ritual of Lunacy.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:17

reporter   ~0032882

Commenter: Sandrasfanat

Same bug with BW rain of fire
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:17

reporter   ~0032883

Commenter: CrimsonFenris

I got somehow similar issue, but it's more **attempting to cast a master rune slightly out of range returns an error message, starts the cooldown timer on the spell, and rune is not cast** (maybe it's related and cast at last position, but usually the spell is simply wasted and goes on cd without effect).
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:17

reporter   ~0032884

Commenter: aaearon

What you experience is also what I reported in https://github.com/WarEmu/WarBugs/issues/17611. It was closed and referenced this one. I guess the idea is that the fix to this issue might apply to what was closed but I think the issues are separate albeit similar.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:17

reporter   ~0032885

Commenter: Tyramissoux

Ritual going on cooldown, when targeting an out of range spot, occurs when you're moving. Other ritual should be on also on CD then but isn't. (result: see screenshot)

![image](https://user-images.githubusercontent.com/13544944/94475052-d39b6780-01ce-11eb-8fea-480897c64054.png)

If you're standing still, the last cursor position is used for placement (which is fine).
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:17

reporter   ~0032886

Commenter: aaearon

Why do you consider using the last cursor position for placement fine? It should give the same target position out of range message and not cast at all.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:17

reporter   ~0032887

Commenter: Tyramissoux

> Why do you consider using the last cursor position for placement fine? It should give the same target position out of range message and not cast at all.

It was the behaviour from live and actually it is helpful. Imagine being in a stressful situation, you want to place your ritual quickly but it is slightly out of range. With this "bug", it is placed close to the position you wanted but still in range, without it, you have to cast again.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:17

reporter   ~0032888

Commenter: aaearon

I do not find "same behavior from live" as a compelling reason to keep it the same. The problem I find is that many times it is NOT close to the position I want. The range to cast the rune/ritual is 80 ft and the range of the rune/ritual itself is 100ft. This bug can make it so the rune/ritual is in a position totally away from the fight and hitting no one. Also, "casting it again" is a non-issue as if you double click the rune/ritual, it is placed at the location of your cursor. It is not as if you need to move your cursor from where it is, to the action bar to click the rune/ritual, then move your cursor again to where you want to place the rune/ritual and then left click.
MaxHayman

MaxHayman

2023-12-09 15:17

administrator   ~0041076

This issue is being closed as it should be fixed in the new ability system. Please create a new issue if this is not the case.

Issue History

Date Modified Username Field Change
2023-08-13 04:17 ReturnOfReckoning New Issue
2023-08-13 04:17 ReturnOfReckoning Tag Attached: Ability
2023-08-13 04:17 ReturnOfReckoning Note Added: 0032881
2023-08-13 04:17 ReturnOfReckoning Note Added: 0032882
2023-08-13 04:17 ReturnOfReckoning Note Added: 0032883
2023-08-13 04:17 ReturnOfReckoning Note Added: 0032884
2023-08-13 04:17 ReturnOfReckoning Note Added: 0032885
2023-08-13 04:17 ReturnOfReckoning Note Added: 0032886
2023-08-13 04:17 ReturnOfReckoning Note Added: 0032887
2023-08-13 04:17 ReturnOfReckoning Note Added: 0032888
2023-12-09 15:17 MaxHayman Note Added: 0041076
2023-12-09 15:17 MaxHayman Status new => closed