PlaneShift

Support => Technical Help: IN GAME bugs (after loading world) => Topic started by: zanzibar on December 06, 2005, 07:58:27 pm

Title: An observation.
Post by: zanzibar on December 06, 2005, 07:58:27 pm
With shortcuts, the commands are read simultaneously, not sequentially.

That means that I can\'t equip daggers, say something, and then sheath them again in a single shortcut.  If the daggers are drawn, they are sheathed.  If they\'re in the inventory, they\'re equipped.  The /say command goes through no matter what.

I\'m not sure if this needs changing or not, but it\'s there.
Title:
Post by: Zan on December 06, 2005, 11:12:34 pm
All you would need to fix that is a /wait [x number of seconds] command to put in between the actions, I think. It has been suggested many times before.

Though it beats me why you would want to draw a weapon to say something then and sheathe them again ... and if you really do, make two buttons or three buttons ;)
Title:
Post by: zanzibar on December 07, 2005, 04:32:52 am
Quote
Originally posted by Zan
All you would need to fix that is a /wait [x number of seconds] command to put in between the actions, I think. It has been suggested many times before.

Though it beats me why you would want to draw a weapon to say something then and sheathe them again ... and if you really do, make two buttons or three buttons ;)




The problem is that the /wait command would be read at the same time as all the other commands.  Every command in the shortcut is executed simultaneously.


Besides, a /wait command would be pretty dangerous, because then you could make a bot.

For instance, a crystal way training bot:


/cast life infusion
/wait 15
/cast life infusion
/wait 15
/cast life infusion
/wait 15
/cast life infusion
/wait 15
/cast life infusion
/wait 15
/cast life infusion
/wait 15


Just set that to run 50 times.  Set it off.  Come back in 13 minutes.  Train up.  Set it off again.  It would also work for camping NPCs, if there were an autoloot command:


/attack next nearest npc
/lootall
/target_clear
/wait 45
/attack next nearest npc
/lootall
/target_clear
/wait 45


Just leave that running for a couple hours, then come back, eat all the fish and waybread, leave it running again.   Come back, sell the stuff, then go back and repeat.
Title:
Post by: Cha0s on December 07, 2005, 04:44:55 am
Perhaps the best solution would be a forced wait of a second or so between every commands AND a maximum number of 10 commands per shortcut. Shortcuts should also be unable to call other shortcuts.
Title:
Post by: DaveG on December 07, 2005, 05:10:39 am
This is yet another bug I reported 4 months ago... and no one ever did anything with.  :P

http://planeshift.oodlz.com/bugtracker/bug.php?op=show&bugid=808
Title:
Post by: stfrn on December 07, 2005, 05:23:58 am
Some sort of automatic delay, as commands are sent one by one would be best. Right now they are sent in one big packet I beleive.
Not putting functions in because people can use it for botting is a bit of an empty argument. There are many programs floating around the internet that let you keep clicking in one place in set patterns, at set times, etc, some it would be trivial for somone to set up their own wait triggers using an external program. Better to have them using our program, so we have some control.
Title:
Post by: zanzibar on December 07, 2005, 05:26:32 am
Quote
Originally posted by DaveG
This is yet another bug I reported 4 months ago... and no one ever did anything with.  :P

http://planeshift.oodlz.com/bugtracker/bug.php?op=show&bugid=808



This isn\'t exactly true.  For instance, this is a shortcut that I use and it works just fine:


/target_clear
/target next nearest npc
/attack 1


Another:

/target_clear
/target next nearest npc
/loot


Another:

/target_clear
/target next nearest item
/target_context



You just can\'t do stuff like this:


/equip dagger
/dequip dagger
Title:
Post by: stfrn on December 07, 2005, 05:31:55 am
Hm, actually that clarifies things in a way you weren\'t thinking- all the /target commands are client based. So they are done long before the /equip command has even gotten to the server. Loot and attack could be the first ones in their respective shortcuts, they would still take longer to finish. Equip and dequip however both need to go to the same place in the server, and are done at the same time.
Title:
Post by: zanzibar on December 07, 2005, 06:04:50 am
Quote
Originally posted by stfrn
Hm, actually that clarifies things in a way you weren\'t thinking- all the /target commands are client based. So they are done long before the /equip command has even gotten to the server. Loot and attack could be the first ones in their respective shortcuts, they would still take longer to finish. Equip and dequip however both need to go to the same place in the server, and are done at the same time.



I\'m a freaking genius!  Give my characer trias!
Title:
Post by: stfrn on December 07, 2005, 06:18:38 am
Quote
Originally posted by zanzibar
I\'m a freaking genius!  Give my characer trias!

yes, congrats on being as smart as dave was 4 months ago :P

At any rate, seeing as this hasn\'t changed in 4 months, if you want this changed you will have to lean on dave to fix it. Granted, he already has a bunch of people bugging him, so one way or anouther this will have to stay a wish for a while.
Title:
Post by: Nikodemus on December 07, 2005, 04:45:29 pm
*Nikodemus gives Zanzibar a candy as a revard, then he wonders if he trust him enough to eat it* ;>

As about the delay beatwen different commands send to the server:
Please, don\'t make things even longer than they are now. We are already frustrated enough because of waiting for different windows refresh, context menu to appear, items to appear in slots we want them to be and many more.

*nikodemus sticks to stfrn ad DaveG leg in begging pose \"Please, Please, Please, Please, Please, Please, Puh-leeeeeeze!\" and awaits his reaction.*

P.S. maybe add to each command inside the big packet some  number of order? the packet will grow, but we avoid annoying waiting.