improved commands

[RalphMW]

time for a new wish!

while playing around with the shortcuts i came to some bugs/limitations.

i use a button \"Atk NPC\" assigned to F5 doing the following:
1. /target_clear
2. /target_next_nearest_npc
3. /attack
4. /confirm You_killed_NPC? /loot /target_clear

Suggestion for command 3. /attack
/attack - where optional wait is \"wait\" or a digit. \"Wait\" means stop at this pos in script until target is dead then continue in script, or if wait is a digit wait \"wait\" seconds until processing next command. wait = 0 is default while wait = wait should be default.

Suggestions for command 4. /confirm
/confirm \"String\" /yes_command /no_command - String should work with quotationmarks so that spaces in \"string\" work! Also the dialog displayed should not block all other screen activity! While the confirm dialog is displayed u can not chat or open inventory etc. For better mouse less support Confirm should understand keys \"Y\" and \"N\" or \"Enter\" and \"Escape\".

Suggestions for command 4.(2) /loot
/loot - where \"what\" could be \"all\" or \"dialog\" or a special name like \"mushroom\". what = dialog is default.

These suggestion would make my button like this:
1. /target_clear
2. /target_next_nearest_npc
3. /attack wait
4. /confirm You_killed_NPC? /loot all /target_clear
And would work by just pressing F5, Y and im done, instead of pressing F5 and using mouse to click Yes and Loot button.

btw. ur right with /attack wait i could have written 4. just like /loot all :-)

Now something beyond the scope.
How about labels in scripts? something that allowes this:
label start
/command
/command
/confirm \"XYZ\" /goto start /goto stop
label stop

What do u think folks?
(Devs: these are just wishes! The game is gorgeous already!)

[Zan]

Only one thing comes to mind while reading this ... wouldn\'t that make the killing even more monotonous and boring?

I don\'t think the macro\'s are meant to be used to create automated leveling procedures. Which is basically what your suggestion is. All you have to do is add a step 5: \"/wait for monster to respawn\" and then add in a loop or just copy paste a lot and you have yourself a killing bot.

Now I \'m not assuming you intended to do this at all but I am certain someone would. So I don\'t think the macros should get too advanced. Personally all my macros are a few lines of text and/or a single action at the most.

[RalphMW]

ur right Zen.
I didnt mean to create a killing bot!

original was the problem that on some camera settings i had probs on doubleclicking to attack an NPC and doubleclick again to loot.

however, the button worked over the aim :-)

but at least the /confirm command should be reworked then.
To display \"A String with Spaces correctly\" and not blocking the rest of the screen.

then im just fine.

Ralph.

[Androgos]

Waits are very very very hard to do since all logic is in one thread (Possible with pub/sub systems, but that\'s quite hard)

[RalphMW]

As Zan stated the possibility of a killing bot,
which we dont want, nearly all parts of my wish is obsolete!

But a better /confirm command would be good.

Your,
Golib.