Skip to content
This repository has been archived by the owner on Jan 22, 2025. It is now read-only.

Killaura with range set 3.0 still tries to use reach above 3.0 #856

Open
3 tasks done
celakk1 opened this issue Nov 29, 2024 · 3 comments
Open
3 tasks done

Killaura with range set 3.0 still tries to use reach above 3.0 #856

celakk1 opened this issue Nov 29, 2024 · 3 comments
Labels
status:unconfirmed For issues and PRs that arn't confirmed/reviewed

Comments

@celakk1
Copy link

celakk1 commented Nov 29, 2024

Pre-reporting checklist

  • I have searched existing issues and didn't find any previous reports of this bug.
  • This bug still happens in the latest version of Raven XD. I've made sure my installation is up to date.
  • I have tried removing all other mods and the bug still happens.

Description

Basically, whenever i have killaura Attack Range 3.0 and Block Range 3.0, but my Swing Range is 3.1 and above (doesnt matter how much) it will try to bypass any set reach by me, using reach module also doesnt help.
Changing raycast modes, rotation and autoblock does not do anything.
turning on and off butterfly clicking also doesnt do anything.

Repro steps

  1. set Attack Range and Block Range to the same range ex. 3.2
  2. set Swing Range that is bigger than both attack range and block range ex. Attack & Block Range 3.2, Swing Range 3.3+
  3. turn on killaura

Raven XD version

2.11, 2.12

Crash report (if applicable)

No response

@celakk1 celakk1 added the status:unconfirmed For issues and PRs that arn't confirmed/reviewed label Nov 29, 2024
@Kefpull
Copy link

Kefpull commented Dec 2, 2024

can you post your config? For some reason for me killaura reach does not work at all, it's locked to 3.0 blocks on raycast strict

@celakk1
Copy link
Author

celakk1 commented Dec 2, 2024

clkBMCcfg.json

its made for blocksmc and isnt publicly posted currently

@xia-mc
Copy link
Owner

xia-mc commented Dec 6, 2024

can you post your config? For some reason for me killaura reach does not work at all, it's locked to 3.0 blocks on raycast strict

Yes, the reach amount will always be 3.0 when raycast 'strict'

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status:unconfirmed For issues and PRs that arn't confirmed/reviewed
Projects
None yet
Development

No branches or pull requests

3 participants