search

RusherDevelopment / rusherhack-issues

Public repository for reporting issues and suggestions in an efficient manner
74 stars 9 forks source link

AutoCrystal not targetting pre-existing crystals [BUG] #1611

Closed ValkLaz closed 1 month ago

ValkLaz commented 2 months ago

Describe the bug Auto Crystal does not target already placed crystals when it's target > priority is set to damage or damage ratio.

To Reproduce Steps to reproduce the behavior: Reset AutoCrystal config then turn the target priority to damage or damage ratio. Make sure a crystal is already placed near a fakeplayer or enemy.

Other mods List other mods you are using (if any): Meteor Client, Sodium, Nvidium, Lithium, ViaFabricPlus

Expected behavior It's supposed to explode the crystal that was placed before the module was on.

ghost commented 2 months ago

try turning off only own in ca options

FluorideHistorian commented 2 months ago

try turning off only own in ca options

not a setting in rusherhack autocrystal

ghost commented 2 months ago

Oh, Ok! Thanks for letting me know. People are better off using BlackOut with Meteor Client, as RH CA is not the best.

ghost commented 2 months ago

Try using ThunderHack or Meteor with BlackOut addon

Describe the bug Auto Crystal does not target already placed crystals when it's target > priority is set to damage or damage ratio.

To Reproduce Steps to reproduce the behavior: Reset AutoCrystal config then turn the target priority to damage or damage ratio. Make sure a crystal is already placed near a fakeplayer or enemy.

Other mods List other mods you are using (if any): Meteor Client, Sodium, Nvidium, Lithium, ViaFabricPlus

Expected behavior It's supposed to explode the crystal that was placed before the module was on.

FluorideHistorian commented 1 month ago

this has been fixed in the next update