#(plonkatronix) ignoring waypoint triggers

24 messages · Page 1 of 1 (latest)

rigid plover
#

I have setup a path with a delay trigger at each end, but only one delay is happening, the npc seems to travel to the 2nd and wait ok, but walks to the 1st waypoint and ignores the animations and delay and returns to the 2nd waypoint.
I have tested this on Citizens-2.0.41-b4050 and Citizens-2.0.41-b4043
(paper 1.21.8)

waypoints: linear: points: - location: worldid: 2513c0bd-39cc-4c8f-afd6-6b7154a30d58 x: 27.0 y: 71.0 z: 43.0 pitch: 0.0 yaw: 0.0 triggers: - animations: - ARM_SWING - ARM_SWING - ARM_SWING type: animation - delay: 2400 type: delay - location: worldid: 2513c0bd-39cc-4c8f-afd6-6b7154a30d58 x: 48.0 y: 71.0 z: 47.0 pitch: 0.0 yaw: 0.0 triggers: - delay: 600 type: delay provider: linear

meager jacinthBOT
#

(plonkatronix) ignoring waypoint triggers

meager jacinthBOT
#

Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.

olive heath
rigid plover
#

yes that one was fixed with the update, but this is not the same

#

that issue cause the path to break and npc to stop, this one the npc just ignores the delay at the paypoint and turns around and goes back

olive heath
#

Yee I see.

rigid plover
#

also, it doesn't seem to quite reach the set postition of the waypoint before it decides to rurn around and go back

#

...it seems to be a block before the set pos. But, if I manually block the path it does reach the exact set spot

#

(I am ref. to the position that it fails to delay on (the first waypoint in my config), the second waypoint it does reach the actual set postion and delays fine). I just thought I would mention this in case they were related

olive heath
#

Interesting. I did some tests.

Having a path with two waypoints:

  • only the second one fires

Having a path with three waypoints:

  • only the second one fires

Having a path with four waypoints:

  • the first and second one fires

Tested via chat triggers. e.g.

- /npc path
- triggers
- add
- chat
- radius 100

      waypoints:
        linear:
          points:
          - location:
              worldid: 13dba912-4bbf-421d-a0fb-bef85740648a
              x: -671.0
              y: 63.0
              z: 444.0
              pitch: 0.0
              yaw: 0.0
            triggers:
            - lines:
              - First
              radius: 100.0
              type: chat
          - location:
              worldid: 13dba912-4bbf-421d-a0fb-bef85740648a
              x: -658.0
              y: 63.0
              z: 444.0
              pitch: 0.0
              yaw: 0.0
            triggers:
            - lines:
              - Second
              radius: 100.0
              type: chat
          - location:
              worldid: 13dba912-4bbf-421d-a0fb-bef85740648a
              x: -664.0
              y: 63.0
              z: 438.0
              pitch: 0.0
              yaw: 0.0
            triggers:
            - lines:
              - Third
              radius: 100.0
              type: chat
          - location:
              worldid: 13dba912-4bbf-421d-a0fb-bef85740648a
              x: -670.0
              y: 63.0
              z: 438.0
              pitch: 0.0
              yaw: 0.0
            triggers:
            - lines:
              - Fourth
              radius: 100.0
              type: chat
        provider: linear
rigid plover
#

That is interesting, i will try the same tests now

#

same results as yours

#

a sep. issue I just noticed (and not sure why)
on my test server I see the waypoints no problem as per picture (and can crouch to select them), but on the production server I don't see them and crouching doesn't allow me to select them

image.png
silver glacierBOT
rigid plover
#

Having a path with five waypoints: only the second one fires.

#

Having a path with six waypoints: the first and second one fires.

#

I won't continue any more tests

queen talon
queen talon
rigid plover
#

The test server is an almost exact copy of the production server, almost being not having plugins connected to mysql

queen talon
#

almost is not the same as exact

rigid plover
#

Thank you for pushing Citizens-2.0.41-b4051
This seems to have fixed the issue 🙂