Pull not working

Character: Whip Dude
Published: 2022-07-13 05:17 UTC

Description

<736/973hp 614/646m 1074/1074mv 12012tnl (41.46%) 5 AM none fighting water outdoor waxing> If you are fighting you can only pull your opponent. A sahuagin scout is writhing in agony. <736/973hp 614/646m 1074/1074mv 12012tnl (41.46%) 5 AM none fighting water outdoor waxing> A sahuagin scout's claw EVISCERATES you! You dodge a sahuagin hunter's stab. Your stinging lash MASSACRES a sahuagin scout! A sahuagin scout dodges your slice. A sahuagin scout is writhing in agony. <691/973hp 614/646m 1074/1074mv 12012tnl (41.46%) 5 AM none fighting water outdoor waxing> pull s If you are fighting you can only pull your opponent. A sahuagin scout is writhing in agony. <691/973hp 614/646m 1074/1074mv 12012tnl (41.46%) 5 AM none fighting water outdoor waxing> pull w If you are fighting you can only pull your opponent. A sahuagin scout is writhing in agony. ***After I kill him and focused on the hunter, I could pull the hunter.

Comments

Carrion Fields on 2022-07-13 05:17 UTC

Automatically imported from the legacy bug board forum.
Ishuli on 2022-07-14 00:09 UTC

Subject: Working as intended.

pull

Since you have two sahuagin in there, it's confused since it is trying to default to the first keyword match in room which isn't necessarily the one you are fighting.

So toss in a target name to help.
Java on 2022-07-17 01:10 UTC

Subject: That kinda sounds like the opposite of working as intended..

Shouldn't the intent of pull be that it works the way every other combat skill works, where the default target is the mob that you're currently targetting?

The fact that pull targets the first keyword (which is pretty arbitrary), rather than the mob you're actively fighting seems like a bug to me. Having a relatively easy workaround doesn't make it less buggy.
Ishuli on 2022-07-17 13:11 UTC

Subject: RE: That kinda sounds like the opposite of working as intended..

It's the way it passes an argument into an argument into a check into a check, where some can use the memory location of the individual, and other require "names" - which translates to keywords on mobs.

So then when you do the command and multiple mobs share names, it gets all kinds of weird due to how pull has to work since it takes multiple argument (name and direction) which it segments out, while it tries to also let you just enter one argument and not obligate two.

Which is funky.

I'll spend some more time on it when I have time and maybe work it from the ground up in a way that prevents this situation AND doesn't create new problems. I already spent an hour just on this this morning, and I'll put some more time in it later to see if I can work it out.