PlaneShift

IMHO "mount" means "mount", least goes to shortcuts. It's about a symmetry: should /unmount command also unsummon a pet?

well yes but only if you call the petname with the command? the reason i requested this is due to the problem with the shortcut macros. The devs REFUSE to add a wait command so you cant specify a second or so delay betwen the summon action and target / mount that you would need to chain together to get the same effect. So you cannot chain summon and mount because the mount is called before the pet finishes summoning. Of course the devs claim the lack of a wait command is to avoid automation but we all know thats a load of crud.

First of all a counter intuitive chat based UI with excessive wait times for things like mining and hammering ingots is the primary reason anyone would want automation in a game. 1)

secondly anyone with a decent keyboard and mouse already has these macros built into their drivers. wether or not a wait command is included in shortcuts doesn't matter and will not really stop or even deter macro automation.

thirdly !!for gods sake the project is open source!! any coder could compile a custom client with this command hardcoded in or worse make a fully automated bot.

there are so many ways around this limitation that the excuse of preventing automation falls kinda flat. but never the less there are certain commands that should be chain able into a macro such as action of summoning, targeting, than mounting. or as you suggested un-mounting and un-summoning.

the simple fact remains that there are only so many keys on a keyboard that can be bound to shortcuts and the sheer number of commands needed to do something fairly simple WASTES ALOT OF THEM.

but what i am asking for is a overload if you call /mount it will work normally

you have to call /mount <petname> to engage the overloaded function. and i guess if you call /mount <petname> while mounted it can unsummon the pet as well however calling /mount without the petname would dismount normally.

I've not suggested un-mounting with un-summoning effect - sorry if I haven't make it clear (forgive me my lack of English skills). I meant that every command should be doing just one simple thing. Then you have many simple commands, to get more complex result you should combine them.

In the light of this, the command chaining in a shortcuts is really that I'm be glad to see in the PS. For now command execution is kind of async (it's by design, AFAIK), so you should not expect that commands gave you results it the order they executed.

The matter of synchronous command execution were discussed so many times in so different cases - deserves making separate issue to list them all. In PS#6241 I've suggested to add /wait command to wait server response from previous command(s), so next command could be executed over a new environment, having all changes done by previous command(s): http://hydlaaplaza.com/flyspray/index.php?task_id=6241

I've also think that command chaining / queueing shouldn't increase botting. The players those make maximum use of command chaining are less probably invest additional time in the development of external macro scripts or client modifications for botting. Also, any shortcut script can be limited to sane total command number.

in a game where every player has access to the client source code it is impossible to stop botting by restricting features. as i said before you need to tackle the automation problem from a game mechanics standpoint making the farming aspect fun and removing pointless time sinking tedium that serves no purpose.