Macro ambiguity

[Darkdingus]

My personal macro is only one click per button press, but goes one step further and returns me to my previous position afterwards.

Specifically, it clicks stacks of trophies in my inventory, at the first 8 positions, and then brings them back to where I was clicking before.

Useful for a few things:
1. Looting, when I get few stacks, I click them in the monster's inventory, then direct it to the first empty slot on my inventory side. It automatically returns to my previous spot on the monster's inventory, saving the time to move around.

2. Reorganizing inventory. I don't move my mouse as much when I want to move stuff to my storage, since it automatically goes back to storage so I have less moving around when I want to drop things in there.

3. Sacrificing trophies. When I sacrifice only a few, using my macro to select a trophy slot, then automatically coming back to highlight the very same altar.

Here's a pseudocode.
1::SelectSlot(1)
2::SelectSlot(2)
...etc
SelectSlot(slotnumber)
{
Save current mouse position
click the slot selected in inventory
return mouse to the original position (without clicking)
}

[Glitchless]

1 click per macro and no logic or conditional statements.

Your macro fits within the guidelines of allowed macros.

[Sapreaver]

Glitch, wouldn't his macro need logic to determine the first empty slot. :O

[Glitchless]

Originally Posted by Sapreaver

Glitch, wouldn't his macro need logic to determine the first empty slot. :O

Yes. The way I read it, he had a different key bound for each slot. If the macro itself is going to multiple slots or is checking for which slot is empty, then yes, that is logic and is not allowed.

[Darkdingus]

No logic allowed
My underlying question was whether "remembering" the place the mouse was at before clicking said slot was counted as "logic". Thanks for the reply.

I used to have a project where it WAS going to do so (search for empty spots to click) until I learned about the legality (well, lack) thereof.