Triggers and their 3 Tile Range
 

temp.plr=findplayer(plrn);
triggerserver("gui", this.name, "hurtother", plr.account, this.damage);
plr.gethit(1);
x=plr.x;
y=plr.y;
triggeraction(plr.x+1.5, plr.y+1.5, "melee", "other", this.damage, player.account, clientr.outpost);

Serverside:
elseif (param1 == "hurtother") {
findPlayer(param2).attr[3] = param3;
}


It conveniently ignores anything that happens more than 3 tiles away regardless. It doesn't find the player if they're more than 3 tiles away, doesn't set their attr[3] if they're more than 3 tiles away, doesn't call their gethit(1) if they're more than 3 tiles away...are we really stuck with serverstrings or projectiles for ranged attacks nowadays?

"params" not "param"

example:

And I think I told you already in another Thread, please use PHP tags

Still doesn't explain why it worked when the objects were within 3 tiles. That's odd...never has happened to me that I can recall.

Maybe his function is set up like this:
Pointless, but still might be the case.

Well, I don't think anyone will read throught his codes if he doesn't use PHP tags :o

Oh I wasn't arguing with you there...I'm just saying that your answer to his problem doesn't explain why it worked when the players were within 3 tiles, and he most likely just set up his parameters as "param1, param2, param3"

Try setting their chat or something ... player.attr can be unreliable sometimes. If the chat works, at least you've solved your trigger problems.

Codein figured it out, somewhere in the code it was setting on name rather than on account. :-D

Huh

GS2 is the worst debugging environment because it is nigh impossible to reduce any given problem to a testcase that everybody can use to reproduce and examine the problem. :mad: