I am trying to get an npc to open a door...
I have 3 waypoints, 1 starting point, 2nd just before the closed door, on the 2nd waypint I have added delay 2s command then npc command add setblock -4709 13 5315 birch_door[open=true] replace, then a 3rd waypoint inside a room the other side of the door. No matter what I try, the npc just keeps walking back and fore from point1 to point 2, it does not open the door. I also tried adding npc pathopt --open-doors true
any idea's on why this isn't working please?
#(plonkatronix) closed door breaks path and door won't open
whole edge
dry ridgeBOT
(plonkatronix) closed door breaks path and door won't open
dry ridgeBOT
I am trying to get an npc to open a door...
I have 3 waypoints, 1 starting point...
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.
whole edge
if I manually open the door then the npc will get to the 3rd point, but I need to have the npc actually open the door
whole edge
I just tried updating to the latest citizens and setting waypoints has changed to the point I no longer know how to set them! the right click is not happening. I have reverted back to find all my npcs have now lost their paths! where is the notifiaction of this game breaking change?
...this had just wasted 3 days of work!
whole edge
everything is broken now, console keeps spamming java.lang.IndexOutOfBoundsException: Index 1 out of bounds for length 1, even if I delete the offending npc and start again, keeps doing java.lang.IndexOutOfBoundsException: Index 1 out of bounds for length 1
Updating to Citizens 2.0.41 has killed my npcs!
jaunty sentinel
everything is broken now, console keeps spamming java.lang.IndexOutOfBoundsExcep...
!logs
whole edge
https://paste.denizenscript.com/View/138150
Also seems like all my npc got fed up and left the server too!
yet my npc's are still there!
as you can see from the logs, I deleted the welshgirl npc and started again, created the npc, set new waypoints with delays. the npc walks to the second waypoint and does not move from there, at this point you see loads of errors
and this happened again
jaunty sentinel
thorny ploverBOT
!logcheck https://paste.denizenscript.com/View/138150
jaunty sentinel
Update to latest dev build, if the issue persists then consider plugin interference and check if the issue exists with only citizens.
(Obviously back up your server prior)
!update citizens
thorny ploverBOT
!update citizens
whole edge
This what my console looks like now, like I said, updating citizens has broken all my npcs
jaunty sentinel
We had a thread recently, I forget where but I remember it was brought up that essentials may be reading npcs as players.
Will wait for fullwall to come in and see what the issue could be.
(Though essentials is reading them as users?)
Meanwhile can you upload your saves.yml?
!paste
whole edge
Hmm, all was working fine yesterday, I just had a problem getting an npc to open doors so I updated citizens, only then all the problems came.
I just tried the latest snapshot from jenkins (Citizens-2.0.41-b4028.jar) and still the same issue.
if I create all 3 waypoints the npc starts moving between them, as soon as I enter triggers to go and add the delay commands, then the npc stops and errors in console again.
I will upload the log again to reflect this attempt, and will add my saves too
cunning hareBOT
https://paste.denizenscript.com/View/138152
whole edge
whole edge
another update, removed the npc and recreated it, I make the 3 waypoints and the npc starts to walk to them fine, but as soon as i do triggers and add a delay to a selected waypoint, the npc stops there and the console errors start again with [18:24:10 INFO]: [Citizens] Exception while updating 136: Index 3 out of bounds for length 3. [18:24:10 WARN]: java.lang.IndexOutOfBoundsException: Index 3 out of bounds for length 3
if I add only 1 trigger (add delay 40) it works and the npc will walk to all points and wait 2sec at the one. As soon as I select another waypoint and another 2nd trigger (the same (add delay 40)) then we start getting the errors. If I remove that second trigger then type exit to leave triggers, the path starts to work again
whole edge
sorry to keep adding to this but the behaviour keeps changing, I'm trying to add as much feedback as I can to this.
Now I can't even create 1 trigger, as soon as the npc gets to the waypoint with the trigger it errors with Index 3 out of bounds for length 3
If I remove the trigger then the npc will carry on going to all waypoints.
There is defo something wrong with triggers i guess
jaunty sentinel
Will have to wait till fullwall responds.
(There was an update about hour and a half ago regarding waypoints, not sure if it's related.)
whole edge
(There was an update about hour and a half ago regarding waypoints, not sure if ...
ooh ty, trying that now
on that latest build I no longer get the Index 3 out of bounds for length 3 and errors in the console,
however if I add a trigger (add delay 2s), the npc still stops when it gets to the waypoint that has that trigger and the path is no longer followed.
What is strange though and it goes agains my tests, I have another npc that has 3 waypoints, one waypoint has a 2sec delay trigger, and that npc is working fine. I did try adding a 2nd trigger to that npc and then it broke that too, remove the 2nd trigger and it works again.
so defo something really odd going on with triggers
whole edge
just to make sure it was not a corrupted saves.yml, I shut down, renamed mine out the way, restarted, it generated a new one, I setup a new npc and the same thing happens... no errors (on the latest build) but the npc gets to a waypoint with a trigger and it stops
more input... I added chat triggers and they all work ok without it breaking, so far it's only the delay command that is causing this
whole edge
I may have found something useful here.
I reverted back to the earlier working version we had in a backup, I compared an entry the old version saves.yml to the new version...
new version:
waypoints: linear: points: - location: worldid: c21b3faf-9050-459a-9125-7c7af141362d x: -4710.0 y: 13.0 z: 5315.0 pitch: 0.0 yaw: 0.0 triggers: - delay: 40 type: delay1
old version:
linear: cachePaths: false cycle: false points: '0': location: worldid: c21b3faf-9050-459a-9125-7c7af141362d x: -4730.0 y: 12.0 z: 5320.0 yaw: 0.0 pitch: 0.0 triggers: '0': delay: 60 type: delay
The new version seems to be missing the numbering system '0' for points and triggers.
maybe that was intended by the dev (i don't know), but it's the only dif I can see between the two
{edit]
I also just spotted delay1 not delay
strong cloud
I can't reproduce this @whole edge
whole edge
Oof, i have been praying for an update to fix this.
I have had to revert to a backup losing many many days work
whole edge
actually I think I got it to happen on restart
same thing is happening sadly
I can create the path and the npc will follow, as soon as I try nd put a delay on a waypoint then it stops when it get to that point
I can give you said perms needed to come and try it yourself on my test server if needed
strong cloud
!logs @whole edge
thorny ploverBOT
!logs <@1235758951094681640>
Info: logs
strong cloud
@whole edge no that's ok, you need to update to citizens #4034
neon bear