Projectile Hit Detection

[xAndrewx]

When a projectile is fired (using shoot) and hits a wall on the serverside it calls this function in the Control-NPC

function onActionProjectile(x, y, shootparams) {

but then the bullet doesn't disappear from the client. It still carries on flying past, even though it's hit an object.

Check the screenshot- the bullet hit the tree (fire starts on impact of hitting the tree on the serverside) but the bullet is still flying past.

[Skyld]

Does the tree have the same setshape both clientside and serverside? I think I remember issues with this when setshape was used both serverside and clientside with different values.

[fowlplay4]

I was under the impression that server-side hit detection is irrelevant to what the client actually sees since the client is basically simulating the shot on their screen, so if the blocking isn't the same on the client-side you'd see scenarios like that.

[cbk1994]

Originally Posted by fowlplay4

I was under the impression that server-side hit detection is irrelevant to what the client actually sees since the client is basically simulating the shot on their screen, so if the blocking isn't the same on the client-side you'd see scenarios like that.

This is correct.

[xAndrewx]

It not just happens on objects, it also happens on players too.

No real fix then? :[

[cbk1994]

Originally Posted by xAndrewx

It not just happens on objects, it also happens on players too.

No real fix then? :[

I don't think it's broken..? As has been explained, you probably have different blocking policies on serverside than clientside (e.g. noplayerkilling on clientside but not serverside, different shapes on serverside, etc).

[xAndrewx]

Oh I see- darn

thanks

[xXziroXx]

Would be nice if there was a command to make players blocking/not blocking for projectiles. As it is now, scripting your own projectile system is mandatory if you want to have non-blocking players on clientside.

[cbk1994]

Originally Posted by xXziroXx

Would be nice if there was a command to make players blocking/not blocking for projectiles. As it is now, scripting your own projectile system is mandatory if you want to have non-blocking players on clientside.

You can use noplayerkilling on clientside, but then players can walk through other players, which may not be what you want. I really do wish we had more customizable projectiles.

[xXziroXx]

Originally Posted by cbk1994

You can use noplayerkilling on clientside, but then players can walk through other players, which may not be what you want. I really do wish we had more customizable projectiles.

noplayerkilling on clientside makes projectiles behave different on each players screen, since every other player will be non-blocking for them. It creates some very annoying situations for an online game.

[Gunderak]

Having the same issue.
My fireball sets crops on fire then continues to pass.

[cbk1994]

Originally Posted by Gunderak

Having the same issue.
My fireball sets crops on fire then continues to pass.

Have you tried the solutions presented in this thread?

[Gunderak]

Yes, and it has the exact same setshape on the client and serverside.

[cbk1994]

Originally Posted by Gunderak

Yes, and it has the exact same setshape on the client and serverside.

Post your code.

[Gunderak]

I'm not actually on my computer at the moment, I'm in these forums on my iPhone.
In fact I'm not even home lol..

[cbk1994]

Originally Posted by Gunderak

I'm not actually on my computer at the moment, I'm in these forums on my iPhone.
In fact I'm not even home lol..

I can wait.

[Gunderak]

PHP Code:

function onActionProjectile(){
  if(params[0] == "fireball"){
    if(this.attr[5] == null){
      this.attr[5] = "wheat_fire.gani";
      scheduleevent(9, "onStop");
    }
  }
}
function onCreated(){
  this.setimg("corinthia_wheat.png");
  this.setshape(0, 32, 32);
  this.maker = null;
}
//Then there is some chopping down code for harvesting wheat
//#CLIENTSIDE
function onCreated(){
  this.setshape(0, 32, 32);
} 


[cbk1994]

It should be setshape(1, 32, 32). Not sure if that will fix it, but besides that everything looks fine. Does it block on clientside when you try to walk through it?

[Gunderak]

No it does not block on the clientside.
It's wheat lol..
Just out of curiosity; what does the first paramater of setshape do?

[Tolnaftate2004]

Originally Posted by Gunderak

Just out of curiosity; what does the first paramater of setshape do?

It's the shape, 1 => rectangle.
There are no other shapes defined afaik.

[Crow]

Originally Posted by Tolnaftate2004

There are no other shapes defined afaik.

Yup, you're right about that.

[Gunderak]

So what does doing setshape(0 achieve o_O?

[Tricxta]

Originally Posted by Gunderak

So what does doing setshape(0 achieve o_O?

nothing at all

[Crow]

Originally Posted by Tricxta

nothing at all

That's not quite~ right. It should just set a rectangle shape like all the other setShape() calls, I believe. But using 1 as the type is the right thing to do.

[Gunderak]

cbk changing that didn't fix the issue.
Is there any other way that you think you could make the fireball go through each NPC and set it on fire and continue passing; setting anything in it's path on fire?

[cbk1994]

Originally Posted by Gunderak

cbk changing that didn't fix the issue.
Is there any other way that you think you could make the fireball go through each NPC and set it on fire and continue passing; setting anything in it's path on fire?

No, this is not how projectiles work on Graal. You'd have to rescript them.

And if they're not blocking clientside, that's your problem.

[Gunderak]

darn

[Admins]

setshape first parameter:
0 - disable
1 - rectangle
2 - tile based (requires setshape2())
Update: I've updated the description on wiki.graal.net for setshape and setshape2.

[ffcmike]

If possible it would be useful to be able to set shapes in the same way as polygon displays.

[BlueMelon]

Originally Posted by ffcmike

If possible it would be useful to be able to set shapes in the same way as polygon displays.

You mean like showpoly?
That would be pretty cool.