'Use Bandage' macro

[main cedar]

Hi devs. Would it be possible to add a 'use bandage' function to the macro list please? Not 'bandage target', or 'bandage self'. I just want a hotkey/keybind to 'use bandage' so I can target one of my pets after. At the moment we don't have a use bandage macro option without having a pre-defined target. Thanks!

[silver ravine]

You can implement it on your own and bind script to hotkey:

const bandage = client.findType(0xE21, undefined, player.backpack)

if ('amount' in bandage) {
  player.use(bandage)
} else {
  console.log('No bandages found')
}

Actually BandageTarget action does what you want, you're not forced to pre-define target.

[main cedar]

Hey 1337, thanks for that, but someone told me BandageTarget required a pre-defined target/would automatically go onto your set target. Don't want that.

[silver ravine]

It will go on to your set target in case it's set.

[main cedar]

Ah, I see. I don't want it to do that, because I have more than 1 pet. And I want to easily change targets

I can't use your script though, I'm on webclient on new legacy, no scripting allowed

So we still need a simple 'use bandage' function, with no frills

[sacred solstice]

Yeah this works exactly as you require.

If I use my Bandage Self it auto targets me
then, if I use this one, it waits for target every time

[main cedar]

I shall give that a try 🙂 thanks

[main cedar]

Yeah that still doesn't work properly. If the pet is by any chance fully healed, and then you try to bandage self again, it just gets stuck with "that being is not damaged". I (we, really) need something that is reliably working 100% of the time, so a plain 'use bandages' function is the only way really, shouldn't have to be using workarounds

Thank you for the workaround suggestion though 🙂

[sacred solstice]

ok I see the problem now, it sticky targets yeah
Even if you include a WaitForTarget after the BandageTarget if the pet is fully healed the target becomes "sticky" (a blue health bar beneath the target) and the next attempted use will not WaitForTarget, instead attempting to apply immediately to the "stickied" friendly.

[sacred solstice]

Reproduce:

• Create BandageTarget macro as per image #1297977978441175141 message
• Use BandageTarget macro and manually target a pet until pet is full / or at full
• Use BandageTarget macro a second time

**Expected result: **

Cursor is waiting for target like in first use

Actual result:

Macro attempts to heal the fully healed pet without manually clicking, it does not WaitForTarget (even with the insertion of this Action)

[sacred solstice]

@main cedar You can use a macro with just LastObject in it as a temporary work around, it will definitely use the bandages (if they're the last object used) and properly waits for manual target.

[main cedar]

that was my first workaround, unfortunately it does not work in a boss fight

[sacred solstice]

lol

[main cedar]

because of all the add bodies that pop up, due to auto open

so the game is constantly reassigning last object to dead adds

[sacred solstice]

Yeah

I have bandages in my counters like so

with single click casting enable

[main cedar]

Need a 'use bandage' standalone option really

Yeah I do as well, but I hate manually clicking

[sacred solstice]

which makes that bandage button a single click for manual targeting

Agree, no good for boss fight. The fix is required, that Action should not auto target last

[main cedar]

thing is if we have a macro option for 'bandage self' which has targetting baked in, surely we can have a 'use bandage' option only without Broadsword minding it. It likely just needs implementing, but I know the cuo devs are busy at work with lots of things to do 🙂

Just thought I'd raise it because a lot of people would like it

[sacred solstice]

even Target.ClearLast() as an Action would make it work, though a second step in the macro itself, useful though

It's in Enhanced Client

They'd be fine with it

I think :D

[sacred solstice]

Reproduce here.

[main cedar]

Ideally just 'use bandage' as a standalone, instead of a clear target separate macro, because sometimes due to latency it could be delayed/less optimal than just using one macro instead of two steps or similar. Aware that might be subject to approval. Either way anything would be an improvement 🙂 Thank you for looking into it

[sacred solstice]

@main cedar #📂github-repo message

[silver ravine]

@main cedar #web-updates message